From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Fri, 07 Aug 2009 00:27:17 +0000
Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath
Message-Id: <ac3eb2510908061727s28cd687er1b002e4e5aaf8652@mail.gmail.com>
List-Id: <linux-hotplug.vger.kernel.org>
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

On Fri, Aug 7, 2009 at 00:03, Mario
Limonciello<mario_limonciello@dell.com> 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 --devpath=
=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.

Thanks,
Kay