Hi Benjamin, > I don't think class device is the right approach. Classes are supposed > to be a functional binding, ie, in this case, input devices. ADB is a > bus, and as such, you should create an adb bus type and and adb_device > that is an extension of struct device, not struct class device. ok, I'll work on that.
> There's also the question of what to do on ADB resets (such as when > doing a sleep/wakeup cycle). Should we wipe out all devices and > re-created them, thus loosing any settings ? Or should we have some way > to attempt at re-matching existing ones ? or maybe generate disconnect/connect events so udev rules can reconfigure each keyboard? -- Aristeu _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
