![]() | |||||||||||||
Messages in this thread |
Am Sonntag, 14. Januar 2007 20:47 schrieb icxcnika@mar.tar.cc: > > Can anyone suggest another approach?> >> > Alan Stern> > Just a thought, you could use both a blacklist approach, and a module > paramater, or something in sysfs, to allow specifying devices that won't > be suspend and resume compatible. Upon further thought, a module parameter won't do as the problem will arise without a driver loaded. A sysfs parameter turns the whole affair into a race condition. Will you set the guard parameter before the autosuspend logic strikes? Unfortunately this leaves only the least attractive solution. Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-01-15 12:43 [from the cache] ©2003-2008 | |||||||||||||