>> How can you be sure that the module doesn't leave accessed hardware (if it's
>> a driver) in an unusable state, or, leaves some other rubbish behind?
> You can't. But a module should at least reset *all* registers of a
> hardware component to default values (say: a defined state) before
> anything else.
Right.
(Just checking whether I'm understanding things :)
> Trust no-one.
"Beware of this code - I have proved it correct, but I haven't tested it!"
(-- Knuth?)
--
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
cat /dev/boiler/water | tea | sieve > /cup
mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/