From: Nick <Nick@bielefeld.ccc.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hello
Date: Mon, 29 Nov 2004 16:58:20 +0100 [thread overview]
Message-ID: <41AB471C.7030609@bielefeld.ccc.de> (raw)
In-Reply-To: <41AB1B6B.5010004@soft.uni-linz.ac.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Simon Vogl wrote:
| well there is one tool: get the csr reset utility, it contains
| source code to also alter the hci mapping (which I used on my
| vaio):
|
http://www.soft.uni-linz.ac.at/_wiki/tiki-index.php?page=ProjectBluezHandsfree
|
|
| no guarantees given, no questions asked ;) simon
excellent it works. that was easy. i think i´ll take a look at the
source code, to know what the tool is doing. ;)
is this a vaio specific thing, got a vaio v505cp myself.
~ ,nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBq0ac40bmwXROfRURApRaAKC4H9Bl5g0Y4bSd1UIjpi6s/C+d1wCbBbqu
fQ2ottOEke4GmhOsowxbZvk=
=Eh5o
-----END PGP SIGNATURE-----
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-29 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 1:57 [Bluez-devel] hello Nick
2004-11-29 2:19 ` Marcel Holtmann
2004-11-29 12:37 ` Nick
2004-11-29 12:44 ` Marcel Holtmann
2004-11-29 12:51 ` Simon Vogl
2004-11-29 15:58 ` Nick [this message]
2004-11-29 13:30 ` Simon Vogl
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=41AB471C.7030609@bielefeld.ccc.de \
--to=nick@bielefeld.ccc.de \
--cc=bluez-devel@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