On Tue, 16 Jun 2009, Martin Shepherd wrote: > On Wed, 17 Jun 2009, Thomas Gleixner wrote: > > > It seems much more friendly and efficient for my driver to provide > > > applications with an ioctl that tells it to set the priority of its > > > IRQ thread. > > > > Wrong. That information is already available in sysfs and there is no > > reason to use an ioctl for that. > > Could you point out where please? Searching sysfs I see the following > two files that contain the IRQ numbers of two of the boards that my > driver handles: > > /bus/pci/drivers/accpcidio/0000:03:02.0/irq > /bus/pci/drivers/accpcidio/0000:03:03.0/irq > > However, I don't see how a user application could figure out which of > these corresponded to the board that it opened using a particular > device file. Only the device driver knows which device file is > associated with a given PCI device ID, and that isn't recorded in > sysfs. Errm, and how does udev figure out which device node to create for which device ? /sys/devices/pci0000:00/0000:00:1d.7/usb1/dev Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
