From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Antti Mäkelä" <zarhan@cs.tut.fi>,
"BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BT3C ceased working in kernel 2.6.6
Date: Wed, 12 May 2004 19:48:19 +0200 [thread overview]
Message-ID: <1084384099.25099.98.camel@pegasus> (raw)
In-Reply-To: <1084383638.4426.391.camel@hades.cambridge.redhat.com>
Hi David,
> > right now I am not going to keep up with a new version of bluefw,
> > because the bt3c_cs driver didn't use it anymore and for 2.6 the bcm203x
> > kernel firmware loader works much better. However I am going to apply
> > patches if they look correct. So this one is in CVS.
>
> I know it's obsolete for the PC card; is it no longer needed for USB
> either with a 2.6 kernel?
the bcm203x driver can be used to load the firmware into Broadcom based
dongles. It doesn't replaces the bluefw, because in some cases it is
better to not use an extra kernel module. However the method with the
kernel driver for firmware loading is working much better for me.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-05-12 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 9:30 [Bluez-devel] BT3C ceased working in kernel 2.6.6 Antti Mäkelä
2004-05-12 13:35 ` Marcel Holtmann
2004-05-12 14:21 ` David Woodhouse
2004-05-12 17:17 ` Marcel Holtmann
2004-05-12 17:40 ` David Woodhouse
2004-05-12 17:48 ` Marcel Holtmann [this message]
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=1084384099.25099.98.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=zarhan@cs.tut.fi \
/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