From: Marcel Holtmann <marcel@holtmann.org>
To: Manuel Estrada Sainz <ranty@debian.org>
Cc: Andrea Arcangeli <andrea@suse.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: request_firmware() backport to 2.4 kernels
Date: 26 Jul 2003 23:04:27 +0200 [thread overview]
Message-ID: <1059253473.922.18.camel@pegasus> (raw)
In-Reply-To: <20030726121638.GB31145@ranty.pantax.net>
Hi Manuel,
> 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, but Marcelo didn't answer emails relating to it (there where
> probably other more important matters back then).
>
> Since then, the 2.4 backport has been deployed and tested with
> orinoco_usb driver variant (http://orinoco-usb.alioth.debian.org/),
> as you can see in the download statistics in alioth, there has been
> more than 400 downloads of the request_firmware enabled version
> (0.2.1). And drivers on the 2.5/2.6 series are being ported to use
> request_firmware() interface.
I've tested your patch with 2.4.22-pre8 and a modified version of my
bfusb driver. It is working fine, but I get these log entries:
hub.c: new USB device 02:0c.0-2, assigned address 2
firmware_class.c:call_helper: firmware: /sbin/hotplug firmware add
remove_proc_entry: bfusb003002/loading busy, count=1
remove_proc_entry: firmware/bfusb003002 busy, count=1
BlueFRITZ! USB loading firmware
de_put: deferred delete of loading
de_put: deferred delete of bfusb003002
BlueFRITZ! USB device ready
Is this a problem of your patch or is it a general /proc problem?
> Would it be possible to include it in the -aa kernel tree? That would
> make it accessible to a wider audience for testing, and make it easier
> for developers to backport their drivers to the 2.4
> series.
The patch don't touches any other part of the Linux kernel, so I think
it is a nice and clean extension.
Documentation/Configure.help | 6
Documentation/firmware_class/README | 58 +
Documentation/firmware_class/firmware_sample_driver.c | 121 +++
Documentation/firmware_class/hotplug-script | 16
include/linux/firmware.h | 20
lib/Config.in | 4
lib/Makefile | 3
lib/firmware_class.c | 557 ++++++++++++++++++
8 files changed, 784 insertions(+), 1 deletion(-)
I already ported drivers/bluetooth/bfusb.c to use the request_firmware()
interface and I will port drivers/bluetooth/bt3c_cs.c after this patch
gets merged.
Regards
Marcel
next prev parent reply other threads:[~2003-07-26 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 12:16 request_firmware() backport to 2.4 kernels Manuel Estrada Sainz
2003-07-26 18:55 ` Andrea Arcangeli
2003-07-26 21:04 ` Marcel Holtmann [this message]
2003-07-26 21:15 ` Manuel Estrada Sainz
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=1059253473.922.18.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=ranty@debian.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 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.