Ian Jackson <ijackson <at> chiark.greenend.org.uk> writes:
>
> 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.
Yes, that is correct. The bug is in the firmware of the PIC
microcontroller.
>
> > > 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 ?
>
This is main problem. Both the drivers try and control the device. The
only work around I could come up with was to pass a usbhid quirks to
ignore this specific board and then load the custom driver.
Thanks for the reply.
--
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/loom.20120918t191704-...@post.gmane.org
