linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev or kernel broken with rsdl 0.30 patch
Date: Fri, 16 Mar 2007 13:58:21 +0000	[thread overview]
Message-ID: <1174053501.21549.71.camel@lov.localdomain> (raw)
In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net>

On Fri, 2007-03-16 at 14:35 +0100, Andreas Jellinghaus wrote:
> Am Freitag, 16. März 2007 13:48 schrieb Kay Sievers:
> > > what exactly is "wait_for_sysfs"? I'm asking because it shows up in the
> > > udevd log right before openct is started / should be started. I thought
> > > it would take care of problems like this? or does it only check the
> > > basedir, and not the subdirs / files in the dirs to be present or
> > > something like that?
> >
> > It waits for what you ask it to wait for. This may work:
> >   SUBSYSTEM="usb", KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceProtocol"
> 
> I tried it like this:
> BUS!="usb", ACTION!="add", GOTO="openct_usb_rules_end"

What do you mean here? You only skip the rules if it's !usb _and_ !add.
So any other subsystem will enter here. It should probably be:
  ACTION=!"add", GOTO="openct_usb_rules_end"
  SUBSYSTEM=!"usb", GOTO="openct_usb_rules_end"

And don't use BUS=, it will search all devices in the devpath, but you
need only want to see real usb-device events, not other classes of
devices that are childs of any usb-device.

> KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceClass"
> KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceSubClass"
> KERNEL="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceProtocol"

You only need bInterfaceProtocol, it's the last file created by the
kernel.

> SYSFS{bInterfaceClass}="0b", SYSFS{bInterfaceSubClass}="00", 
> SYSFS{bInterfaceProtocol}="00" RUN+="/lib/udev/openct_usb"
> 
> LABEL="openct_usb_rules_end"
> 
> i.e. with extra lines in the config file. is that correct? now I have a 50/50
> chance that openct_usb run (I plugged in&out 15 times for testing).
> and I get lots of warnings during boot because some usb hardware
> doesn't have these attributes. is there a way to restrict them to 
> everything that has a usb device file?

It's probably because you match all sorts of devices which aren't usb.

Kay


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2007-03-16 13:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 10:46 udev or kernel broken with rsdl 0.30 patch [u] Andreas Jellinghaus [c]
2007-03-15 15:22 ` Kay Sievers
2007-03-15 17:03 ` udev or kernel broken with rsdl 0.30 patch Andreas Jellinghaus
2007-03-15 19:57 ` Kay Sievers
2007-03-16 10:06 ` Andreas Jellinghaus
2007-03-16 10:35 ` Kay Sievers
2007-03-16 10:59 ` Andreas Jellinghaus
2007-03-16 11:34 ` Kay Sievers
2007-03-16 11:45 ` Andreas Jellinghaus
2007-03-16 12:08 ` Kay Sievers
2007-03-16 12:32 ` Andreas Jellinghaus
2007-03-16 12:48 ` Kay Sievers
2007-03-16 13:35 ` Andreas Jellinghaus
2007-03-16 13:38 ` Andreas Jellinghaus
2007-03-16 13:58 ` Kay Sievers [this message]
2007-03-16 14:39 ` Andreas Jellinghaus
2007-03-16 14:59 ` Kay Sievers
2007-03-16 15:20 ` Andreas Jellinghaus
2007-03-16 15:39 ` Kay Sievers

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=1174053501.21549.71.camel@lov.localdomain \
    --to=kay.sievers@vrfy.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).