From: Marcel Holtmann <marcel@holtmann.org>
To: Marcelo Tosatti <marcelo@parcelfarce.linux.theplanet.co.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: request_firmware() backport to 2.4
Date: 01 Sep 2003 15:45:26 +0200 [thread overview]
Message-ID: <1062423932.30893.148.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.44.0309011022140.2504-100000@logos.cnet>
Hi Marcelo,
> > > Now bfusb loads "bfubase.frm", but stock kernel has no such thing.
> > >
> > > I assume that breaks bfusb?
> >
> > no, the bfubase.frm is the original firmware file from AVM. This file
> > have to be placed somewhere on the filesystem.
>
> Right, and without placing the file somewhere on the filesystem bfusb
> 2.4.22 users wont have 2.4.23 working without "issues".
this is correct, but the firmware in bfusb.h of 2.4.22 is outdated and
it have some problems which are fixed in the newer firmware versions.
The development progress in Bluetooth is very fast at the moment and the
companies are fixing the problems with their own schedule. The driver
interface of the bfusb.o is clean and stable and in the most cases we
have no chance to workaround any problems in the Bluetooth firmware,
because we don't have access to the link manager. A new firmware means
recompile and pushing you a new bfusb.h (after I got the permission from
AVM) and this can happen very often in a 2.4.x release cycle.
> But well, I dont know if I should care that much.
I already thought about it, because the request_firmware() can report
back if a firmware file is not found and in this case it can load the
included firmware. But as stated above the firmware is outdated and so I
decided to remove it completly.
Regards
Marcel
next prev parent reply other threads:[~2003-09-01 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 12:22 request_firmware() backport to 2.4 Marcel Holtmann
2003-09-01 12:04 ` Marcelo Tosatti
2003-09-01 13:00 ` Marcel Holtmann
2003-09-01 13:26 ` Marcelo Tosatti
2003-09-01 13:45 ` Marcel Holtmann [this message]
-- 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=1062423932.30893.148.camel@pegasus \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=marcelo@parcelfarce.linux.theplanet.co.uk \
/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