From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Jellinghaus Date: Fri, 16 Mar 2007 12:32:06 +0000 Subject: Re: udev or kernel broken with rsdl 0.30 patch Message-Id: <200703161332.06365.aj@leogic.com> List-Id: References: <20070315104654.19025CA4097@mx1.ciphirelabs.net> In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Am Freitag, 16. M=C3=A4rz 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=20 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 ude= vd 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 = /=20 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=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ 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