From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Keyboard woe
Date: Thu, 17 Aug 2006 20:24:13 +0200 [thread overview]
Message-ID: <1155839053.4075.160.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200608180117.02770.jwm@angrymonkey.net.nz>
Hi John,
> I've just picked up a luggable bluetooth keyboard for use with a cellphone,
> but I'd like to get it going under linux. This is proving to be a challenge.
>
> So far the USB bluetooth dongle seems to work fine, and I can gather
> information about the keyboard, ie:
>
> > hcitool inq
> Inquiring ...
> 00:0A:3A:30:D4:40 clock offset: 0x60be class: 0x001f00
> > hcitool info 00:0A:3A:30:D4:40
> Requesting information ...
> BD Address: 00:0A:3A:30:D4:40
> Device Name: KEYBOARD
> LMP Version: 1.1 (0x1) LMP Subversion: 0x2c2
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xbc 0x06 0x07 0x00 0x00 0x00 0x00 0x00
> <encryption> <slot offset> <timing accuracy> <role switch>
> <sniff mode> <RSSI> <channel quality> <CVSD> <paging scheme>
> <power control>
>
> After some reading I discover that I need to get going hidd to use the
> keyboard and I'd need to connect manually first to perform pairing. (This I
> find in the Debian readme, but no where else - is there documentation I'm
> missing?)
>
> The first time I run hidd --connect 00:0A:3A:30:D4:40 it fails with an oblique
> error message about not being able to open an input device. I have to run
> strace to find out which (/dev/input/uinput) then grep the kernel source to
> work out which module needs building (CONFIG_INPUT_UNINPUT). Again - have I
> missed some vital piece of documentation, here, because googling was rather
> unreliable...
>
> Now, when I run it, I get a connection, but I'm a bit lost as to what ought to
> happen. What I'm getting is every key press on the bluetooth keyboard
> producing an unknown event code, ie:
>
> > hidd --connect 00:0A:3A:30:D4:40
> Connected to 00:0A:3A:30:D4:40 on channel 1
> Press CTRL-C for hangup
> Unknown event code 1
> Unknown event code 64
> Unknown event code 2
> Unknown event code 3
> Unknown event code 4
>
> (String was 1234)
>
> What _should_ be happening?
>
> And what can I do to produce some debugging output of use to any developers on
> the list?
please get us the SDP records for this device. Use sdptool with "browse"
or "records" commands to fetch them. You might have a non-HID device
that needs special support in hidd.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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-08-17 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 13:17 [Bluez-users] Keyboard woe John Morton
2006-08-17 18:24 ` Marcel Holtmann [this message]
2006-08-18 4:17 ` John Morton
2006-08-18 11:10 ` Marcel Holtmann
2006-08-18 9:55 ` John Morton
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=1155839053.4075.160.camel@aeonflux.holtmann.net \
--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