From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Microsoft Optical Desktop Elite for Bluetooth and dual booting
Date: Wed, 01 Feb 2006 20:18:01 +0100 [thread overview]
Message-ID: <1138821481.3806.21.camel@localhost.localdomain> (raw)
In-Reply-To: <43E0F8F7.9070009@gmail.com>
Hi John,
> And thanks for your quick reply. Having watched some replies in this
> mailing list I totally agree that transferring the link key from one OS
> to the other can be difficult.
>
> So, let's get back on the first solution: since sometimes I can use my
> keyboard in Linux, I suppose my device is sometimes paired, right? If
> not, which commands exactly I have to use? Then, how to write the link
> key to the bluetooth chip? Could you make an example of the command
> hciconfig for writing this key to the chip?
use "hciconfig hci0 putkey ..." after you paired your keyboard with your
Linux machine.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-01 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 11:10 [Bluez-users] Microsoft Optical Desktop Elite for Bluetooth and dual booting JoKo
2006-02-01 16:42 ` Marcel Holtmann
2006-02-01 18:07 ` JoKo
2006-02-01 19:18 ` Marcel Holtmann [this message]
2006-02-02 9:09 ` JoKo
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=1138821481.3806.21.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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