Re: psb.ko module
* Ben Collins | On Mon, 2007-10-01 at 15:29 -0700, Matt Zimmerman wrote: | On Mon, Oct 01, 2007 at 11:11:27PM +0100, Colin Watson wrote: | On Mon, Oct 01, 2007 at 12:00:11PM -0700, Johnson, Charles F wrote: |Did the upload, where the missing psb.ko module was included in the lpia |kernel, occur ?? | | No, it's still only in git. The best group to contact about this would | be the Ubuntu kernel team. | | Escalating to Ben, as this bug was reported 5 days ago and is a severe | blocker for mobile builds. | | https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/147792 | | We planned an upload for Friday, but that was delayed over till today. It's quite important that when this happens, you tell us so we can communicate this to Intel and the mobile list. [...] | Perhaps Amit can get you a build of the flavor you need, that can be | wedged into the mobile build for immediate testing. Would this get | things going until the upload? We have an explicit policy of having the daily images be built from the archive and nothing else, I would not want this to change. Also, the problem here isn't that I can't work around psb.ko being broken, but rather that the dailies have been broken for quite a while due to the kernel being uploaded too seldomly. At UDS, I'd like us to discuss how we can prevent this problem in the future. -- 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: Moblin and Gnome
On Fri, Sep 21, 2007 at 02:36:04PM -0400, Pat McGowan wrote: When custom versions of gnome based components are created, is it the intention to manage these as patches upstream in gnome, for example in the gnome mobile project? If not, what is the plan to sync these customizations with upstream changes? As far as development in Ubuntu goes, our intention is to merge upstream anything which can be reasonably generalized. Regarding the Moblin components derived from GNOME, I believe Todd Brandt is the person to ask about their plans. Hopefully the changes can be merged upstream (maybe with a --with-hildon configure option or similar). -- - mdz -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: psb.ko module
On Wed, 2007-10-03 at 10:15 +0200, Tollef Fog Heen wrote: * Ben Collins | On Mon, 2007-10-01 at 15:29 -0700, Matt Zimmerman wrote: | On Mon, Oct 01, 2007 at 11:11:27PM +0100, Colin Watson wrote: | On Mon, Oct 01, 2007 at 12:00:11PM -0700, Johnson, Charles F wrote: |Did the upload, where the missing psb.ko module was included in the lpia |kernel, occur ?? | | No, it's still only in git. The best group to contact about this would | be the Ubuntu kernel team. | | Escalating to Ben, as this bug was reported 5 days ago and is a severe | blocker for mobile builds. | | https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/147792 | | We planned an upload for Friday, but that was delayed over till today. It's quite important that when this happens, you tell us so we can communicate this to Intel and the mobile list. [...] | Perhaps Amit can get you a build of the flavor you need, that can be | wedged into the mobile build for immediate testing. Would this get | things going until the upload? We have an explicit policy of having the daily images be built from the archive and nothing else, I would not want this to change. Also, the problem here isn't that I can't work around psb.ko being broken, but rather that the dailies have been broken for quite a while due to the kernel being uploaded too seldomly. At UDS, I'd like us to discuss how we can prevent this problem in the future. We explicitly decided to do this, and in part were forced into it. We have about an 8 day window to do uploads in a 2-week (milestone-to-milestone) period. Usually that allows us one upload. every milestone. A lot of projects are expecting regular kernel side changes: server team (xen, apparmor, etc), sparc port, IHV's, UME...and the list keeps expanding. Everyone wants a little bit fixed/added/developed in each kernel upload. Coordinating that so that each project benefits in every upload is a task in itself. I think the best way to overcome this is to have a set kernel development schedule for the release, with relative dates bound by milestones, freezes, and other dates on the main release schedule. I think keeping the projects informed about what they can expect from the kernel, and how they need to interact with the kernel team for their schedules, would benefit all. I already have a planned UDS agenda item for this. The UME project's input would be greatly appreciated at this meeting. -- Ubuntu : http://www.ubuntu.com/ Linux1394: http://wiki.linux1394.org/ SwissDisk: http://www.swissdisk.com/ -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
IRC meeting reminder, 2007-10-04, 1600 UTC
Hi, we'll be having the IRC meeting on #ubuntu-mobile, as usual, tomorrow. Please make sure to post status reports to this list before 1400 UTC, and if you have agenda items, please add them to the list on https://wiki.ubuntu.com/MobileAndEmbedded/Meeting . -- 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: Moblin and Gnome
I believe for Network Admin and Date/Time settings, Todd was planning on providing a patch to gnome-system-tools for the UI changes necessary for running in the hildon environment. But I'm not sure about all of the other control panel applets. Todd, does it make sense to do this for all the control-panel applets so that it's easier to stay in sync with upstream, rather than forking and having the code live in moblin? On Oct 3, 2007, at 8:17 AM, Matt Zimmerman wrote: On Fri, Sep 21, 2007 at 02:36:04PM -0400, Pat McGowan wrote: When custom versions of gnome based components are created, is it the intention to manage these as patches upstream in gnome, for example in the gnome mobile project? If not, what is the plan to sync these customizations with upstream changes? As far as development in Ubuntu goes, our intention is to merge upstream anything which can be reasonably generalized. Regarding the Moblin components derived from GNOME, I believe Todd Brandt is the person to ask about their plans. Hopefully the changes can be merged upstream (maybe with a --with-hildon configure option or similar). -- - mdz -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
RE: Moblin and Gnome
Bill Filler wrote: I believe for Network Admin and Date/Time settings, Todd was planning on providing a patch to gnome-system-tools for the UI changes necessary for running in the hildon environment. But I'm not sure about all of the other control panel applets. Todd, does it make sense to do this for all the control-panel applets so that it's easier to stay in sync with upstream, rather than forking and having the code live in moblin? In the short term the UI changes are minimal while we get our feet on the ground, but eventually there might be radical changes. For example, the standard Linux keyboard configuration tool might have 40 options today while a simplified MID UI might only expose 5. In another world, I looked at Claws for the first time with the new LPIA build. It is so cluttered with controls and menus that it makes my MID feel very small. I agree with Matt that we should always attempt to push changes upstream. Non-UI changes seem like a no-brainer. In time upstream component owners might have to decide if they want to support a Hildon-esque UI in addition to their standard UI which could be more than a few #define's. Lastly, perhaps we could agree on some standards for branching existing projects. For example #ifdef tag, for code, Makefile.am, configure.in, etc. Then we could easily go to a project and find where/if someone else had added mobile-device-specific changes. tag = MID or UME or HILDON or MOBILE (My vote is MID) Bob On Oct 3, 2007, at 8:17 AM, Matt Zimmerman wrote: On Fri, Sep 21, 2007 at 02:36:04PM -0400, Pat McGowan wrote: When custom versions of gnome based components are created, is it the intention to manage these as patches upstream in gnome, for example in the gnome mobile project? If not, what is the plan to sync these customizations with upstream changes? As far as development in Ubuntu goes, our intention is to merge upstream anything which can be reasonably generalized. Regarding the Moblin components derived from GNOME, I believe Todd Brandt is the person to ask about their plans. Hopefully the changes can be merged upstream (maybe with a --with-hildon configure option or similar). -- - mdz -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/ listinfo/ubuntu-mobile -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
Re: Moblin and Gnome
I agree with Matt that we should always attempt to push changes upstream. Non-UI changes seem like a no-brainer. In time upstream component owners might have to decide if they want to support a Hildon-esque UI in addition to their standard UI which could be more than a few #define's. I would think (hope) in the case of GNOME, they would be very interested in the hildonized mobile ui for some of their components, as they have commited to support GNOME Mobile http:// www.gnome.org/mobile/. That project looks like it's still very early stage, but we should certainly coordinate with them as it sounds like it's inline with our vision. Lastly, perhaps we could agree on some standards for branching existing projects. For example #ifdef tag, for code, Makefile.am, configure.in, etc. Then we could easily go to a project and find where/if someone else had added mobile-device-specific changes. tag = MID or UME or HILDON or MOBILE (My vote is MID) Bob I agree. Maybe you guys could post on the GNOME mobile list (mobile- [EMAIL PROTECTED]) to propose some of these ideas. -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
