On Tue, Jan 18, 2011 at 12:00:57PM +0000, David Woodhouse wrote:
On Mon, 2011-01-17 at 15:04 +0000, Andy Gospodarek wrote:
>
> It looks like that firmware is in Linus' tree, but somehow it is not in
> Woodhouse's linux-firmware tree. That seems odd.
Yeah, that's just broken. If the driver/firmware ABI changes
incompatibly and the kernel gets updated so that it can no longer use
the older firmware, then driver maintainers *need* to put the new
firmware into the firmware tree so that it actually gets to users.
In this case it looks like they only updated the legacy firmware/
directory in the kernel source itself, that people don't really use any
more and that is going to be going away real soon now. That's not very
useful.
Michael? Did you submit the new firmware for linux-firmware.git and I
just missed it? If so, I apologise; please could you resend?
David,
I seemed to recall that you were initially pulling (just copying with a
cronjob, iirc) files from firmware/ in Linus' tree to your
linux-firmware git tree. That was why I was a bit confused that these
were out of sync.
I see now that the last time you did this was here:
commit 72cf26d513496edfaaf6be7c605dd57f7b44e073
Merge: 2d07c7d 7936fd8
Author: David Woodhouse <David.Woodhouse(a)intel.com>
Date: Fri Aug 6 08:20:09 2010 +0100
Merge legacy kernel source firmware/ directory from 2.6.35
and that explains how we missed the bnx2 firmware changes. Does this
mean you will not be merging from Linus going forward?
Thanks,
-andy