Re: DRIVER vs. PHYSDEVDRIVER for block susbsystem

[Kay Sievers <kay.sievers@vrfy.org>]

On Sat, Mar 25, 2006 at 10:10:38PM +0300, Andrey Borzenkov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Saturday 25 March 2006 21:50, Kay Sievers wrote:
> > On Sat, Mar 25, 2006 at 09:24:30PM +0300, Andrey Borzenkov wrote:
> > > The example persistent rules distributed with udev use DRIVER matching
> > > for SUBSYSTEM=block. Unfortunately, it appears that DRIVER is simply not
> > > defined in this case - it is fetched only for the case when devpath is
> > > /devices/* not /block/*.
> >
> > No DRIVER matches up the whole chain of devices. But the driver value of
> > block is "" which matches successfully the non-match of the values it is
> > compared against.
> >
> > The rules have changed and should work that way:
> >  
> > http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=etc/ud
> >ev/60-persistent-storage.rules
> >
> 
> Those rules will never match for ide-cs or ide-floppy as intended (while this 
> "fixes" it for ide-cdrom, sure :)

Care to explain?

> > We should not introduce any new users of the "device" link or the
> > PHYSDEV* values, they will go away some day along with the odd idea
> > to distinguish between class and physical devices.
> >
> > > Is DRIVER expected to be set for SUBSYSTEM=block (I will submit patch)?
> > > Otherwise it would be nice to fix examples in rules.
> >
> > No, class devices don't have a driver for now.
> >
> 
> In this case adding driver for block devices looks like the right thing, does 
> not it? Strictly speaking, it could be generalized to "if device symlink 
> exists, fetch driver from it"; this will go away when sysfs layout will have 
> changed.

No, the block devices don't have a driver.

Thanks,
Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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