Ben Hutchings writes ("Re: Handling /etc/modprobe.d and module load order"):
> On Mon, 2012-09-17 at 16:46 +0000, Amit wrote:
> > It is a driver for a PIC microcontroller board. I was using usbhid but
> > there was a bug that I couldn't work around.
>
> A bug in which?
I assume a bug in the board which Amit wanted to work around by using
a stunt version of the usbhid driver.
> > I haven't thought of this. How does this work in the case when usbhid
> > already has the device in its device ID table.
>
> They both get loaded.
And how should Amit arrange that the stunt driver, not normal usbhid,
gets control of the device ?
Ian.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20568.20278.966711.586...@chiark.greenend.org.uk
