netdev - Re: WiMAX linux firmware pull request

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1285734465.3136.339.camel@localhost.localdomain>
Date:	Tue, 28 Sep 2010 21:27:45 -0700
From:	Inaky Perez-Gonzalez <inaky.perez-gonzalez@...el.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	"wimax@...uxwimax.org" <wimax@...uxwimax.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: WiMAX linux firmware pull request

On Tue, 2010-09-28 at 19:52 -0700, David Woodhouse wrote: 
> On Tue, 2010-09-28 at 11:46 -0700, Inaky Perez-Gonzalez wrote:    
> >    The 1.3 version is purged as it is not supported anymore.
> 
> Not supported by newer kernels? Or "if you are using something that
> requires the 1.3 firmware, you can just fuck off and die", along the
> lines of what we say to users of the 2.4 kernel?

Along those lines -- basically 1.3 was an experimental release and if
you have that firmware, you won't be able to connect to anything than a
very specific test setup in a lab. The code is still there because it is
just two perfectly isolated paths (if curious, check what goes with the
i2400m_le_v1_3() test) that I forgot to excise out.

> We shouldn't drop stuff from linux-firmware.git until there really is
> *no* reason to need it any more. We shouldn't force people to keep
> linux-firmware in step with their kernel; they should always be able to
> use the latest.

Yes, I am aware of that. That's why 1.4 is kept there -- 1.3 is an
special case because as I said above, it can't be used in the real world
of WiMAX, 

> When I get home from Tokyo I'll be working on a way to specify min/max
> kernel versions for each firmware image, along with a 'make install'
> target which lets you say "drop anything which is only relevant to
> kernels < 2.6.35' or whatever.

That looks pretty sensible :)



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html