Ben Finney writes: > Marco d'Itri <[EMAIL PROTECTED]> writes: > >> I am saying that the driver does not "depend" on the firmware because >> its functionality does not change if the firmware is uploaded or not to >> the hardware device. In both situations the driver is the same program, > > "is the same program" != "functionality does not change"
"cream cheese" != "wagon wheel" In other words: So what? Unlike cases where a program fails to run due to a missing interpreter, library, or whatever else, the program still runs and interfaces to the hardware per spec. If the hardware fails to perform -- because it the firmware was not loaded, because a resistor is burnt out, or whatever -- it would be nice to know why that becomes a policy issue. Michael Poole -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
