Bug#628676: firmware-nonfree: add ti-connectivity firmware

2011-06-05 Thread David Woodhouse
On Sun, 5 Jun 2011, Ben Hutchings wrote: This firmware has a very problematic licence. It actually forbids anyone to download the firmware without agreeing to the licence. We have no way to ask users whether they agree to this before even downloading the package. Do not download this

Bug#628676: firmware-nonfree: add ti-connectivity firmware

2011-06-05 Thread David Woodhouse
On Sun, 5 Jun 2011, Ben Hutchings wrote: In reality every transfer over a network involves many transient copies being made. However, I think that legally only the sender tends to be held responsible for distributing or copying. It was sent to me by TI with the express intention of including

Re: alsa-firmware in firmware-linux-non-free package

2010-10-19 Thread David Woodhouse
assistance to David Woodhouse as I do to you in Debian - willingness to answer questions etc, to make this happen. You are welcome to help me remind him to actually pick these things up. Where do I pick them up from? The git tree referenced above seems to add to a 'WHENCE.ubuntu' file

Bug#553024: [PATCH 1/2] phylib: Support phy module autoloading

2010-04-02 Thread David Woodhouse
s/PHY_ID_BCMAC131/0x0143bc70/ in the patch to broadcom.c, because 2.6.32 didn't have a definition for that. There's also trivial change in phy_device_create() which will make the patch fail to apply, but git-cherry-pick copes. -- David WoodhouseOpen Source Technology

Bug#553024: [PATCH 1/2] phylib: Support phy module autoloading

2010-04-02 Thread David Woodhouse
On Thu, 2010-04-01 at 05:34 +0100, Ben Hutchings wrote: --- a/drivers/net/phy/phy_device.c +++ b/drivers/net/phy/phy_device.c @@ -188,7 +188,7 @@ struct phy_device* phy_device_create(struct mii_bus *bus, int addr, int phy_id) around for long enough for the driver to get loaded. With

Bug#553024: [PATCH 1/2] phylib: Support phy module autoloading

2010-04-01 Thread David Woodhouse
On Thu, 2010-04-01 at 05:34 +0100, Ben Hutchings wrote: On Wed, 2010-03-31 at 02:18 +0100, David Woodhouse wrote: We don't use the normal hotplug mechanism because it doesn't work. It will load the module some time after the device appears, but that's not good enough for us -- we need

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Tue, 2009-10-27 at 20:40 +0100, maximilian attems wrote: hello David, I have a question on howto ship firmware build out of make deb-pkg in linux-2.6. On Mon, 26 Oct 2009, Ben Hutchings wrote: On Mon, 2009-10-26 at 21:27 +0100, Marc Haber wrote: Hi, Is it a feature

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Wed, 2009-10-28 at 10:48 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need for it -- the firmware should live in /lib/firmware. If there are incompatible versions of firmware, then they'll have a different

Re: Building vanilla kernel .debs

2009-10-28 Thread David Woodhouse
On Wed, 2009-10-28 at 11:31 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 10:17:52AM +, David Woodhouse wrote: On Wed, 2009-10-28 at 10:48 +0100, Marc Haber wrote: On Wed, Oct 28, 2009 at 07:30:47AM +, David Woodhouse wrote: That's intentional. There is no need