From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Beisert Date: Mon, 03 Nov 2008 10:12:05 +0000 Subject: How to write rules for mtd based devices Message-Id: <200811031112.06061.jbe@pengutronix.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Hello list, has anybody an idea how to write some rules to match devices from the mtd framework? All I get is: ------------------------------------------------------------------ $ udevadm info -a -p /sys/block/mtdblock5 Udevinfo starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/virtual/block/mtdblock5': KERNEL=3D"mtdblock5" SUBSYSTEM=3D"block" DRIVER=3D"" ATTR{range}=3D"1" ATTR{removable}=3D"0" ATTR{ro}=3D"0" ATTR{size}=3D"1024" ATTR{capability}=3D"10" ATTR{stat}=3D" 0 0 0 0 0 0 = 0 0 0 0 0" ------------------------------------------------------------------ And its mostly the same for all the other mtdblock devices. The other frameworks like SATA and USB providing much more information about their bus controllers and connected devices to find adequate matching rules. But mtd seems very uncommunicative, or do I query the wrong path to search = for usefull rules to match? Regards, Juergen --=20 Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de =A0Pengutronix - Linux Solutions for Science and Industry =A0 Handelsregister: Amtsgericht Hildesheim, HRA 2686 =A0 =A0 =A0 Vertretung Sued/Muenchen, Germany Phone: +49-8766-939 228 | Fax: +49-5121-206917-9