Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Wacom Graphire Bluetooth  problems
Date: Wed, 28 Sep 2005 09:28:31 +0200	[thread overview]
Message-ID: <1127892511.5321.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050926113225.GA19843@polar.elf12.net>

Hi Robert,

> Aehm, sorry for being unclear, my question was: Where
> are the huge differences between
> 2.6.12-mh3 and
> 2.6.13-mh1

if you look only to HID then there is no difference.

> A new question: Do I see it right that there are at the moment two HID
> interpreter in a patched kernel: one for USB and one for Bluetooth? Are
> there already differences between them? (Why? Which?)

The Bluetooth HID is derived from the USB HID, but without the hiddev
support and a lot of things stripped out. It is basically a proof of
concept.

> > > Where is the driving force
> > > behind a generic HID driver? Here or more with the USB guys? <-:
> > > I fear that it will take some six month or longer. - I will probably dig
> > > into the HID bluetooth code to get the Wacom working ...
> > > ... and do some adaptions when the generic driver arises.
> > 
> > I think the force for that have to be driven by me. We all agreed on how
> > this should be done, but there are some things pending that I like to
> > see merged first mainline (subclass support and sysfs integration)
> > before I look at it again.
> 
> Hm... Would you approve some HID hacking on your -mh patches for the
> meantime? I'm also interested in a generic HID driver but don't want to
> stand still until it appears. - Later joining wanted.

Send in patches against the latest -mh patch.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-09-28  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 20:03 [Bluez-users] Wacom Graphire Bluetooth problems Robert Siemer
2005-09-25 10:29 ` Marcel Holtmann
2005-09-25 12:34   ` Robert Siemer
2005-09-25 15:10     ` Marcel Holtmann
2005-09-25 16:54       ` Robert Siemer
2005-09-26  9:24         ` Marcel Holtmann
2005-09-26 11:32           ` Robert Siemer
2005-09-28  7:28             ` 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=1127892511.5321.2.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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