All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: request_firmware() backport to 2.4
Date: 25 Aug 2003 14:22:46 +0200	[thread overview]
Message-ID: <1061814172.973.130.camel@pegasus> (raw)

Hi Marcelo,

I have collected the patches for the request_firmware() interface
backport for 2.4 done by Manuel Estrada Sainz. It is now in -ac for a
while and I have used it in my -mh patches. It works fine and seems to
be clean and very stable. Karsten Keil has tested it together with my
ported bfusb.o Bluetooth driver on AMD64.

Regards

Marcel


Please do a

        bk pull http://linux-mh.bkbits.net/fw-loader-2.4

This will update the following files:

 drivers/bluetooth/bfusb.h                             |52261 ------------------
 Documentation/Configure.help                          |    6 
 Documentation/firmware_class/README                   |   58 
 Documentation/firmware_class/firmware_sample_driver.c |  121 
 Documentation/firmware_class/hotplug-script           |   16 
 drivers/bluetooth/Makefile.lib                        |    1 
 drivers/bluetooth/bfusb.c                             |   38 
 include/linux/firmware.h                              |   20 
 lib/Config.in                                         |    7 
 lib/Makefile                                          |    4 
 lib/firmware_class.c                                  |  581 
 11 files changed, 830 insertions(+), 52283 deletions(-)

through these ChangeSets:

<marcel@holtmann.org> (03/08/19 1.1078.1.5)
   [PATCH] Make request_firmware() compile cleanly
   
   This patch makes the request_firmware() compile on other platforms
   than i386. It adds the missing include <linux/init.h> and replaces
   some ssize_t with int.

<marcel@holtmann.org> (03/08/16 1.1078.1.4)
   [Bluetooth] Make use of request_firmware() for the BlueFRITZ! USB driver
   
   The BlueFRITZ! USB devices need a firmware download every time they are
   plugged in. With request_firmware() the file bfubase.frm is now loaded
   from the userspace and the included firmware is removed.

<marcel@holtmann.org> (03/08/15 1.1078.1.3)
   [PATCH] Firmware loading depends on hotplug support
   
   This patch makes the firmware loading support only selectable if the
   hotplug support is also enabled.

<marcel@holtmann.org> (03/08/11 1.1078.1.2)
   [PATCH] Make request_firmware() compile if hotplug support is disabled
   
   This patch fixes the problem, where hotplug support is disabled and an
   internal kernel driver uses request_firmware(). The driver will compile
   and load now, but it must handle the case where the firmware loading
   fails, because the kernel is build without hotplug support, by itself.

<ranty@debian.org> (03/08/11 1.1078.1.1)
   [PATCH] request_firmware() backport to 2.4 kernels
   
   A while back request_firmware() was added to the 2.5 kernel series
   to support firmware needing drivers keeping the firmware images in
   userspace. And I also backported it to the 2.4 kernel series on top
   of procfs.




             reply	other threads:[~2003-08-25 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 12:22 Marcel Holtmann [this message]
2003-09-01 12:04 ` request_firmware() backport to 2.4 Marcelo Tosatti
2003-09-01 13:00   ` Marcel Holtmann
2003-09-01 13:26     ` Marcelo Tosatti
2003-09-01 13:45       ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2003-09-02 19:20 Jean Tourrilhes
2003-09-03 16:50 ` Jeff Garzik

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=1061814172.973.130.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.