From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Fri, 07 Aug 2009 00:57:53 +0000 Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath Message-Id: List-Id: References: <4A6E19FF.5070207@dell.com> In-Reply-To: <4A6E19FF.5070207@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Hey Marcel, On Fri, Aug 7, 2009 at 02:44, Marcel Holtmann 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}=3D"1", RUN+=3D"hid2hci --method=DEll --devpa= th=3D%p" >> >> > Thanks for the suggestion! =C2=A0 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