[opensuse-arm] GSoC: openSUSE ARM
Hi, does anyone have ideas fora good GSoC project around openSUSE ARM? http://en.opensuse.org/openSUSE:GSOC_2012_Ideas We should come up with ideas for this wiki page ASAP . Thanks, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 03.03.2012, at 10:54, Dirk Müller
Hi,
does anyone have ideas fora good GSoC project around openSUSE ARM?
http://en.opensuse.org/openSUSE:GSOC_2012_Ideas
We should come up with ideas for this wiki page ASAP .
One idea I'd have is to properly get the AC100 working. That would involve: - get u-boot bootstrap by the android bootloader - get the kernel working - put all of this into a kiwi description and into obs Since Andreas has such a device, he would be a great fit for the mentor - if he wants to be one. Apart from that, there are the obvious things: - get packages compiled - package binary gfx drivers - get yast working with arm specific hw - do the firstboot thing in kiwi for config on 1st boot (too easy?) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Saturday 03 March 2012, Alexander Graf wrote:
One idea I'd have is to properly get the AC100 working.
I'd be also interested in that (I also have an AC100, but no time to debug it yet). I think Joop has already some image available?
Apart from that, there are the obvious things:
- get packages compiled - package binary gfx drivers
Not a self-contained task for a student who is otherwise not experienced with openSUSE..
- get yast working with arm specific hw
Good one, but we don't know how much work it would be .. it could be anything from a one liner fix to a rewrite of partitioning or other arch specific parts ;/
- do the firstboot thing in kiwi for config on 1st boot (too easy?)
Probably touch <magicfile> plus all the debugging afterwards :) Hmm. I'll think about it over the weekend. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 03.03.2012, at 13:23, Dirk Müller wrote:
On Saturday 03 March 2012, Alexander Graf wrote:
One idea I'd have is to properly get the AC100 working.
I'd be also interested in that (I also have an AC100, but no time to debug it yet). I think Joop has already some image available?
Well, the stressing point is "properly", hence the u-boot work and integrating all of this with how the other systems work.
Apart from that, there are the obvious things:
- get packages compiled - package binary gfx drivers
Not a self-contained task for a student who is otherwise not experienced with openSUSE..
Yeah, this is really more of a brainstorming. I merely noted all the things that I remembered need work :)
- get yast working with arm specific hw
Good one, but we don't know how much work it would be .. it could be anything from a one liner fix to a rewrite of partitioning or other arch specific parts ;/
Yeah, the first step would be to see what actually needs to be done :)
- do the firstboot thing in kiwi for config on 1st boot (too easy?)
Probably touch <magicfile> plus all the debugging afterwards :)
Hmm. I'll think about it over the weekend.
Cool, thanks! :) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 03.03.2012 13:23, schrieb Dirk Mueller:
On Saturday 03 March 2012, Alexander Graf wrote:
One idea I'd have is to properly get the AC100 working.
I'd be also interested in that (I also have an AC100, but no time to debug it yet).
I think Joop has already some image available?
Yes, the image I guess is not really the issue here. Like Ubuntu, Joop has been using the marvin24s-kernel from gitorious. This is combined with an initrd into an Android Boot Image that the native bootloader understands. Alex would like this to be replaced by a U-Boot that loads kernel and initrd from an actual partition and that kernel being the standard Factory kernel with appropriate config. Someone would need to diff a working ac100 kernel against the corresponding upstream kernel and forward-port it to 3.2 (or whatever 12.2 uses) and I've been lacking the time to do so. There's a few pages on U-Boot attempts here: http://ac100.grandou.net/uboot http://pecourt.ovh.org/wiki-tegra/doku.php?id=uboot http://ac100.grandou.net/debian_uboot Kernels: http://ac100.gudinna.com/toshiba-gpl-source-code/ (2.6.36?) http://gitorious.org/~marvin24/ac100/marvin24s-kernel/commits/chromeos-ac100... BTW if someone wants to add Tegra2/AC100 or Tegra3 emulation to QEMU I'd be willing to help mentor that. ;) Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, March 3, 2012 2:56 pm, Andreas F01rber wrote:
Am 03.03.2012 13:23, schrieb Dirk Mueller:
On Saturday 03 March 2012, Alexander Graf wrote:
One idea I'd have is to properly get the AC100 working.
I'd be also interested in that (I also have an AC100, but no time to debug it yet).
I think Joop has already some image available?
Yes, the image I guess is not really the issue here.
Like Ubuntu, Joop has been using the marvin24s-kernel from gitorious. This is combined with an initrd into an Android Boot Image that the native bootloader understands.
Alex would like this to be replaced by a U-Boot that loads kernel and initrd from an actual partition and that kernel being the standard Factory kernel with appropriate config. Someone would need to diff a working ac100 kernel against the corresponding upstream kernel and forward-port it to 3.2 (or whatever 12.2 uses) and I've been lacking the time to do so.
There's a few pages on U-Boot attempts here: http://ac100.grandou.net/uboot http://pecourt.ovh.org/wiki-tegra/doku.php?id=uboot http://ac100.grandou.net/debian_uboot
I've build a u-boot-ac100 package. It can be found in: home:worldcitizen:armv7l. This also holds kernel-tegra-ac100 which includes uImage, needed for u-boot-ac100. I haven't tested this one yet. I've also created python-putusb in home:worldcitizen. Probably my worst package ever, I will improve this one. Instructions for usage can be found here: http://ac100.grandou.net/uboot http://ac100.grandou.net/putusb http://ac100.grandou.net/debian_uboot I still need to test this. From what I've read u-boot can tested without flashing it. I haven't had time yet to test this.
Kernels: http://ac100.gudinna.com/toshiba-gpl-source-code/ (2.6.36?) http://gitorious.org/~marvin24/ac100/marvin24s-kernel/commits/chromeos-ac100...
BTW if someone wants to add Tegra2/AC100 or Tegra3 emulation to QEMU I'd be willing to help mentor that. ;)
Andreas
-- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N¨¹rnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend02rffer; HRB 16746 AG N¨¹rnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sat, 2012-03-03 at 10:54 +0100, Dirk Müller wrote:
Hi,
does anyone have ideas fora good GSoC project around openSUSE ARM?
http://en.opensuse.org/openSUSE:GSOC_2012_Ideas
We should come up with ideas for this wiki page ASAP .
Thanks, Dirk
It would be good if we had a variety of tasks that covered beginner to advanced levels. So far things that I think may be of benefit from listening to others are: Tegra support in Qemu ARM support in openQA, including serial only connections Lima graphics driver support Better ARM support in Kiwi - 1st boot config etc Better ARM support for YaST AC100 support lguest support Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 03.03.2012 10:54, schrieb Dirk Müller:
does anyone have ideas fora good GSoC project around openSUSE ARM?
- Adding capability-based build scheduling to OBS (Alex' idea) Many of the ARM boards have very limited amounts of RAM, like 256 or 512 MB. To broaden the number of build nodes it would be nice being able to add such build nodes for their CPU power but to avoid scheduling builds on them that are destined to fail due to required amounts of RAM. Possibly also forcing RAM-intensive builds to QEMU system emulation on x86/ppc. Apparently right now there is only a single "powernode" flag to prefer some build nodes. Would there be any mentor for such an OBS extension? Adrian? Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Mittwoch, 7. März 2012, 14:55:35 schrieb Andreas Färber:
Am 03.03.2012 10:54, schrieb Dirk Müller:
does anyone have ideas fora good GSoC project around openSUSE ARM?
- Adding capability-based build scheduling to OBS (Alex' idea)
Many of the ARM boards have very limited amounts of RAM, like 256 or 512 MB. To broaden the number of build nodes it would be nice being able to add such build nodes for their CPU power but to avoid scheduling builds on them that are destined to fail due to required amounts of RAM. Possibly also forcing RAM-intensive builds to QEMU system emulation on x86/ppc. Apparently right now there is only a single "powernode" flag to prefer some build nodes.
Would there be any mentor for such an OBS extension? Adrian?
Yes, we would mentor it. That feature should cover also some other use cases like used virtualization, network access, cpu features, product building, storage size and so on... And for step 2, we should be able to create instance on the fly in a flexible way. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 07.03.2012 15:10, schrieb Adrian Schröter:
Am Mittwoch, 7. März 2012, 14:55:35 schrieb Andreas Färber:
- Adding capability-based build scheduling to OBS (Alex' idea)
Many of the ARM boards have very limited amounts of RAM, like 256 or 512 MB. To broaden the number of build nodes it would be nice being able to add such build nodes for their CPU power but to avoid scheduling builds on them that are destined to fail due to required amounts of RAM. Possibly also forcing RAM-intensive builds to QEMU system emulation on x86/ppc. Apparently right now there is only a single "powernode" flag to prefer some build nodes.
Would there be any mentor for such an OBS extension? Adrian?
Yes, we would mentor it.
That feature should cover also some other use cases like used virtualization, network access, cpu features, product building, storage size and so on...
And for step 2, we should be able to create instance on the fly in a flexible way.
Thanks, I've added the following: http://en.opensuse.org/openSUSE:GSOC_ideas#Capability-based_build_scheduling Feel free to improve on the description. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (6)
-
Adrian Schröter -
Alexander Graf -
Andreas Färber -
Andrew Wafaa -
Dirk Müller -
Joop Boonen