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 Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
On Thu, Nov 08, 2007 at 01:42:56PM -0800, GrueMaster wrote: > Ok, given that the new drm module won't be integrated any time soon, could it > be renamed to avoid conflicting with the main drm module? This is a simple > fix that will eventually go away when the drm modules are merged. Renaming the module isn't enough, the symbols will all need to be renamed as well in order to ensure that the correct module is used. -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
On Thu, Nov 15, 2007 at 11:35:10PM -0800, Tobin Davis wrote: > Isn't that what depmod -a does? Have you tried this? > It worked fine for me a few weeks ago, but I'll try it again with a newer > image, just to be sure. Depmod will generate the symbol dependencies, but it'll do so by looking at the exported symbols. If two modules provide the same symbols it has no way of knowing which is the correct one to load for the module which requires them. The order of preference ends up being dependent on the order that the modules are copied into a directory, so I suspect what ended up happening in your test is that psb correctly loaded the new drm module. However, I suspect that attempting to load (say) i915 would also result in the new drm module being loaded, potentially along with the old one. The result would probably not be pretty. To avoid this scenario, the exported symbols in the two modules need to have different names and the psb driver needs modifying to reference the new names. -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
On Thu, 2007-11-08 at 20:40 +, Matthew Garrett wrote: > On Mon, Nov 05, 2007 at 05:39:26PM +0100, Tollef Fog Heen wrote: > > * GrueMaster > > > > | The bigger question is, should the lpia and lpiacompat configurations be > > | combined? > > > > No, they use different versions of drm.ko which are not compatible. I > > suspect this will be fixed sometime during the hardy cycle, Amit might > > know more. > > TTM isn't going to land in mainline DRM before Hardy, so a separate DRM > is pretty much a necessity. > > -- > Matthew Garrett | [EMAIL PROTECTED] > Ok, given that the new drm module won't be integrated any time soon, could it be renamed to avoid conflicting with the main drm module? This is a simple fix that will eventually go away when the drm modules are merged. -- Tobin Davis No matter how old a mother is, she watches her middle-aged children for signs of improvement. -- Florida Scott-Maxwell -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
On Mon, Nov 05, 2007 at 05:39:26PM +0100, Tollef Fog Heen wrote: > * GrueMaster > > | The bigger question is, should the lpia and lpiacompat configurations be > | combined? > > No, they use different versions of drm.ko which are not compatible. I > suspect this will be fixed sometime during the hardy cycle, Amit might > know more. TTM isn't going to land in mainline DRM before Hardy, so a separate DRM is pretty much a necessity. -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
On 11/5/07, Tollef Fog Heen <[EMAIL PROTECTED]> wrote: > * GrueMaster > > | The bigger question is, should the lpia and lpiacompat configurations be > | combined? > > No, they use different versions of drm.ko which are not compatible. I > suspect this will be fixed sometime during the hardy cycle, Amit might > know more. It would be up to Intel. The current Poulsbo DRM driver is based on upsteam DRM. So we disable the in-kernel DRM and use the whole stack from Intel's moblin repository. For Hardy, if Intel agrees to provide a patch against the in-kernel DRM (2.6.24), then we could have a common config. Regards, Amit -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Image issues
* GrueMaster | The bigger question is, should the lpia and lpiacompat configurations be | combined? No, they use different versions of drm.ko which are not compatible. I suspect this will be fixed sometime during the hardy cycle, Amit might know more. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Image issues
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: ubuntu-mobile@lists.ubuntu.com 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 Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
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 Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
