/sys/bus/spi/devices/spi10.0/modalias:harc_xxsc /sys/bus/spi/devices/spi10.0/uevent:DRIVER=harc_xxsc /sys/bus/spi/devices/spi10.0/uevent:PHYSDEVBUS=spi /sys/bus/spi/devices/spi10.0/uevent:PHYSDEVDRIVER=harc_xxsc /sys/bus/spi/devices/spi10.0/uevent:MODALIAS=harc_xxsc I've also tried matching the DRIVER attribute, which also works to execute a script but will not create a device node. udevadm monitor --environment info UDEV [3737.206959] change /devices/80000000.soc/80011a00.spi/spi10.0 (spi) UDEV_LOG=3 ACTION=change DEVPATH=/devices/80000000.soc/80011a00.spi/spi10.0 SUBSYSTEM=spi DRIVER=harc_xxsc MODALIAS=harc_xxsc SEQNUM=5212 On Wed, May 27, 2009 at 8:43 AM, Kay Sievers <kay.sievers@xxxxxxxx> wrote: > On Wed, May 27, 2009 at 15:37, Luke Harvey <digilogik@xxxxxxxxx> wrote: >> I have a spi device that I am trying to get to work with udev. I >> currently have a udev rule written that will execute a script so I >> know the udev rule is valid. I can also make it execute mknod to >> create a device node in /dev. What I would like to do is have udev >> create the device node for me without using the mknod call. >> >> -Working Rule- >> SUBSYSTEM=="spi", KERNEL=="spi10.0", RUN+="/bin/mknod /dev/thedevice c 252 0" >> >> -Want to work rule (not working)- >> SUBSYSTEM=="spi", KERNEL=="spi10.0", NAME="thedevice" > > How does the kernel device look like? > > What does: > grep . /sys/bus/spi/devices/spi10.0/* > say? > > Kay > -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
