Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: Peter Klausler <pmk@cray.com>,
	BlueZ Users List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bthid updated
Date: Sat, 15 Nov 2003 23:57:46 +0100	[thread overview]
Message-ID: <1068937066.17638.346.camel@pegasus> (raw)
In-Reply-To: <1068933564.15097.46.camel@saag>

Hi Edd,

> Thanks for the pointer.  Attached is a patch to make Peter's software
> work with the uinput driver, suitable for bthid-0.8.  Tested under
> 2.6.0-test9.
> 
> With a bit of trouble I have this working with an Apple keyboard and an
> MS mouse.  I have found it troublesome to connect the devices:
> 
>         * power cycling the mouse is required after a connection is
>         lost, and even this doesn't always work
>         
>         * the Apple keyboard is very difficult to connect. Often after
>         reading the HID descriptor it receives no key events.
> 
> Also, the mouse events get lagged and the cursor sways drunkenly around
> the desktop: looks like we need to do something to batch up mouse events
> so the cursor keeps up with the mouse.

maybe it is a good idea to read my notes about HID

	http://www.holtmann.org/linux/bluetooth/hid.html

I also put my bthid utility into the utils2 CVS repository. It was
working fine for me and I solved the problem when the HID device
disconnects the L2CAP channels. However it depends on a modified USB HID
kernel module which allows us to input the HID reports directly into
their HID parser. But this USB HID modification is only a bad hack at
the moment.

I like to reuse the kernel HID parser from the USB subsystem, but this
is not as easy as I thought in the first place, because it is hardwired
with the USB subsystem. A HID parser is not a USB only thing, not
anymore. Maybe we should have the HID parser also in user space like
Peter's code does and use the uinput driver. At the moment I think this
is bad, because both parsers must be maintained and writing a good HID
parser is not a easy job. The kernel parser is doing quite a very good
job, but the people from the input subsystem are not very helpful in
building a general HID interface. Any thoughts about how to proceed?

As a side note, be careful with libs2 and utils2 ;)

Regards

Marcel




-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2003-11-15 22:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06  1:45 [Bluez-users] bthid updated Peter Klausler
2003-11-06  9:02 ` Gareth Reakes
2003-11-06  9:10 ` Marcel Holtmann
2003-11-10 11:25   ` Michal Semler (volny.cz)
2003-11-10 11:52     ` Marcel Holtmann
2003-11-10 13:06 ` Olivier Bornet
2003-11-15 18:02 ` Edd Dumbill
2003-11-15 19:39   ` Marcel Holtmann
2003-11-15 21:59     ` Edd Dumbill
2003-11-15 22:50       ` Edd Dumbill
2003-11-15 22:57       ` Marcel Holtmann [this message]
2003-11-16 13:14         ` Florian Echtler
2003-11-16 13:22           ` Marcel Holtmann

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=1068937066.17638.346.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=edd@usefulinc.com \
    --cc=pmk@cray.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