From: Karl Relton <karllinuxtest.relton@ntlworld.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/wlan-ng: Convert firmware loading to load binary ihex format
Date: Thu, 20 Aug 2009 08:40:27 +0100 [thread overview]
Message-ID: <1250754027.4820.17.camel@localhost> (raw)
In-Reply-To: <20090819181426.GA12827@kroah.com>
On Wed, 2009-08-19 at 11:14 -0700, Greg KH wrote:
> On Wed, Aug 19, 2009 at 06:39:09PM +0100, Karl Relton wrote:
> > On Wed, 2009-08-19 at 09:34 -0700, Greg KH wrote:
> > > On Wed, Aug 19, 2009 at 05:20:51PM +0100, Karl Relton wrote:
> > > > I plan to give the various distributions a utility to pre-compile the
> > > > firmware. It is based on ihex2fw.c.
> > > >
> > > > I don't think the firmware will ever be accepted into linux-firmware
> > > > because the original licensing cannot be established.
> > >
> > > Have you asked the company?
> > > Where is the firmware at today?
> > >
> >
> > At some point in the past the owner was Conexant, but we are not sure
> > they still own in. Some efforts to track down which company now owns
> > this firmware, and who the contact within that company would be, have
> > been made but have not been successful.
> >
> > The firmware is downloadable from the linux-wlan-ng project. I have been
> > liasing with the maintainer in that project, who has tried to help as
> > far as he could.
>
> Ok, I'm just worried that if I take this change, then users whose
> systems were working, will now break. So, why would this change
> actually help anyone out?
>
I think the change will negatively effect very few users to be honest -
since driver firmware loading was only introduced in .31 anyway. I doubt
if any distributions have arranged to install the srec firmware file
in /lib/firmware to coincide with the .31 kernel release. Currently
users (and distributions) use the old user-space utility that squirts
the firmware at the driver via an ioctl, and I'm sure it will stay that
way for users in the near future.
Once we have binary fw loading heading for mainline, I will start
working with distributions so that if they have scripts/packages to make
the firmware available, they should use the new pre-compiler and put the
result in /lib/firmware, to align with the .32 kernel.
The eventual advantage is a lighter weight firmware file (one third the
size), and slightly quicker runtime processing and hence faster startup
time (e.g. system boot). Thats the reasoning people gave me when they
heard the driver was doing srec loading.
Cheers
Karl
prev parent reply other threads:[~2009-08-20 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 7:06 [PATCH] staging/wlan-ng: Convert firmware loading to load binary ihex format Karl Relton
2009-08-19 15:44 ` Greg KH
2009-08-19 16:20 ` Karl Relton
2009-08-19 16:34 ` Greg KH
2009-08-19 17:39 ` Karl Relton
2009-08-19 18:14 ` Greg KH
2009-08-20 7:40 ` Karl Relton [this message]
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=1250754027.4820.17.camel@localhost \
--to=karllinuxtest.relton@ntlworld.com \
--cc=greg@kroah.com \
--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