public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] getting bluetooth v1.2
Date: Mon, 28 Mar 2005 14:19:11 +0200	[thread overview]
Message-ID: <4247F63F.70206@gmx.ch> (raw)
In-Reply-To: <1112011490.9016.27.camel@pegasus>

Hello Marcel

Marcel Holtmann wrote:
> Hi Marco,
> 
> 
>>>The CSR BlueCore02/BlueCore3/BlueCore4 chips support inquiry with RSSI,
>>>but the Silicon Wave ROM chips I have seen so far have a problem with
>>>inquiry with RSSI event size. The Broadcom chips don't support inquiry
>>>with RSSI (this includes the Microsoft 2.0 dongle).
>>
>>hciconfig -a tells me that the manufacturer of my dongle is "Cambridge 
>>Silicon Radio (10)". this is one of the problems-dongle, right?
> 
> 
> check with "hciconfig hci0 revision" as root what BlueCore chip is on it
> and no, these are not the problematic dongles.

it's a BlueCore02

>>so, an update to bt v1.2 wouldn't make sense to me...
> 
> What does "lsusb" tells you?

it think you mean this line:
Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle


>>>>Is it still to early for bluetooth v1.2?
>>>
>>> 
>>>It is actually too late, because we are moving to Bluetooth 2.0 with EDR
>>>support.
>>
>>but it's too early for 2.0 yet?
> 
> 
> Actually it is not. The only problem at the moment is that the Bluetooth
> module manufactures don't get the BlueCore4 modules done. After that you
> will see them in the USB dongles and the CSR BlueCore4 already supports
> EDR without any problems and so do BlueZ.

regards
Marco


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-03-28 12:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 16:51 [Bluez-users] getting bluetooth v1.2 Marco Trudel
2005-03-27 17:08 ` Marcel Holtmann
2005-03-28 11:47   ` Marco Trudel
2005-03-28 12:04     ` Marcel Holtmann
2005-03-28 12:19       ` Marco Trudel [this message]
2005-03-28 13:15         ` Marcel Holtmann
2005-03-28 16:18           ` Marco Trudel
2005-03-28 17:21             ` Marcel Holtmann
2005-03-28 17:36               ` Adam Goode
2005-03-28 17:48                 ` Marcel Holtmann
2005-03-29  8:07                   ` [Bluez-users] getting bluetooth v1.2, success report Marco Trudel
2005-03-29  9:56                     ` Michal Semler
2005-03-29 10:22                       ` Marco Trudel
2005-03-29 10:30                         ` Michal Semler
2005-03-29 10:16                     ` Marcel Holtmann
2005-03-29 10:20                       ` Michal Semler
2005-03-28 15:49   ` [Bluez-users] getting bluetooth v1.2 Adam Goode

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=4247F63F.70206@gmx.ch \
    --to=mtrudel@gmx.ch \
    --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