Message ID | 20130321220931.GA30668@luxor.wired.org |
---|---|
State | New |
Headers | show |
On Thu, Mar 21, 2013 at 11:09:31PM +0100, Paolo Pisati wrote: > > The following changes since commit 605d3f768f6d9d65980eab000ed45de981e9a9af: > > UBUNTU: [Config] CONFIG_SERIAL_8250_DW=m across all arches (2013-03-20 07:13:58 -0600) > > are available in the git repository at: > > git://kernel.ubuntu.com/ppisati/ubuntu-raring.git master_omaprename > > for you to fetch changes up to 3e9a1bce8b6683eb540d8a77a709ba5bc773f07c: > > UBUNTU: [Config] rename omap flavour to generic (2013-03-21 18:35:05 +0000) one of the side effects that i noticed renaming 'omap' to 'generic' is that modules are split between linux-image and linux-image-extra, so we either: 1) pull in both packages during the upgrade or 2) disable this split for arch == armhf in case we pick 1, i want to do some adjusments (i want some vital modules to be part of linux-image - but in this case it'll inflate linux-image for x86 too), while in case 2, someone needs to help me find the exact spot where this rule is applied. Personally i would prefer 2 if it's possible without much hurdle. Let me know.
On 03/22/2013 05:46 AM, Paolo Pisati wrote: > On Thu, Mar 21, 2013 at 11:09:31PM +0100, Paolo Pisati wrote: >> >> The following changes since commit 605d3f768f6d9d65980eab000ed45de981e9a9af: >> >> UBUNTU: [Config] CONFIG_SERIAL_8250_DW=m across all arches (2013-03-20 07:13:58 -0600) >> >> are available in the git repository at: >> >> git://kernel.ubuntu.com/ppisati/ubuntu-raring.git master_omaprename >> >> for you to fetch changes up to 3e9a1bce8b6683eb540d8a77a709ba5bc773f07c: >> >> UBUNTU: [Config] rename omap flavour to generic (2013-03-21 18:35:05 +0000) > > one of the side effects that i noticed renaming 'omap' to 'generic' is that modules > are split between linux-image and linux-image-extra, so we either: > > 1) pull in both packages during the upgrade > > or > > 2) disable this split for arch == armhf > > in case we pick 1, i want to do some adjusments (i want some vital modules to be > part of linux-image - but in this case it'll inflate linux-image for x86 too), > while in case 2, someone needs to help me find the exact spot where this rule is > applied. > > Personally i would prefer 2 if it's possible without much hurdle. > > Let me know. > Option 2 it is.