It wants to. What happens is this
- The IDE layer detects the raid chip
- We check it isnt a supertrak hardware raid
- If it isnt we add the chips as basic ide devices
- The ataraid module loaded on top of those opens the ide disks and
hunts for promise and hpt raid descriptors
- When it finds the raid descriptor it creates an additional
/dev/ataraid/.... device
Because our ataraid driver actually sits on top of the existing IDE drivers it
requires they grab the devices. This also allows end users to issue commands
directly to the drives (for example for SMART)
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/