> -----Original Message-----
> From: Michael Chan [mailto:mc...@broadcom.com]
> Sent: Tuesday, January 18, 2011 12:04 PM
> To: David Woodhouse
> Cc: Andy Gospodarek; Development discussions related to Fedora; Iyer,
> Shyam; KM, Paniraja; jla...@redhat.com; Rose, Charles
> Subject: Re: bnx2 driver fails to load on Fedora Rawhide
> 
> 
> On Tue, 2011-01-18 at 04:00 -0800, 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?
> >
> 
> Sorry, I didn't know about the linux-firmware git tree.  I'll re-submit
> the missing firmware files shortly.  Thanks.
> 

Michael/David - Have we resolved the issue here? We would very much like fedora 
rawhide to be fixed before the Linux Nic Naming problem testday which has been 
long standing problem in Linux. We don't want this merge issue to be blocking 
the testing on the testday, Jan 27th 2011.
http://lists.fedoraproject.org/pipermail/devel/2011-January/148023.html

As I understand the sequence of events- 
1) Michael to post patches to linux-firmware tree
2) David to build linux-firmware rpm with Michael's patches for fedora rawhide.
Let me know if this incorrect.

Shyam Iyer
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to