From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-input <linux-input@vger.kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
mjg <mjg@redhat.com>, Peter Hutterer <peter.hutterer@redhat.com>,
zap@homelink.ru
Subject: Re: RFC: Wacom Bluetooth HID driver, first pass
Date: Mon, 16 Mar 2009 23:58:54 +0000 [thread overview]
Message-ID: <1237247934.32264.10670.camel@cookie.hadess.net> (raw)
In-Reply-To: <1237213799.32264.10090.camel@cookie.hadess.net>
On Mon, 2009-03-16 at 14:29 +0000, Bastien Nocera wrote:
> On Mon, 2009-03-16 at 15:00 +0100, Marcel Holtmann wrote:
<snip>
> > > A couple of notes:
> > > - the wheel action is reversed, it's a simple fix, done locally
> > > - hidp and the Bluetooth sub-system says it can't probe the device
> > > with
> > > error "-14" when hid-wacom.ko isn't already loaded
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
wacom 0005:056A:0081.0001: parse failed
wacom: probe of 0005:056A:0081.0001 failed with error -14
wacom driver registered
> > what was the reason for not forcing HID to load the generic driver?
>
> What generic driver? If you're talking about the default Wacom driver,
> it isn't an HID driver, and requires a USB device.
>
> > I
> > lost track on how HID is suppose to handle these. You could also
> > introduce a phony export like we do with L2CAP to ensure it is loaded
> > even if userspace isn't ready to handle this dependency.
>
> Well, the problem is that the driver _does_ load, but I'm not certain
> about the sequence of events between the Bluetooth sub-system, the
> user-space enabling (see the linked patch to bluetoothd), and the HID
> sub-system.
Turning the device off and on again works though. No idea what's
happening.
> > > - I'm getting oopses in hci_conn_del() when the device goes away
> > > (eg. I
> > > turn it off).
> >
> > Try to run a net-next-2.6 or bluetooth-next-2.6 kernel. Kyle should
> > have merged these patches into the latest rawhide kernel.
>
> I was hoping this would be fixed in the latest linus-2.6 tree, guess
> not.
No more crashes. Great stuff.
I sent a fixed up patch to the list earlier.
Cheers
next prev parent reply other threads:[~2009-03-17 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 23:59 RFC: Wacom Bluetooth HID driver, first pass Bastien Nocera
[not found] ` <1236988799.32264.6310.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-03-16 10:55 ` Bastien Nocera
[not found] ` <1237200912.32264.9867.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-03-16 14:00 ` Marcel Holtmann
[not found] ` <93531296-64B0-4D4B-A4A9-26F3D67DF579-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2009-03-16 14:29 ` Bastien Nocera
2009-03-16 23:58 ` Bastien Nocera [this message]
2009-03-16 23:55 ` [PATCH] Wacom Graphire Bluetooth driver Bastien Nocera
2009-03-18 0:11 ` [PATCH] Wacom Graphire Bluetooth driver (updated with a few fixes) Bastien Nocera
2009-03-18 21:28 ` Andrew Zabolotny
2009-03-18 22:47 ` Bastien Nocera
2009-03-28 19:35 ` Andrew Zabolotny
[not found] ` <1237247755.32264.10664.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-03-31 22:35 ` [PATCH] Wacom Graphire Bluetooth driver Bastien Nocera
2009-05-06 15:14 ` [PATCH] Wacom Graphire Bluetooth driver (updated with a few fixes) Bastien Nocera
2009-05-11 15:20 ` Jiri Kosina
2009-05-11 16:12 ` Bastien Nocera
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=1237247934.32264.10670.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mjg@redhat.com \
--cc=peter.hutterer@redhat.com \
--cc=zap@homelink.ru \
/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;
as well as URLs for NNTP newsgroup(s).