[Precise,LBM,and,linux-meta,Pull-Requests] UBUNTU: Add v3.7 and v3.8 compat-wireless stacks

Message ID cover.1365229631.git.leann.ogasawara@canonical.com
State New
Headers show


git://kernel.ubuntu.com/ogasawara/ubuntu-precise-meta.git lp1165111


Leann Ogasawara April 6, 2013, 7:24 a.m. UTC
From: Leann Ogasawara <leann.ogasawara@canonical.com>

BugLink: http://bugs.launchpad.net/bugs/1165084
BugLink: http://bugs.launchpad.net/bugs/1165111

== Precise SRU Justification ==
We currently provide updated compat-wireless stacks for Precise via LBM.
This gives users access to updated or newer wireless drivers while
remaining under the umbrella of the LTS release.  The v3.7 and v3.8
compat wireless stacks are now available.  We should provide them in LBM
for Precise.

== Impact ==
LBM is an elective install so there shouldn't be any potential for
regression. For those who do choose to install, it will provide an
updated v3.7 or v3.8 compat wireless stack.

==Fix ==
The compat-wireless snapshots were manually created by first following
the steps documented at:


Which are based on the following:

linux-stable: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git v3.7.9
compat: https://github.com/mcgrof/compat.git compat-v3.7.9-1
compat-drivers: git://github.com/mcgrof/compat-drivers.git compat-drivers-v3.7.9-1


linux-stable: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git v3.8.3
compat: https://github.com/mcgrof/compat.git compat-v3.8.3-1
compat-drivers: git://github.com/mcgrof/compat-drivers.git compat-drivers-v3.8.3-2

Manual creation was done because the compat-drivers archive isn't
current.  ie. http://www.orbit-lab.org/kernel/compat-drivers/ is out of
date.  Also, adding a v3.7 compat-wireless snapshot is a slightly
different process than what we've been able to do in the past.  There
now exists a compat-drivers framework which provides updates to multiple
different subsystems (eg. ethernet, wireless, bluetooth, drm).  By
default, all sybsystems are built.  Generating the compat-drivers
snapshot is a well documented process and easily reproducible (ie easy to
replicate for v3.8 and onward).  Then it is just a matter of modifying
the Makefile to reduce the build targets to just the wireless related

I'd appreciate a closer review to make sure this looks correct.  I have
have build tested each of these on both amd64 and i386.  I have also
tested installation on amd64 and i386 machines which both utilized the
iwlwifi driver.  I can confirm the updated iwlwifi driver from both the
v3.7 and v3.8 stacks were installed and operated as expected.  I also
built and install tested the meta package changes as well.

The following changes since commit ba8d3198edb75ef18eed5af6ff2e8294e4fc493e:

  UBUNTU: Ubuntu-3.2.0-40.27 (2013-03-20 17:53:54 -0500)

are available in the git repository at:

  git://kernel.ubuntu.com/ogasawara/ubuntu-precise-lbm.git lp1165111

for you to fetch changes up to fb32af3405e762280c96f5c272c9592069306073:

  UBUNTU: Restrict v3.8 compat-drivers to only build wireless targets (2013-04-05 23:55:09 -0700)

Leann Ogasawara (4):
      UBUNTU: Add compat-drivers v3.7
      UBUNTU: Restrict v3.7 compat-drivers to only build wireless targets
      UBUNTU: Add compat-drivers v3.8
      UBUNTU: Restrict v3.8 compat-drivers to only build wireless targets

I have also prepared a corresponding patches for linux-meta: 

The following changes since commit c84673c8a67fbe6d2e8a4cceac55c8b17eb76f09:

  UBUNTU: Ubuntu- (2013-03-20 17:29:38 -0500)

are available in the git repository at:

  git://kernel.ubuntu.com/ogasawara/ubuntu-precise-meta.git lp1165111

for you to fetch changes up to 3883cc8c854d23a9d483834448506dc7ce0af831:

  UBUNTU: Add compat-wireless v3.8 meta package (2013-04-05 10:41:18 -0700)

Leann Ogasawara (2):
      UBUNTU: Add compat-wireless v3.7 meta package
      UBUNTU: Add compat-wireless v3.8 meta package


Tim Gardner April 6, 2013, 3:09 p.m. UTC | #1
What the h*ll are you doing working so late on a Friday night ? 12:30AM
? Don't you have better things to do ?

I wonder if we should consider publishing some of the other drivers. A
refresh of net-3.8 wouldn't hurt. We could also publish a drm-3.8 and a
platform-3.8 (upon which net-3.8 would depend).

I noticed that though we produce a cw-3.x-virtual, there is no
corresponding meta package. I think since nobody has howled about their
-virtual package flavours not being updated that we can likely just stop
producing them.

I also noticed that there are no Conflicts: statements in precise-lbm
like there are in lucid-lbm. I believe they are necessary in order to
prevent first order stupidity.