public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris S" <chrisspen@gmail.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: Celluon Laserkey Bluetooth Keyboard
Date: Mon, 18 Sep 2006 09:42:59 -0400	[thread overview]
Message-ID: <beb7688e0609180642i50453bdel671fb81cb50a053b@mail.gmail.com> (raw)
In-Reply-To: <1158585929.25125.5.camel@localhost>

On 9/18/06, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Chris,
>
> > > > >> 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.
> > > >
> > > > What do mean by the "third of these"? Is it going to be difficult to
> > > > make a driver?
> > >
> > > run "hcidump -X -V" and then connect to RFCOMM channel 1 with the rfcomm
> > > tool and then start pressing keys and see what hcidump shows you. Maybe
> > > it is a simple key mapping.
> >
> > Ok, I'll do that as soon as I get home today.
> >
> > > Check the Smart Keyboard support for an
> > > example on how to add support for this keyboard.
> >
> > What do you mean by this? I Googled for <bluez smart keyboard support>
> > but didn't find anything. Is this code in CVS or documentation?
>
> it is in the CVS now. Maybe it is even the same key mapping. I looked
> the keyboard up on eBay and this one is too expensive to buy for testing
> and so I have to wait for donation to add it to my device library.

Btw, where in CVS is the Smart Keyboard example?

Chris

  parent reply	other threads:[~2006-09-18 13:42 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         ` [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 [this message]
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=beb7688e0609180642i50453bdel671fb81cb50a053b@mail.gmail.com \
    --to=chrisspen@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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