"Marco d'Itri" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: > >>> These two cases are well different: the first driver already contains >>> all code needed to manage the hardware device (even if it chooses to not >>> send some commends to the device until it will be ready to process them), >>> in the second case the program is not complete and lacks some parts. >> >>The driver contains code to interact with the firmware in operating the >>hardware device, just as the program contains code to interact with the >>library in performing its function. > No, this is again wrong: a program and the libraries it use are a single > entity (why do you think it's called linking?) while drivers and devices > are different entities. > They interact the same way IM clients and servers interact.
>From the point of view of userspace, a driver, device, and any firmware on it are one abstract entity. -Brian -- Brian Sniffen [EMAIL PROTECTED]
