From: amateur <ztl.post@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] why does one need bluez-firmware ?
Date: Mon, 18 Dec 2006 18:47:31 +0800 [thread overview]
Message-ID: <20061218104730.GA3296@163.com> (raw)
In-Reply-To: <1166357730.6557.12.camel@aeonflux.holtmann.net>
On Sun, Dec 17, 2006 at 01:15:30PM +0100, Marcel Holtmann wrote:
> Hi,
>
> > I read on some web pages that one need bluez-firmware to be able to
> > operate the BroadCom 203x series bluetooth dongle correctly on a 2.4
> > kernel. So I am wondering what is the purpose of bluez-firmware? And
> > how does it work?
>
> that is a misunderstanding. For the 2.6 kernel you use a kernel module
> to load the firmware. For 2.4 an extra USB application was needed. Both
> however need the firmware files.
And what is the purpose of bluez-firmware? How does it work?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-12-18 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 2:20 [Bluez-users] why does one need bluez-firmware ? amateur
2006-12-17 12:15 ` Marcel Holtmann
2006-12-18 10:47 ` amateur [this message]
2006-12-18 11:55 ` Marcel Holtmann
[not found] <mailman.247983.1166465173.8777.bluez-users@lists.sourceforge.net>
2006-12-18 19:35 ` Steve " 'dillo " Okay (Roadknight Labs)
2006-12-19 9:43 ` Marcel Holtmann
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=20061218104730.GA3296@163.com \
--to=ztl.post@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/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