On Mon, 28 Sep 2015, Carlos E. R. wrote:
El 2015-09-28 a las 12:48 +0200, Xen escribió:
Not exactly.
A driver is some software to interface with a certain hardware that does something. Like telling the video driver: paint me a square of this size, color, and position, and the hardware then goes and does it, on its own, once the driver writes the directions.
The fake raid hardware does nothing. It is just the same as the separate disks with their interfaces. The CPU does it all, in code. Not driver.
Don't confuse what Windows calls "driver" :-)
I'm not sure why you keep making this distinction as if to drive a point? I have already accepted that the hardware does not processing nor does it offer a different model of its connected harddrives to the OS. However what we call the driver reads the "RAID configuration" you have made in the card's BIOS and then supplies a unified 'RAID' model of these drives (that the card doesn't do by itself) to the OS. Also "The CPU does it all, in code. Not driver" is a pretty meaningless statement since the CPU is executing driver code. What else do you think it is executing? A CPU is not a software entity. I think you can stop this now. It is the driver that is providing raid capability to the OS. The same as in Linux, pretty much, with dmraid. Regards, B.