On Wed, 2010-05-26 at 16:10 -0600, Mathieu Poirier wrote:
> >From d9811804ff0a7b6c3aa687c5ec9d0cd2ad7a15a3 Mon Sep 17 00:00:00 2001
> From: Mathieu J. Poirier <firstname.lastname@example.org>
> Date: Wed, 26 May 2010 15:14:08 -0600
> Subject: [PATCH] UBUNTU: ARM: Adding MosChip MCS7830 to nic-usb
> Adding driver for MosChip MCS7830 usb ethernet device. It was also requested
> that module found in the linux-image .deb file also be ported to the nic-usb
> .udeb file, which is also done here.
> BugLink: https://bugs.launchpad.net/bugs/584920
> Signed-off-by: Mathieu Poirier <email@example.com>
> debian.ti-omap/d-i/modules/nic-usb-modules | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
> diff --git a/debian.ti-omap/d-i/modules/nic-usb-modules b/debian.ti-omap/d-i/modules/nic-usb-modules
> index 33b1c11..0934dea 100644
> --- a/debian.ti-omap/d-i/modules/nic-usb-modules
> +++ b/debian.ti-omap/d-i/modules/nic-usb-modules
> @@ -10,4 +10,17 @@ rt2500usb ?
> rt73usb ?
> rt2570 ?
> cdc_ether ?
> +cdc_eem ?
> +cdc-phonet ?
> +cdc_subset ?
> +dm9601 ?
> +gl620a ?
> +hso ?
> +int51x1 ?
> +mcs7830 ?
> +net1080 ?
> +plusb ?
> +rndis_host ?
> +smsc95xx ?
> +zaurus ?
> asix ?
Some of these modules are very esoteric. I doubt anyone is going to try
to install Lucid on a Zaurus (or tethered through a Zaurus, if that's
what the module does) *. Is there pressure on udeb sizes to make us be
concerned about throwing in modules that may never be used, especially
at install time?
For that matter, what networking support is used at install time? I
assume the only purpose is for alternative installs where you do a
network installation. Are people doing these types of installations with
I assume we also won't be respinning an installation image for lucid, so
I'm not sure how useful these changes are for us. Is the mobile team
spinning new installation images?
* I'd give a pile of change to see someone net install lucid through a
tethered Zaurus. Then I'd laugh at the data plan overages incurred
kernel-team mailing list