From: Marcel Holtmann <marcel@holtmann.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Philip Blundell <pb@nexus.co.uk>,
Keith Pemberton <kbpember@cox.net>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Writing a bluetooth mouse driver...
Date: Mon, 15 Mar 2004 16:00:43 +0100 [thread overview]
Message-ID: <1079362843.3405.58.camel@pegasus> (raw)
In-Reply-To: <20040315143214.GB1365@ucw.cz>
Hi Vojtech,
> > the problematic part is hid-core.c, because it contains the USB specific
> > transport layer. I ripped it off and included the rest into my HIDP code
> > and it works flawless. The Bluetooth transport code is almost ready. I
> > only need to include some workarounds for the stupid L2CAP disconnect
> > problems with some HID implementations, but this has nothing to do with
> > the HID parser.
> >
> > Actually the HID parser is independent from the input and USB subsystem,
> > because you can use a Bluetooth transport and the hiddev interface for
> > reading and writing reports. What I have in mind is cleaning up the
> > current code and putting it under drivers/hid/ with this API:
> >
> > struct hid_device {
> > ...
> >
> > void *driver_data;
> > int (*send)(struct hid_device *device, unsigned char *data, int size);
> > }
> >
> > struct hid_device *hid_alloc_device(unsigned char *data, int size);
> > void hid_free_device(struct hid_device *device);
> > int hid_register_device(struct hid_device *device);
> > void hid_unregister_device(struct hid_device *device);
> > int hid_recv_report(struct hid_device *hid, int type, unsigned char *data, int size);
>
> This is a very nice idea. I'm all for it.
the problem that I see is that someone has to code it and I am not a
real HID parser expert. I want to add kernel side Bluetooth HID support
into 2.6.5 and at the moment I only see to choices:
1. I include my ripped hid-core.c and hid-input.c code along with my
HIDP code in net/bluetooth/hidp/
2. I build up a basic drivers/hid/ with limited functionality (only
input and no hiddev support) and the proposed API. The name of the
kernel module should be something like hid-ng.ko until we have a full
replacement for hid.ko.
Comments?
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-15 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 11:38 [Bluez-devel] Writing a bluetooth mouse driver Keith Pemberton
2004-03-15 12:03 ` Marcel Holtmann
2004-03-15 13:58 ` Philip Blundell
2004-03-15 14:18 ` Marcel Holtmann
2004-03-15 14:32 ` Vojtech Pavlik
2004-03-15 15:00 ` Marcel Holtmann [this message]
2004-03-15 15:44 ` [Bluez-devel] Implementing Bluez into microchip MSP430 zubiwat
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=1079362843.3405.58.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kbpember@cox.net \
--cc=pb@nexus.co.uk \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.