From: Arjan van de Ven <arjan@infradead.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: venu <vjosyula@gmail.com>, Roland Dreier <rdreier@cisco.com>,
Philip Downer <phil@csldevices.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: firmware loading interface
Date: Sat, 14 Nov 2009 10:29:19 -0800 [thread overview]
Message-ID: <20091114102919.54606831@infradead.org> (raw)
In-Reply-To: <51f3faa70911141019y1248fb27k5f7edb3729f72375@mail.gmail.com>
On Sat, 14 Nov 2009 12:19:13 -0600
Robert Hancock <hancockrwd@gmail.com> wrote:
> On Sat, Nov 14, 2009 at 10:55 AM, venu <vjosyula@gmail.com> wrote:
> > who triggers this upgrade from userspace ? I understand it is a
> > naivee / beginers questions but i hope somebody explains me how ?
>
> The request_firmware interface probably isn't suitable for that..
> using an ioctl or read/write-based interface, possibly on a separate
> device node, would likely be the way to go..
>
it's not unusual to have a sysfs attribute that, when written to, will
just do a request_firmware().
It's not pretty, but it's cleaner than the alternatives....
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-11-14 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AFD971C.3090204@csldevices.co.uk>
2009-11-13 17:47 ` Philip Downer
2009-11-13 19:29 ` Arnd Bergmann
[not found] ` <53ea87da0911140951q1050212fwe9f5839b900b3804@mail.gmail.com>
2009-11-14 17:54 ` Arnd Bergmann
2009-11-16 10:57 ` Philip Downer
2009-11-14 0:35 ` Roland Dreier
2009-11-14 16:08 ` Robert Hancock
[not found] ` <53ea87da0911140855u7993989aod746bcaf18ee4c31@mail.gmail.com>
2009-11-14 18:19 ` Robert Hancock
2009-11-14 18:29 ` Arjan van de Ven [this message]
2009-11-16 11:16 ` Philip Downer
2009-12-01 9:14 ` Dmitry Torokhov
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=20091114102919.54606831@infradead.org \
--to=arjan@infradead.org \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@csldevices.co.uk \
--cc=rdreier@cisco.com \
--cc=vjosyula@gmail.com \
/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®