public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Chris Spencer <chrisspen@gmail.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Celluon Laserkey Bluetooth Keyboard
Date: Mon, 18 Sep 2006 08:36:42 +0200	[thread overview]
Message-ID: <1158561402.30486.27.camel@localhost> (raw)
In-Reply-To: <450C3D9B.5040506@gmail.com>

Hi Chris,

> >>>> 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.
> >> Sure, here's the output:
> >>
> >> $ sdptool records --raw 00:0B:24:40:C7:83
> >> Sequence
> >>          Attribute 0x0000 - ServiceRecordHandle
> >>                  UINT32 0x00010000
> >>          Attribute 0x0001 - ServiceClassIDList
> >>                  Sequence
> >>                          UUID16 0x1101 - SerialPort
> >>          Attribute 0x0004 - ProtocolDescriptorList
> >>                  Sequence
> >>                          Sequence
> >>                                  UUID16 0x0100 - L2CAP
> >>                          Sequence
> >>                                  UUID16 0x0003 - RFCOMM
> >>                                  UINT8 0x01
> >>          Attribute 0x0100
> >>                  String Serial Port
> >>
> >> Please let me know if you need any other information, or if there's 
> >> anything I can do to help get this working.
> > 
> > this looks like the third of these. Please also run "hcitool inq" and
> > "hcitool info ..." (as root) for this.
> 
> I may have already pasted those outputs in my original email, but here 
> they are again:

sorry, my bad. Too many emails.

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

  reply	other threads:[~2006-09-18  6:36 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
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         ` Marcel Holtmann [this message]
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=1158561402.30486.27.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=chrisspen@gmail.com \
    /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