From: Arjan van de Ven <arjan@infradead.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Martin Langer <martin-langer@gmx.de>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [RFC][PATCH 1/2] firmware version management: add firmware_version()
Date: Sun, 09 Jul 2006 23:07:53 +0200 [thread overview]
Message-ID: <1152479273.3255.67.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200607092109.02707.mb@bu3sch.de>
On Sun, 2006-07-09 at 21:09 +0200, Michael Buesch wrote:
> On Sunday 09 July 2006 17:25, you wrote:
> > > yes it does. bcm43xx asks userspace to upload firmware (via
> > > request_firmware() ) and a userspace app (udev most of the time) will
> > > upload it. That app, eg udev, can do the md5sum and checking it against
> > > a list of "known good" firmwares. Voila problem solved ;)
> >
> > I see. It's an interesting way that I didn't noticed.
> > Thanks for the guidance.
>
> Nono, stop. Not too fast. :)
> Where is this "list of "known good" firmwares" actually stored?
> In userspace (udev)? That would be guaranteed to be out of sync
> with the driver.
for all I care it's part of the kernel tarbal somehow
but a real file, not some in kernel memory eating thing
prev parent reply other threads:[~2006-07-09 21:08 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
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 [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=1152479273.3255.67.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=martin-langer@gmx.de \
--cc=mb@bu3sch.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®