From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath
Date: Fri, 07 Aug 2009 00:44:19 +0000 [thread overview]
Message-ID: <1249605859.21101.44.camel@localhost.localdomain> (raw)
In-Reply-To: <4A6E19FF.5070207@dell.com>
Hi Kay,
> >> 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Þll --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 ;)
Regards
Marcel
next prev parent reply other threads:[~2009-08-07 0:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 21:19 [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath Mario Limonciello
2009-07-27 21:35 ` Marcel Holtmann
2009-07-27 22:36 ` Mario Limonciello
2009-07-27 22:42 ` Marcel Holtmann
2009-07-28 0:04 ` Kay Sievers
2009-07-28 18:10 ` Mario Limonciello
2009-07-31 18:53 ` Kay Sievers
2009-07-31 19:35 ` Mario Limonciello
2009-08-05 7:47 ` Kay Sievers
2009-08-06 22:03 ` Mario Limonciello
2009-08-07 0:27 ` Kay Sievers
2009-08-07 0:44 ` Marcel Holtmann [this message]
2009-08-07 0:57 ` Kay Sievers
2009-08-07 1:28 ` Marco d'Itri
2009-08-07 1:47 ` Kay Sievers
2009-08-07 3:48 ` Marco d'Itri
2009-08-11 17:49 ` Karl O. Pinc
2009-08-11 22:22 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249605859.21101.44.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).