From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Celluon Laserkey Bluetooth Keyboard
Date: Fri, 15 Sep 2006 16:13:12 +0200 [thread overview]
Message-ID: <1158329592.5233.32.camel@localhost> (raw)
In-Reply-To: <beb7688e0609150702x738ad4d8re64815d12f457a76@mail.gmail.com>
Hi Crhis,
> First, I apologize if this is off-topic for this list, but I'm not
> sure where to post general Bluetooth+Linux related questions.
>
> I recently bought a Celluon CL800BT Bluetooth keyboard/mouse
> (http://celluon.com/products/laserkey.htm?sm=2_1) and I'd like to use
> it in Linux (Fedora Core 5). I've tried the Gnome and KDE utilities,
> but haven't had much luck. I was able to use kbluetoothd to see some
> sort of "Serial Port" file on the device, but I wasn't able to do
> anything further. I've also gotten some feedback from hcitool and hidd:
>
> $ hcitool scan
> Scanning ...
> 00:0B:24:40:C7:83 CL800BT
> $ hcitool inq
> Inquiring ...
> 00:0B:24:40:C7:83 clock offset: 0x3ab6 class: 0x400210
> $ hcitool info 00:0B:24:40:C7:83
> Requesting information ...
> BD Address: 00:0B:24:40:C7:83
> Device Name: CL800BT
> LMP Version: 1.1 (0x1) LMP Subversion: 0x291
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2
> packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging
> scheme>
> <power control> <transparent SCO>
> $ hidd --connect 00:0B:24:40:C7:83
> Connected to 00:0B:24:40:C7:83 on channel 1
> Press CTRL-C for hangup
> Unknown event code 165
> Unknown event code 165
> Unknown event code 1
> Unknown event code 0
> Unknown event code 0
> Unknown event code 0
> Unknown event code 1
> Unknown event code 255
> Unknown event code 1
> Unknown event code 18
> Unknown event code 0
> Unknown event code 1
> Unknown event code 255
> Unknown event code 255
> Unknown event code 255
> Unknown event code 0
> Unknown event code 1
>
> The last part is interesting, because the three 255s repeat for every
> keypress and mouse movement made with the device.
this is not a HID compatible keyboard and needs an extra driver to
function properly. Please run "sdptool records --raw <bdaddr>" to
retrieve the SDP records for this device.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-09-15 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 14:02 [Bluez-devel] Celluon Laserkey Bluetooth Keyboard Chris S
2006-09-15 14:13 ` Marcel Holtmann [this message]
2006-09-15 23:45 ` Chris Spencer
2006-09-16 9:00 ` Marcel Holtmann
2006-09-16 18:08 ` Chris Spencer
2006-09-18 6:36 ` [Bluez-devel] " Marcel Holtmann
2006-09-17 16:55 ` Chris Spencer
2006-09-18 6:38 ` [Bluez-devel] " Marcel Holtmann
2006-09-18 13:21 ` Chris S
2006-09-18 13:25 ` [Bluez-devel] " Marcel Holtmann
2006-09-18 13:34 ` Chris S
2006-09-18 13:39 ` [Bluez-devel] " Marcel Holtmann
2006-09-18 13:53 ` Chris S
2006-09-18 14:48 ` Chris S
2006-09-18 13:42 ` Chris S
2006-09-18 14:18 ` [Bluez-devel] " Marcel Holtmann
2006-09-21 0:56 ` Chris Spencer
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=1158329592.5233.32.camel@localhost \
--to=marcel@holtmann.org \
--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