public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Downer <phil@csldevices.co.uk>
To: linux-kernel@vger.kernel.org
Subject: firmware loading interface
Date: Fri, 13 Nov 2009 17:47:27 +0000	[thread overview]
Message-ID: <4AFD9BAF.1010200@csldevices.co.uk> (raw)
In-Reply-To: <4AFD971C.3090204@csldevices.co.uk>

Hi,

I'm working for a company which is manufacturing a new pci card. The
details are probably irrelevant at this stage, but for those who might
be concerned the driver will be covered by the GPL and submitted
upstream at or before the launch of the card.

Currently I'm investigating how to provide firmware upgrades for the
card, and I've been looking at the request_firmware api. All of the
documentation (and mails that I've read from lkml archives) suggest that
request_firmware is for use with devices without firmware stored in
flash or eeprom, and to load it in to memory at initialisation of the
device.

However our device will have flash to store the firmware in and, whilst
it looks as though it would be possible for us to use request_firmware
to provide occasional firmware upgrades from userspace, I can't find any
reference as to whether this is an accepted method for doing so. Could
someone please confirm for me whether or not it's a good idea to use
request_firmware for this, or perhaps point me at another standard
method for doing firmware updates from userspace?

Please note that I am not subscribed to this mailing list, so could
anyone responding please CC me in their response.

Philip Downer



       reply	other threads:[~2009-11-13 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 [this message]
2009-11-13 19:29   ` firmware loading interface 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
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=4AFD9BAF.1010200@csldevices.co.uk \
    --to=phil@csldevices.co.uk \
    --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