public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael D. Setzer II" <msetzerii@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Firmware Support
Date: Tue, 07 May 2013 14:56:29 +1000	[thread overview]
Message-ID: <5188897D.15662.1AD368@msetzerii.gmail.com> (raw)
In-Reply-To: <20130507024750.GA26639@kroah.com>

On 6 May 2013 at 19:47, Greg KH wrote:

Date sent:      	Mon, 6 May 2013 19:47:50 -0700
From:           	Greg KH <gregkh@linuxfoundation.org>
To:             	"Michael D. Setzer II" <msetzerii@gmail.com>
Copies to:      	linux-kernel@vger.kernel.org
Subject:        	Re: Kernel Firmware Support

> On Tue, May 07, 2013 at 11:44:42AM +1000, Michael D. Setzer II wrote:
> > Looking for method to best support users firmware needs within 
> > the kernel. 
> > 
> > Have a disk-image project that users kernel.org kernels, and have 
> > had users that require firmware that is not included in the 
> > kernel.org source. I've been able to find it in linux-firmware.git and 
> > then manually adding it to the kernel.org firmware directory and 
> > then modifying the Makefile.
> 
> Use the linux-firmware package, all of the distros package it up for you
> automatically, and install it in the correct place, so it should "just
> work".
> 
> What is failing for you when you use the firmware package?
> 

First, Thanks for the quick reply. The problem is this isn't using a 
distro build. My project (G4L) uses a number of kernels from 
kernel.org and I try to include as many of the nic and other 
devices in the kernel to make it support hardware that is outside 
my control. I've had users with bnx2x hardware that requires 
firmware that is not part of the kernel.org source code, and have 
manuaully added it by putting the .fw file in the subdirectory of 
firmware and modifying the Makefile. Then building the kernel 
includes that additional firmware in the about 8M kernel file that 
the user selects from the CD boot process. 

The ideal is to be able to boot from the cd, or load the kernel with 
its filesystem to be able to do partition or disk image backups, but 
it must be able to use the hardware to access the disks and in 
most cases the nic. Without the firmware these bnx2x nics don't 
work.

For awhile I've been manually adding these two firmwares
./bnx2x/bnx2x-e2-7.2.51.0.fw
./bnx2/bnx2-mips-09-6.2.1b.fw

But yesterday, I got a message from a different user with screen 
captures that showed  failure of loading the firmware below. 
Actually, one screen shot with the 7.0.23.0 and another with the 
7.0.29.0. Wasn't sure, so I had added all three of th 7.0.x group to 
a test build of my kernels. Is only the latest needed?

./bnx2x/bnx2x-e1h-7.0.23.0.fw
./bnx2x/bnx2x-e1h-7.0.29.0.fw
./bnx2x/bnx2x-e1h-7.0.20.0.fw

I don't have access to any hardware with these bnx2? devices, so 
have to get feedback from users. The previous additions of 
firmware solved the problems, but just looking for the best way to 
solve it.

Thanks again.





> thanks,
> 
> greg k-h


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes@kuentos.guam.net                            
  mailto:msetzerii@gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
SETI        14672667.574611   |   EINSTEIN    11160884.209852
ROSETTA      7189167.439443   |   ABC         15954188.106838


  reply	other threads:[~2013-05-07  4:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  1:44 Kernel Firmware Support Michael D. Setzer II
2013-05-07  2:47 ` Greg KH
2013-05-07  4:56   ` Michael D. Setzer II [this message]
2013-05-07 17:20     ` Greg KH
2013-05-10  4:30       ` Michael D. Setzer II
2013-05-10  6:17       ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5188897D.15662.1AD368@msetzerii.gmail.com \
    --to=msetzerii@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox