[RFC] MPIC Bindings and Bindings for AMP Systems
Hollis_Blanchard at mentor.com
Sat Jan 8 03:00:42 EST 2011
On 01/07/2011 07:48 AM, Grant Likely wrote:
> Actually, for a while now the kernel has been moving towards userspace
> being responsible for device identification. That's what udev is for.
> The kernel udev looks at the available information when a device is
> registered/bound, and it creates useful symlinks to the dynamically
> assigned major/minor devices. The rest of userspace doesn't need to
> know about it; it can simply use the symlinks in /dev, but it is
> appropriate to let udev figure out the correct naming.
Can you point out an example of how this is done for Open Firmware
devices currently? In particular, how are the udev rules supposed to
operate? They get a device path, use that to find additional information
in /proc/device-tree (hope that's mounted), and then what? Do we
hardcode the block addresses in the rules, for example @1400 and @2400?
Mentor Graphics, Embedded Systems Division
More information about the Linuxppc-dev