All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] MODULE_FIRMWARE for binary firmware(s)
Date: Wed, 19 Apr 2006 00:41:56 +0100	[thread overview]
Message-ID: <20060418234156.GA28346@apogee.jonmasters.org> (raw)

From: Jon Masters <jcm@redhat.com>

Right now, various kernel modules are being migrated over to use
request_firmware in order to pull in binary firmware blobs from userland
when the module is loaded. This makes sense.

However, there is right now little mechanism in place to automatically
determine which binary firmware blobs must be included with a kernel in
order to satisfy the prerequisites of these drivers. This affects
vendors, but also regular users to a certain extent too.

The attached patch introduces MODULE_FIRMWARE as a mechanism for
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.

Signed-off-by: Jon Masters <jcm@redhat.com>

diff -urN linux-2.6.16.2_orig/include/linux/module.h linux-2.6.16.2_dev/include/linux/module.h
--- linux-2.6.16.2_orig/include/linux/module.h  2006-04-07 17:56:47.000000000 +0100
+++ linux-2.6.16.2_dev/include/linux/module.h   2006-04-12 13:51:56.000000000 +0100
@@ -155,6 +155,8 @@
 */
 #define MODULE_VERSION(_version) MODULE_INFO(version, _version)

+#define MODULE_FIRMWARE(_firmware) MODULE_INFO(firmware, _firmware)
+
 /* Given an address, look for it in the exception tables */
 const struct exception_table_entry *search_exception_tables(unsigned long add);

             reply	other threads:[~2006-04-18 23:49 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 23:41 Jon Masters [this message]
2006-04-18 23:01 ` [PATCH] MODULE_FIRMWARE for binary firmware(s) David Lang
2006-04-19  0:15   ` Jon Masters
2006-04-18 23:41     ` David Lang
2006-04-19  1:07       ` Jon Masters
2006-04-19  9:07 ` Duncan Sands
2006-04-19 12:41   ` Jon Masters
2006-04-19 15:32     ` Duncan Sands
2006-04-19 15:45       ` Jon Masters
2006-07-29 19:05 ` Jon Masters
2006-07-29 19:06 ` Fwd: " Jon Masters
2006-07-29 19:46   ` Sam Ravnborg
2006-08-28 22:08 James Bottomley
2006-08-28 22:11 ` James Bottomley
2006-08-28 23:04   ` Sven Luther
2006-08-28 23:50     ` James Bottomley
2006-08-29  0:35     ` Oleg Verych
2006-08-28 23:55       ` James Bottomley
2006-08-29  2:15         ` Oleg Verych
     [not found]           ` <20060829015103.GA28162@kroah.com>
     [not found]             ` <20060829031430.GA9820@flower.upol.cz>
2006-08-29  2:49               ` Greg KH
2006-08-29  4:19                 ` Oleg Verych
2006-08-29 15:46                 ` David Lang
2006-08-29 18:32                   ` Greg KH
2006-08-29 19:04                     ` Michael Buesch
2006-08-29 20:13                       ` Olaf Hering
2006-08-29 20:42                         ` David Lang
2006-08-29 20:52                           ` Greg KH
2006-08-30  5:44                           ` Olaf Hering
2006-08-30 17:52                             ` David Lang
2006-08-30 18:13                               ` Sven Luther
2006-08-30 18:20                                 ` David Lang
2006-08-30 19:15                                   ` Sven Luther
2006-08-30 19:34                                     ` David Lang
2006-08-30 20:57                                       ` Sven Luther
2006-08-30 21:11                                         ` David Lang
2006-08-31  1:16                                           ` Jim Crilly
2006-09-15 19:48                               ` Olaf Hering
2006-08-29 16:30           ` Michael Buesch
2006-08-29 13:13 ` Marcel Holtmann
2006-08-29 20:16   ` Greg KH
2006-08-30 13:49     ` Marcel Holtmann
     [not found] <6OXsW-4pW-7@gated-at.bofh.it>
     [not found] ` <6Peat-82q-17@gated-at.bofh.it>
     [not found]   ` <6PgFh-53l-7@gated-at.bofh.it>
     [not found]     ` <6Ph8l-61I-9@gated-at.bofh.it>
2006-08-29 22:10       ` Bodo Eggert

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=20060418234156.GA28346@apogee.jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=akpm@osdl.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.