> Maybe we can get the kernel drivers to expose the information we need > (maybe even an 'eject' attribute in sysfs or something) and then we just > have to write udev rules instead of having a whole bunch of libusb junk > in userspace? Would that preserve the policy-always-in-userspace > requirement yet keep the code to drive the hardware in kernel space > where it really belongs? Or put the magic strings in the kernel with a translation hook for the eject request ? That would keep policy and method in the right places. You ask the kernel to eject, it hides the magic weirdness. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
