Arthur Othieno wrote:
> IMHO, you're better off going with the bus-layer -> device-driver
> architecture, initially. That way, the bus driver handles things like
> probing for and maintaining a list of existing devices, binding device
> drivers to devices, handling PM and hotplug events, etc, while device
> drivers handle stuff like enabling the device, accessing configuration
> space and communicating with the drive.
> Don't get me wrong here - if you feel more comfortable starting with your
> approach, feel free to do so. We can always move over later on :)
You're right :) !!!! But the "temporary" driver is written :), it need
more tests (it's a port of the GCLIB driver so it should work correclty
(i hope) :)
I will work on the SI driver...
Regards, Free The Cube.