mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Martin Langer <martin-langer@gmx.de>
Cc: linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [RFC][PATCH 1/2] firmware version management: add firmware_version()
Date: Sat, 08 Jul 2006 15:31:54 +0200	[thread overview]
Message-ID: <1152365514.3120.46.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060708130904.GA3819@tuba>

On Sat, 2006-07-08 at 15:09 +0200, Martin Langer wrote:
> It would be good if a driver knows which firmware version will be 
> written to the hardware. I'm talking about external firmware files 
> claimed by request_firmware(). 
> 
> We know so many different firmware files for bcm43xx and it becomes 
> more and more complicated without some firmware version management.
> 
> This patch can create the md5sum of a firmware file. Then it looks into 
> a table to figure out which version number is assigned to the hashcode.
> That table is placed in the driver code and an example for bcm43xx comes 
> in my next mail. Any comments?

Hi,

why does this have to happen on the kernel side? Isn't it a lot easier
and better to let the userspace side of things do this work, and even
have a userspace file with the md5->version mapping? Or are there some
practical considerations that make that hard to impossible?

(I personally don't care if the file comes with the kernel, that may be
the most convenient thing, but it would be a userspace file that the
userspace side of the firmware loader uses)


  reply	other threads:[~2006-07-08 13:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 13:09 Martin Langer
2006-07-08 13:31 ` Arjan van de Ven [this message]
2006-07-08 13:49   ` Marcel Holtmann
2006-07-09 12:21     ` Martin Langer
2006-07-09 13:25       ` Marcel Holtmann
2006-07-09 14:44       ` Michael Buesch
2006-07-09 14:57         ` Marcel Holtmann
2006-07-09 15:00         ` Jon Smirl
2006-07-09 14:51       ` Jon Smirl
2006-07-09 15:01       ` Arjan van de Ven
2006-07-09 15:25         ` Martin Langer
2006-07-09 19:09           ` Michael Buesch
2006-07-09 21:07             ` Arjan van de Ven

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=1152365514.3120.46.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin-langer@gmx.de \
    /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

all inboxes | Powered by JetHome®