Subject: Re: [Bluez-users] HID report mode protocol support in 2.6.11-mh1
	broken/missing?
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
In-Reply-To: <200503141344.03345.florian-evers@gmx.de>
References: <1110498275.3040.6.camel@pc.vesuri.net>
	 <1110796090.8158.56.camel@pegasus>
	 <200503141344.03345.florian-evers@gmx.de>
Content-Type: text/plain
Message-Id: <1110804929.629.7.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Reply-To: bluez-users@lists.sourceforge.net
Date: Mon, 14 Mar 2005 13:55:29 +0100

Hi Florian,

> I have the same problem here. I'm owner of a Microsoft Wireless Desktop
> Elite for BT 2.0. The only kernel that offered me support for the
> mouse wheel was 2.6.10-mh2. It had some quirks (left mouse button does
> not work properly after reconnection, I've to press all mouse-buttons
> simultaneously with mouse cursor over background in KDE. Then it
> works again) but basically it is _far_ better than having no wheel
> support.
> 
> -mh3 and -mh4 didn't work for me. They were not able to detect my bluetooth
> dongle. Vanilla 2.6.11 and 2.6.11-mh1 detect my MS-BT 2.0 dongle correctly, 
> but keyboard and mouse are accessed in boot protocol mode. So I'm using
> 2.6.10-mh2 again...

send in the "hcidump -X -V" for the HID connection setup.

Regards

Marcel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users