On Mon, Dec 01, 2008 at 03:57:01PM +0000, Andy Green wrote: > Somebody in the thread at some point said:
> | It's never keeping track of the state it wants at all, it's attempting > | to force a particular physical state without reference to the logical > | state. If it were keeping track of the state it wants it would only do > | so at startup. > There's some more "dodgy" code in probe() for this. Anyway I'll replace > it with the boot_on attribute thing... for bt case it's okay to force it > off and then we at least start on a consistent footing. If it's doing it on probe that's fine and reasonably expected - it's when it's being done as part of the normal runtime decision making that it looks suspicious.
