From: Robert Siemer <Robert.Siemer@backsla.sh>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Wacom Graphire Bluetooth  problems
Message-ID: <20050926113225.GA19843@polar.elf12.net>
References: <20050924200358.GJ28437@polar.elf12.net> <1127644165.6362.0.camel@localhost.localdomain> <20050925123425.GA8683@polar.elf12.net> <1127661017.6362.9.camel@localhost.localdomain> <20050925165458.GC8683@polar.elf12.net> <1127726670.6163.18.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <1127726670.6163.18.camel@localhost.localdomain>
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Reply-To: bluez-users@lists.sourceforge.net
Date: Mon, 26 Sep 2005 13:32:25 +0200

> > > > I'm using debian and it's kernel-making tool but the latest prepared
> > > > kernel was 2.6.12.  I patched it with 2.6.12-mh3. There does not seem
> > > > to be much Bluetooth/HID related changes between it and 2.6.13 with
> > > > patch. - Am I wrong?
> > > 
> > > yes, you are.
> > 
> > Hey, that answer was to short... (-:  I found no changelog for the 2.6
> > kernel series patches and I compared the patch 2.6.12-mh3 with the
> > 2.6.13 one (with my two human eyes). - What changed so dramatically?
> 
> the -mh patches contain a specific version for the hidp driver with
> report protocol support that is not mainline. It will also never get
> into mainline, because the solution is the generic HID driver.

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

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

> > 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.

> Check the mailing list archive for comments about that.

What search keywords do you recommend?


Bye,
	Robert


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users