mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [PATCH] MODULE_FIRMWARE for binary firmware(s)
Date: Sat, 29 Jul 2006 21:46:25 +0200	[thread overview]
Message-ID: <20060729194625.GA10459@mars.ravnborg.org> (raw)
In-Reply-To: <35fb2e590607291206o2c25d3el704942e77ca98f62@mail.gmail.com>

On Sat, Jul 29, 2006 at 08:06:14PM +0100, Jon Masters wrote:
> ---------- Forwarded message ----------
> From: Jon Masters <jonathan@jonmasters.org>
> Date: Apr 19, 2006 12:41 AM
> Subject: [PATCH] MODULE_FIRMWARE for binary firmware(s)
> To: akpm@osdl.org, linux-kernel@vger.kernel.org
> 
> 
> 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.
NAK.
Please provide some inline documentation so users knows how it is
supposed to be used etc. See MODULE_VERSION as an example.
Changelog comments is not enough documentation.

	Sam

      reply	other threads:[~2006-07-29 19:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 23:41 Jon Masters
2006-04-18 23:01 ` 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 [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=20060729194625.GA10459@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome