From: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "wimax@linuxwimax.org" <wimax@linuxwimax.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: WiMAX linux firmware pull request
Date: Tue, 28 Sep 2010 21:27:45 -0700 [thread overview]
Message-ID: <1285734465.3136.339.camel@localhost.localdomain> (raw)
In-Reply-To: <1285728768.814.74.camel@macbook.infradead.org>
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 :)
prev parent reply other threads:[~2010-09-29 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 18:46 WiMAX linux firmware pull request Inaky Perez-Gonzalez
2010-09-29 2:52 ` David Woodhouse
2010-09-29 4:27 ` Inaky Perez-Gonzalez [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=1285734465.3136.339.camel@localhost.localdomain \
--to=inaky.perez-gonzalez@intel.com \
--cc=dwmw2@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=wimax@linuxwimax.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;
as well as URLs for NNTP newsgroup(s).