From: Andrea Arcangeli <andrea@suse.de>
To: Manuel Estrada Sainz <ranty@debian.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: request_firmware() backport to 2.4 kernels
Date: Sat, 26 Jul 2003 14:55:51 -0400 [thread overview]
Message-ID: <20030726185551.GA5053@x30.random> (raw)
In-Reply-To: <20030726121638.GB31145@ranty.pantax.net>
On Sat, Jul 26, 2003 at 02:16:38PM +0200, Manuel Estrada Sainz wrote:
> Hi,
>
> 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.
>
> 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.
>
> Attached goes the patch against current 2.4-bk-cvs.
it's not intrusive, so I can certainly include it in the meantime,
thanks.
> Have a nice day
same to you ;)
Andrea
next prev parent reply other threads:[~2003-07-26 18:41 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 [this message]
2003-07-26 21:04 ` Marcel Holtmann
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=20030726185551.GA5053@x30.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).