On Tue, Jan 25, 2011 at 15:07, Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote: > On 01/25/11 14:39, Kay Sievers wrote: >>> +dist_udevrules_DATA += extras/qemu/99-qemu-usb.rules >> >> The number should be 10-90 for the default things, or is there a >> dependency on anything else? > > No dependency at all. ÂWhat number do you suggest then? Doesn't really matter, we just leave 00-09 and 91-99 for other custom stuff, to get easily before and after the common things. >> That could go in the compat rules, udev does not ship rules for older >> kernels in the default installation. > > Ok. ÂIs there some way to express "power/control doesn't exist but > power/level does" as udev rule, so I can zap the shell script? TEST=="" should do that. >> Anyway, why isn't all this done in the kernel? Can't this be made >> working somehow? > > As far I know the kernel doesn't do that by default because too much broken > hardware is out there which breaks when autosuspend is enabled by default. Yeah, there is a reason not to do that for all devices, there are too many broken ones. > I saw mentioned somewhere the plan is to have udev enable this for > known-good devices, so I'm trying that route :) Oh, yeah, nice idea. That's the reason there is no list at all. :) > Havn't checked whenever there is a in-kernel white list for that stuff which > could be used instead. Yeah, would be nice to have some generic way to enable autosuspend when the hardware (real or emulated one) hints that it supports that. Not sure how it would look like in detail though. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
