All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Philip Blundell <pb@nexus.co.uk>
Cc: Keith Pemberton <kbpember@cox.net>,
	Vojtech Pavlik <vojtech@suse.cz>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Writing a bluetooth mouse driver...
Date: Mon, 15 Mar 2004 15:18:06 +0100	[thread overview]
Message-ID: <1079360285.3405.46.camel@pegasus> (raw)
In-Reply-To: <1079359127.21325.3.camel@mill.nexus.co.uk>

Hi Philip,

> I spoke with Vojtech last year about moving the HID parser from the USB
> code into the input subsystem, so that it could be shared with
> Bluetooth.  He seemed happy with that in principle, and I don't think it
> would be very difficult to implement, but I haven't had time to actually
> write a patch yet.

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);

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

  reply	other threads:[~2004-03-15 14:18 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 [this message]
2004-03-15 14:32       ` Vojtech Pavlik
2004-03-15 15:00         ` Marcel Holtmann
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=1079360285.3405.46.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.