All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] binary firmware and modules
Date: Tue, 18 Apr 2006 16:25:27 +0200	[thread overview]
Message-ID: <1145370327.10255.62.camel@localhost> (raw)
In-Reply-To: <35fb2e590604180616r33a05380p65c0e1c26ae276de@mail.gmail.com>

Hi Jon,

> > The attached patch introduces MODULE_FIRMWARE as one way of advertising
> > that a particular firmware file is to be loaded - it will then show up
> > via modinfo and could be used e.g. when packaging a kernel. I've also
> > given an example via the QLogic gla2xxx driver.
> 
> Ok. If nobody shouts today I'm going to suggest this go into 2.6.17. I
> think more ellaborate schemes will come up later, but we also need
> something usable out there now.

I like to see this in 2.6.17, too. I also think that it would be a good
idea if we can add a description to each firmware file. Like we do with
the module parameters.

> As others have pointed out, cunning schemes to hack how
> request_firmware et al work are all very well and good, but often we
> just don't know what firmware we'll need until runtime. Unless or
> until there's a good way to address that, I think modules will need to
> advertise every firmware and distros will have to package all possible
> firmwares, just in case.

And remember that request_firmware() is also used for overriding CIS
tables for PCMCIA cards.

Regards

Marcel



      parent reply	other threads:[~2006-04-18 14:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15  8:10 [RFC] binary firmware and modules Jon Masters
2006-04-15  9:54 ` Oliver Neukum
2006-04-17 14:22   ` John W. Linville
2006-04-17 14:29     ` Arjan van de Ven
2006-04-17 14:38       ` Marcel Holtmann
2006-04-17 15:15       ` Duncan Sands
2006-04-17 16:10         ` Marcel Holtmann
2006-04-18 13:16 ` Jon Masters
2006-04-18 13:37   ` Duncan Sands
2006-04-18 14:14     ` Jon Masters
2006-04-18 15:14       ` Duncan Sands
2006-04-19  0:01         ` Jon Masters
2006-04-18 14:22     ` Marcel Holtmann
2006-04-18 14:59       ` Duncan Sands
2006-04-18 15:41         ` Marcel Holtmann
2006-04-19 13:28           ` Mark Lord
2006-04-19 13:37             ` Marcel Holtmann
2006-04-19 14:10               ` Jon Masters
2006-04-18 14:25   ` Marcel Holtmann [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=1145370327.10255.62.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.