From: Marcel Holtmann <marcel@holtmann.org>
To: nicolas <n1c0l4s.l3@wanadoo.fr>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] probleme installing Wireless IntelliMouse and optical desktop
Date: Tue, 15 Jun 2004 12:11:11 +0200 [thread overview]
Message-ID: <1087294271.13792.87.camel@pegasus> (raw)
In-Reply-To: <200406151155.09370.n1c0l4s.l3@wanadoo.fr>
Hi Nicolas,
> i have some questions because i have kernel 2.6.7Rc2mdk and my bluetooth is
> recognise
first you need a least the 2.6.6-mh3 patch in your kernel and you must
activate HIDP support.
> $ hcitool inq
> Inquiring ...
> 00:50:F2:7F:C4:E8 clock offset: 0x6892 class: 0x002580
> 00:50:F2:80:A1:2B clock offset: 0x6d26 class: 0x002540
> $ hcitool scan
> Scanning ...
> 00:50:F2:7F:C4:E8 Microsoft Mouse
> 00:50:F2:80:A1:2B Microsoft Keyboard
> # hcitool info 00:50:F2:80:A1:2B
> Requesting information ...
> BD Address: 00:50:F2:80:A1:2B
> Device Name: Microsoft Keyboard
> LMP Version: 1.1 (0x1) LMP Subversion: 0x1df
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xfc 0xfb 0x0f 0x00 0x00 0x00 0x00 0x00
> <encryption> <slot offset> <timing accuracy> <role switch>
> <hold mode> <sniff mode> <park state> <RSSI> <SCO link>
> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
> <paging scheme> <power control> <transparent SCO>
> # hcitool info 00:50:F2:7F:C4:E8
> Requesting information ...
> BD Address: 00:50:F2:7F:C4:E8
> Device Name: Microsoft Mouse
> LMP Version: 1.1 (0x1) LMP Subversion: 0x1d0
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xfc 0xfb 0x0f 0x00 0x00 0x00 0x00 0x00
> <encryption> <slot offset> <timing accuracy> <role switch>
> <hold mode> <sniff mode> <park state> <RSSI> <SCO link>
> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
> <paging scheme> <power control> <transparent SCO>
> #
>
> but how to connecte it to use it?
>
> i don't understand i have look at
> http://www.holtmann.org/linux/bluetooth/microsoft.html but it doesn't
>
> there is someone using it and which have the solution?
I splitted the pages yesterday, because it seems that every HID device
has its bugs and the text on www.holtmann.org/linux/bluetooth/hid.html
was getting too long.
More detailed information can be found in the mailing list archives, but
the short is; get the hidp.ko kernel module and install bluez-libs-2.7
and bluez-utils-2.7. Then start "hidd --server" and use "hidd -c ..."
for the initial connection to your mouse and keyboard.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-06-15 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 9:55 [Bluez-users] probleme installing Wireless IntelliMouse and optical desktop nicolas
2004-06-15 10:11 ` Marcel Holtmann [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=1087294271.13792.87.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=n1c0l4s.l3@wanadoo.fr \
/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