From: Soeren Sonnenburg <kernel@nn7.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: usb initialization order (usbhid vs. appletouch)
Date: Sat, 28 Oct 2006 19:36:32 +0200 [thread overview]
Message-ID: <1162056992.9216.3.camel@localhost> (raw)
In-Reply-To: <200610281903.29510.oliver@neukum.org>
On Sat, 2006-10-28 at 19:03 +0200, Oliver Neukum wrote:
> Am Samstag, 28. Oktober 2006 18:56 schrieb Soeren Sonnenburg:
> > Anyways, back to the above problem. Can one somehow tell the hid-core to
> > load the appletouch driver when it detects any of these devices and then
> > initialize on top of that ? The appletouch driver is completely ignored
> > (doesn't even enter the atp_prope function as usb_register registers
> > with device/product tuples that are already taken by hid....
> >
> > Any ideas ?
>
> Try udev to disconnect the hid driver, then load appletouch.
I don't understand... I can disconnect the driver if I do on cmdline
libhid-detach-device 05ac:<id> ; modprobe appletouch .
However then my keyboard is gone.
Of course there is the workaround of building both the appletouch and
hid driver as modules and then loading them in this order ... but I was
hoping to have them fix in the kernel. If this is however not doable we
should mark it in Kconfig and I will have to live with it.
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
next prev parent reply other threads:[~2006-10-28 17:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:53 usb initialization order (usbhid vs. appletouch) Soeren Sonnenburg
2006-10-26 10:20 ` Oliver Neukum
2006-10-26 11:49 ` Soeren Sonnenburg
2006-10-26 12:36 ` Oliver Neukum
2006-10-28 16:56 ` Soeren Sonnenburg
2006-10-28 17:03 ` Oliver Neukum
2006-10-28 17:36 ` Soeren Sonnenburg [this message]
2006-10-28 18:14 ` [linux-usb-devel] " Sergey Vlasov
2006-10-28 18:14 ` Pete Zaitcev
2006-10-28 18:30 ` [linux-usb-devel] " Oliver Neukum
[not found] ` <200610282043.59106.oliver@neukum.org>
2006-10-28 18:55 ` Fwd: " Oliver Neukum
2006-10-28 19:14 ` Fwd: " Pete Zaitcev
2006-10-28 20:27 ` Fwd: Re: [linux-usb-devel] " Soeren Sonnenburg
2006-10-30 10:12 ` Joseph Fannin
2006-10-30 12:43 ` Soeren Sonnenburg
2006-10-30 20:05 ` Joseph Fannin
2006-11-01 20:47 ` Soeren Sonnenburg
2006-12-08 17:19 ` [PATCH] usbhid quirks for macbook(pro) (was: Re: Fwd: Re: [linux-usb-devel] usb initialization order (usbhid vs. appletouch)) Soeren Sonnenburg
2006-12-10 2:08 ` Joseph Fannin
2006-12-15 8:36 ` Soeren Sonnenburg
2006-12-15 17:56 ` Greg KH
2006-12-23 10:38 ` [PATCH] usbhid quirks for macbook(pro) updated to 2.6.20-rc1 Soeren Sonnenburg
2007-01-27 14:08 ` [PATCH] usbhid quirks for macbook(pro) updated to 2.6.20-rc6 Soeren Sonnenburg
2007-01-29 9:38 ` Jiri Kosina
2007-01-29 10:59 ` Soeren Sonnenburg
2007-01-30 15:27 ` Jiri Kosina
2006-10-28 19:14 ` [linux-usb-devel] usb initialization order (usbhid vs. appletouch) Sergey Vlasov
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=1162056992.9216.3.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.org \
/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