[oe] Status of ARM machines in OE

[Paul Sokolovsky]

Hello Marcin,

Monday, January 8, 2007, 5:18:46 PM, you wrote:

> During weekend I build 'task-base' for all ARM (armv4t and better) 
> machines and Angstrom distribution.

  Thanks!

> The list included:

[]

> h1910 - kernel broken:
> arch/arm/mach-pxa/built-in.o: In function `h4000_set_led':
> dma_needs_bounce.c:(.text+0x1ca0): undefined reference to `ipaq_asic3_set_led'
> dma_needs_bounce.c:(.text+0x1cd0): undefined reference to `ipaq_asic3_set_led'
> dma_needs_bounce.c:(.text+0x1ce4): undefined reference to `ipaq_asic3_set_led'
> dma_needs_bounce.c:(.text+0x1d04): undefined reference to `ipaq_asic3_set_led'
> dma_needs_bounce.c:(.text+0x1d18): undefined reference to `ipaq_asic3_set_led'
> make: *** [.tmp_vmlinux1] Error 1

> Full log: 
> http://ewi546.ewi.utwente.nl/tinderbox/showlog.pl?machine_id=177&logfile=20070107150654.log

> =============================================================================

> htcblueangel - kernel broken is same place as h1910

> =============================================================================

> rx3000 - kernel broken is same place as h1910

  Well, all these 3 actually "no defconfig" cases, with some "default"
one being used, I'll take care of this. But htcblueangel and rx3000
are more complex, they are not supported by Angstrom formally, and
Angstrom's default linux-handhelds-2.6 version doesn't work for them,
they require much more recent versions. I'm going to add ?= version
spec to machine config, this way it will be fully overridable by
local.conf/distro.


> =============================================================================

> htcuniversal - kernel broken:

CONFIG_AUDIT is broken in latest versions, old defconfig... Will be
taken care of.

[]

> =============================================================================

> magician is OK - builds without problem. But as this is HTC Magician then
> maybe we should rename it to htcmagician to follow other htc phones
> (htcblueangel, htcuniversal) which are in OE?

  Philipp, please, please!!! ;-)))

  Generally, we should start to think about machine naming convention.
As an informal proposal, I would like to ask machine maintainers
considering adopting naming scheme where device name/model is
prepended with vendor or well-known brand ID. "htc*" devices are good
example of this.

  iPaqs also used to be, starting with well-known "h" prefix ;-). But
no longer, with series have expanded. So, they'd ideally be called
like "ipaq-hx4700", etc. Yes, that applies to Zaurus too ;-).

  So again, I don't think it's good time to set some rules right now,
but sooner or later OE will need them. So, it would be nice to start
exchanging ideas now, and one of them is above ;-).


> =============================================================================

> Maintainers of 'broken' machines - would be nice if you will try to fix
> those problems. I will try to do such builds in future.

  Such regression builds are very good thing. It would be nice if
there was some background info available about them - are they
automated and to what extent, how often they are run, etc. I
understand that at this time that info will be likely "this is test,
pilot run", but if you have some plans/ideas regarding that, please
share them.



-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com