From: Juergen Beisert <jbe@pengutronix.de>
To: linux-hotplug@vger.kernel.org
Subject: How to write rules for mtd based devices
Date: Mon, 03 Nov 2008 10:12:05 +0000 [thread overview]
Message-ID: <200811031112.06061.jbe@pengutronix.de> (raw)
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="mtdblock5"
SUBSYSTEM="block"
DRIVER=""
ATTR{range}="1"
ATTR{removable}="0"
ATTR{ro}="0"
ATTR{size}="1024"
ATTR{capability}="10"
ATTR{stat}=" 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
--
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Vertretung Sued/Muenchen, Germany
Phone: +49-8766-939 228 | Fax: +49-5121-206917-9
next reply other threads:[~2008-11-03 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 10:12 Juergen Beisert [this message]
2008-11-03 10:27 ` How to write rules for mtd based devices Kay Sievers
2008-11-03 11:12 ` Juergen Beisert
2008-11-03 13:18 ` Kay Sievers
2008-11-03 13:21 ` Kay Sievers
2008-11-03 13:39 ` Juergen Beisert
2008-11-03 14:11 ` 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=200811031112.06061.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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).