From: Marcel Holtmann <marcel@holtmann.org>
To: John McCorquodale <mcq@cacr.caltech.edu>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez HID story?
Date: Tue, 09 Mar 2004 23:37:55 +0100 [thread overview]
Message-ID: <1078871875.10671.86.camel@pegasus> (raw)
In-Reply-To: <20040309212125.GA27173@viz.cacr.caltech.edu>
Hi John,
> So I'm trying to get my spiffy new Logitech BT keyboard working with my CF
> BT card.
>
> I found Peter Klausler's 'bthid' which seems to sortof work with the uinput
> driver in 2.4.25. However, when typing very fast, it repeats substrings of
> my input more than once (e.g. 'ls -lsa' -> 'ls -ls-lsa') which is a problem
> that typing more slowly eliminates. I've also had my kernel panic once or
> twice when trying this stuff out.
>
> I also found Marcel's page:
>
> http://www.holtmann.org/linux/bluetooth/hid.html
>
> Which starts off great talking about how "this reimplementation" reuses the HID
> parser from USB and is morally superior to Peter's work. However, the page
> then goes on to talk about all sorts of USB dongles, which is irrelevant (the
> whole point of a BT keyboard is to throw the dongle in the trash and use my
> laptop's builtin BT), and further doesn't seem to talk about any exiting code
> at all past the mention of "this reiplementation" in the first paragraph.
>
> My question is:
>
> What is the best currently working way to handle bluetooth HI devices? The
> device itself, not the dongle. How does one configure host-initiated
> disconnection on idle detection (since I'm a Logitech KB, I guess I need to
> do that)? Am I just totally missing the important message on Marcel's
> HID page? By the way: what's doing the layout on hortmann.org? -- I really
> respect and admire the minimalism and good design sense of those pages.
>
> If there is such a thing, can you give me a quick breakdown of the steps one
> would take to get it working? For example, for bthid, the steps I use go:
>
> 1. Get HCI working (cardmgr loads serial_cs, hciattach ttyS0 bcsp 2300400)
> 2. Compile bthid from http://www.visi.com/~pmk/bthid-0.10.tar.gz
> 3. hcitool scan, hit connect button, to deduce BT address of keyboard
> 4. bthid -n -v -v <address>
> 5. hit connect on KB
>
> If there is no existing HID implementation other than Peter's, please let me
> know this so I know it's worth the time to debug the substring repeat problem
> and figure out why it panics me.
actually there is a new implementation. The code is only present in the
CVS, because it makes use of the new Bluetooth library and this is not
fully ready for mainstream. A installation HOWTO can be found here
http://www.bueche.ch/comp/mx900/mx900.html
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-09 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 21:21 [Bluez-users] Bluez HID story? John McCorquodale
2004-03-09 22:37 ` 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=1078871875.10671.86.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=mcq@cacr.caltech.edu \
/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