Hey Marcel,
On Fri, Aug 7, 2009 at 02:44, Marcel Holtmann<marcel@xxxxxxxxxxxx> wrote:
>> >> I guess, we can get rid of all these hacks and the search code, by
>> >> tagging the mouse device we need to find, with:
>> >> ..., ENV{HID2HCI_SWITCH}="1", RUN+="hid2hci --method=dell --devpath=%p"
>>
>> > Thanks for the suggestion! I've cleaned up per this advice and am
>> > attaching a new patch.
>>
>> Great, that this works. Applied. Now lets wait for a reply, if we can
>> get libusb fixed, otherwise we will just replace the dumb scanning
>> code with our own thing.
>
> actually you might wanna do that anyway. The whole point to put hid2hci
> into udev was that we can have it run really early at boot when /usr is
> not mounted yet (I don't buy that /usr argument, but whatever). With
> libusb installed under /usr/lib that goal is moot again ;)
Yeah, that's a valid point.
We could move it to / though, if it will ever get fixed. Oh well, the
/usr on a different filesystem thing -- many things break in
not-so-interesting ways and this is just one issue on top. :)
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
