linux-kernel - Re: [PATCH] staging/wlan-ng: Convert firmware loading to load binary ihex format

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1250754027.4820.17.camel@localhost>
Date:	Thu, 20 Aug 2009 08:40:27 +0100
From:	Karl Relton <karllinuxtest.relton@...world.com>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/wlan-ng: Convert firmware loading to load
 binary ihex format

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/