From: Rob Sims <bluez-z@robsims.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Sharing devices with dual-booted Windows
Date: Thu, 29 Nov 2007 13:44:42 -0700 [thread overview]
Message-ID: <20071129204442.GC17661@robsims.com> (raw)
In-Reply-To: <81AD8A6B-9825-4641-951F-FEE9A0DE20C4@holtmann.org>
[-- Attachment #1.1: Type: text/plain, Size: 1397 bytes --]
On Thu, Nov 29, 2007 at 09:15:23PM +0100, Marcel Holtmann wrote:
> > fwiw, the only thing I could find would work only for csr chips using
> > bccmd from bluez-utils/tools (configure --enable-bccmd). Get the
> > bdaddr to see how the bytes are swapped around:
> > bccmd psget bdaddr
> > then set and reset the adapter (sometimes these commands take two
> > goes to take)
> > bccmd psset -r bdaddr 0x2000 0xaf9b 0xf400 0x0800
> > I could give this a whack tonight.
> using the bdaddr command is much simpler. It does the magic of
> bringing the address into the right format.
> > fyi, bccmd can brick the adapter (eg if you use "-s" to make bad
> > settings permanent). It would be nice if someone who fiddles with csr
> > stuff can verify this approach.
> Take this warning serious. You can really brick your dongle.
It appears from the behavior described above and a sample CSR datasheet
that PS is "Persistent Store." This means that not only would I have to
run this each time starting Linux, I'd have to restore the original
bdaddr in Linux before booting to Windows.
Also, this is a built-in adapter in a Thinkpad; it's significantly more
expensive than a dongle to fix, even if it might be a CSR core.
Thanks for settling this - there is no way to soft-set (change
disappears on reset) the bdaddr of existing bluetooth adapters.
--
Rob
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 309 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-11-29 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 16:12 [Bluez-users] Sharing devices with dual-booted Windows Rob Sims
2007-05-22 18:08 ` Marcus C. Gottwald
2007-05-28 0:13 ` Rob Sims
2007-05-28 15:16 ` Marcus C. Gottwald
2007-05-23 20:38 ` [Bluez-users] auth problems bhairava
2007-05-24 6:05 ` Aveek Audhya
2007-05-24 6:06 ` bhairava
2007-11-29 15:55 ` [Bluez-users] Sharing devices with dual-booted Windows Rob Sims
2007-11-29 16:45 ` Brad Midgley
2007-11-29 18:37 ` Rob Sims
2007-11-29 20:06 ` Brad Midgley
2007-11-29 20:15 ` Marcel Holtmann
2007-11-29 20:44 ` Rob Sims [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=20071129204442.GC17661@robsims.com \
--to=bluez-z@robsims.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;
as well as URLs for NNTP newsgroup(s).