On Wed, 25 May 2011, Oliver Neukum wrote: > Am Mittwoch, 25. Mai 2011, 16:14:29 schrieb Arvid Brodin: > > So one solution would be to create a chain of pipes, running something like > > 'tail -f /var/log/messages | egrep "hub.*over-current change"' and read the > > output from this in the program. Is there a better way (some kind of sysfs > > interface for port power state, maybe)? > > Eek. It seems to me that the cleanest solution would be to have > a charachter device per hub that allows such conditions to be polled > for. There are plenty of error conditions that the kernel does not export to userspace. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
