[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0807141934060.3017@woody.linux-foundation.org>
Date: Mon, 14 Jul 2008 19:39:03 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
cc: rene.herman@...access.nl, david@...g.hm, arjan@...radead.org,
akpm@...ux-foundation.org, dwmw2@...radead.org,
alan@...rguk.ukuu.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,
use it in more drivers.
On Mon, 14 Jul 2008, David Miller wrote:
>
> They states that it was being done on a technical basis rather
> than being predominantly a legal one.
No.
Yes, the original reason for request_firmware() was obviously very much
partly legal.
HOWEVER.
Once you have a model that is required (for whatever reasons) for some
drivers, we're much better off using the _same_ model for all drivers,
whether it is necessary for legal reasons for those other drivers.
Put this way: if you do a distro, you _need_ to support firmware loading
anyway. And once you do that, it's just annoying how some drivers then do
something odd and special for the same thing, for no real good reason.
It's like having each wireless driver do their own 802.11 stack. It works,
and all those driver writers seem to be always convinced that it's the
right thing to do. But as a network maintainer, do you like it?
Now, replace "802.11 stack" with "firmware loader", and then replace
"network maintainer" with "kernel maintainer".
And maybe you can see why I like just making everybody do
request_firmware().
Do you call that a legal reason? Or a technical one?
Linus
--
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/
Powered by blists - more mailing lists