Hi Andy, > Just curious about this "machine name" concept, what does it actually > address?
This is what you give to OE as the MACHINE settings, it defines things like * jffs2 params for the rootfs * flash size * serial tty setting * preferred X server * machine capabilities in general (phone, screen, keyboard, usbhost, ...) This MACHINE setting is also used as OVERRIDE for config file in packages such as: [EMAIL PROTECTED]:/local/pkg/oe/openembedded$ find . -name om-gta01 ./packages/scummvm/files/om-gta01 ./packages/uclibc/uclibc-0.9.29/om-gta01 ./packages/uclibc/uclibc-0.9.30/om-gta01 ./packages/netbase/netbase/om-gta01 ./packages/u-boot/u-boot-1.2.0/om-gta01 ./packages/base-files/base-files/om-gta01 ./packages/tslib/tslib/om-gta01 ./packages/gpephone/gpe-applauncher/om-gta01 ./packages/gpsd/files/om-gta01 ./packages/pointercal/files/om-gta01 ./packages/freesmartphone/frameworkd/om-gta01 ./packages/openmoko2/openmoko-dialer2/om-gta01 ./packages/initscripts/initscripts-1.0/om-gta01 ./packages/fbset/fbset-modes/om-gta01 > It has become clear lately that we need single rootfs image > that deals with several types of device, is that what it actually does? While a single rootfs image is very appealing, our experience says it only works well on device families where the siblings are _very_ related. (It may work for gta01 and gta02, but we're also talking about machines like the Motorola EZX series here or the Zaurus family which have dozens of somewhat similar, but still too different variants) Of course you can try to achieve most of this with runtime configuration and shipping stuff for all variants, but you will run into limitations, especially regarding flash size. -- :M: _______________________________________________ devel mailing list [email protected] https://lists.openmoko.org/mailman/listinfo/devel
