Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,use it in more drivers.

From: david
Date: Tue Jul 15 2008 - 01:45:15 EST


On Mon, 14 Jul 2008, David Woodhouse wrote:

On Mon, 2008-07-14 at 21:56 -0700, Arjan van de Ven wrote:
On Mon, 14 Jul 2008 19:45:57 -0700 (PDT)
David Miller <davem@xxxxxxxxxxxxx> wrote:

From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 14 Jul 2008 19:39:03 -0700 (PDT)

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.

In what way is it annoying?

Most distribution people aren't even aware that drivers like tg3 and
bnx2 even have firmware. In fact it's self contained and less for
them to worry about.

and.. after this patch that still seems to be the case, unless I'm
looking at it really cross eyed.
Nothing in this patch makes it impossible to do so.. or changes the
drivers you mention.

Well, the HEAD of my tree (and linux-next) does change tg3. I just
haven't asked Linus to pull that part, because I wanted to keep the
contentious part separate from the simple and obvious parts.

(Even though the tg3 fix _is_ simple and obvious, to me. But that
evidently doesn't stop it from being contentious too. So it can wait.)

a techinical question here (I know, how dare I ask a technical question in the middle of the flamefest ;-)

linus pointed out that the documentation reccomended the
request_firmware();load_firmware();release() approach and stated that that approach was the wrong way to do things, instead doing a request_firmware early and release when the module is unloaded.

does this patch series follow the documented reccomendation? or does it follow the more concervative approach Linus pointed out? (it's far faster to ask then to search Internet archives for the patches)

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