Using udev-extras for hardware-specific quirks?
ddstreet at ieee.org
Mon Jun 1 09:13:01 PDT 2009
I am creating udev rules for some system units I'm responsible for
enabling Linux on; specifically these systems have multiple serial
ports with labels on the ports like "A", "B", "C", etc. However on
many of the units the hardware doesn't match the labelling so ports
"C" and above usually do not match the right serial node, i.e. while a
port labeled "C" should be /dev/ttyS2 it isn't.
The initial udev rule I set up for one system is below - just as an
example of what I'm planning on creating. As you can see this
particular system has a PCI serial card, with the middle 2 ports
actually wired up to the rear panel and labeled "C" and "D". The
other 4 ports aren't actually wired up, so this rule could be changed
to ignore those instead of creating nodes for them.
Anyway, my question is, is udev-extras the appropriate place for this
to live? I would like to put the rules into a standard location that
all distros can pull from. It seems like DeviceKit and udev-extras is
the direction that everything is going in, but I'm not sure if
udev-extras is intended to hold system-specific quirk rules like this.
If it is, then I would like to get this added once we finish up all
the rules for our system units. Also, any comments/suggestions on how
I'm writing the rules are welcome.
More information about the devkit-devel