linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@leogic.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev or kernel broken with rsdl 0.30 patch
Date: Fri, 16 Mar 2007 12:32:06 +0000	[thread overview]
Message-ID: <200703161332.06365.aj@leogic.com> (raw)
In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net>

Am Freitag, 16. März 2007 13:08 schrieb Kay Sievers:
> If you run:
>   udevtest /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0
> it works, right?

yes, I booted both kernels once more and tested this, and the output is 
exactly the same, and it runs openct_usb in both cases.

> It that works, it seems the sysfs files are not created at the time you
> want to read them, and the attribute creation time needs to be fixed in
> the kernel.

ok. that seems likely, with rsdl the kernel has different timings and that 
seems to trigger the problem.

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?


> > ok. so until that patch is in the kernel (or udev? or both?),
>
> A patch to the kernel, and a rule to udev, to create the nodes
> in /dev/bus/usb, from the event of the real usb-device in /sys/devices
> instead of the current class device.
>
> > /dev/bus/usb
> > will not work for udev users as /proc/bus/usb replacement, since the
> > rules to match the attributes of the usb device won't work. right?
>
> That works fine, to match device properties. but not to match interface
> properties of that device. It only works with HAL, because it has a
> weird hack to look at the sibling device.
>
> > is there some page documenting the compatiblity issues with udev
> > and the kernel? this might be interesting for other people as well.
>
> As usual, unfortunately no there is not documentation besides what the
> distros are doing with it.

the kernel has the requirement document which documents which version
of udev is needed. it could be a good start to put this as list on the net / 
which kernel needs which minimum udev.

I ran into udev/kernel incompatibilities at least once (but my fault, didn't
check that document properly).

Thanks,

Andreas

-------------------------------------------------------------------------
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 12:32 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 [this message]
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
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=200703161332.06365.aj@leogic.com \
    --to=aj@leogic.com \
    --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).