linux-kernel - Re: usb initialization order (usbhid vs. appletouch)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 28 Oct 2006 11:14:54 -0700
From:	Pete Zaitcev <zaitcev@...hat.com>
To:	Soeren Sonnenburg <kernel@....de>
Cc:	Oliver Neukum <oliver@...kum.org>,
	linux-usb-devel@...ts.sourceforge.net,
	Linux Kernel <linux-kernel@...r.kernel.org>, zaitcev@...hat.com
Subject: Re: usb initialization order (usbhid vs. appletouch)

On Sat, 28 Oct 2006 18:56:16 +0200, Soeren Sonnenburg <kernel@....de> wrote:

> > > > > I've noticed that the appletouch driver needs to be loaded *before* the
> > > > > usbhid driver to function. This is currently impossible when built into
> > > > > the kernel (and not modules). So I wonder how one can change the
> > > > > ordering of when the usb drivers are loaded.
> > > > > 
> > > > > Suggestions ?
> > > > 
> > > > Add a quirk to HID. Messing around with probing orders is not
> > > > a sure thing.
> > > 
> > > what do you have in mind ? if appletouch is turned on ignore IDs that
> > > appear in appletouch ?
> > 
> > Yes, or even make it unconditional. There is a specific driver for a device.
> > It exists for a reason.
> 
> OK, so I tried adding all of them to the HID_QUIRK_IGNORE LIST, i.e.

This, of course, cannot possibly work, as we discussed a month ago.
 http://lkml.org/lkml/2006/10/1/18

So, you two are just beating a dead horse. It's time to write the code
which identifies Apple devices and not try to ride a quirk.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/