public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: amateur <ztl.post@gmail.com>,
	BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] why does one need bluez-firmware ?
Date: Sun, 17 Dec 2006 13:15:30 +0100	[thread overview]
Message-ID: <1166357730.6557.12.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20061217022039.GA4238@163.com>

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.

Regards

Marcel



-------------------------------------------------------------------------
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

  reply	other threads:[~2006-12-17 12:15 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 [this message]
2006-12-18 10:47   ` amateur
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=1166357730.6557.12.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=ztl.post@gmail.com \
    /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