Since we now use the lpia APT repository for both Menlow and McCaslin
based devices, we absolutely can use a single platform definition and
control the correct set of device specific packages (like
ume-config-samsung-q1-ultra or ume-config-crownbeach) with the fset
definitions.
For example, we could have a single platform called 'mid' for Mobile
Internet Device, and have an fset for crownbeach-full-stack that pulls
in all the Ubuntu-mobile packages + ume-config-crownbeach + correct lpia
kernel + whatever makes sense for that specific device, and then have an
equivilant fset for Samsung-q1-ultra-full-stack.
--rusty
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of GrueMaster
Sent: Monday, October 29, 2007 10:42 AM
To: [email protected]
Subject: Image issues
The recent images (since ~10/16) have installed both lpia and lpiacompat
kernels, defaulting to the lpiacompat kernel on bootup. This fails for
melow systems, as the lpiacompat modules do not contain the psb kernel
video driver, yet the system is configured to boot X with the psb
drivers. This causes XWindows to constantly respawn, thrashing the
unionfs image.
The bigger question is, should the lpia and lpiacompat configurations be
combined? There really is no need to have separate configs, as the core
hardware is the same and the rest is built as modules. The menlow
specific modules should be intelligent enough to bypass code specific to
that hardware if not needed (i.e. snd-hda-intel).
--
Tobin Davis <[EMAIL PROTECTED]>
--
Ubuntu-mobile mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
