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 18:18:26 +0200 (MEST)	[thread overview]
Message-ID: <20242.1112026706@www42.gmx.net> (raw)
In-Reply-To: 1112015700.9016.30.camel@pegasus

so it doesn't mather that i've a silicon dongle?
(i need the bt v1.2 only because the rssi inquiry)
or isn't it a silicon one?

what is now the procedure?
- getting the btdfu program
- fix it (Adam Goode told how)
- download the 18.x firmware. where can i get it?
- install it...

regards
Marco


> Hi Marco,
> 
> > > 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
> 
> and if this chip now contains 8 Mbit flash you get a good chance to
> upgrade it with HCI 18.x firmware and so get Bluetooth 1.2 support.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> 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
> 

-- 
Handyrechnung zu hoch? Tipp: SMS und MMS mit GMX
Seien Sie so frei: Alle Infos unter http://www.gmx.net/de/go/freesms


-------------------------------------------------------
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 16:18 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
2005-03-28 13:15         ` Marcel Holtmann
2005-03-28 16:18           ` Marco Trudel [this message]
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=20242.1112026706@www42.gmx.net \
    --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