[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MiNT] XHDI driver for USB mass storage devices. Time to decide ;)
Hi all, I would like to decide something regarding the XHDI driver for
USB mass storage devices.
I do a small resume of the possibilities I got till now.
1) Driver as kernel module.
1.a) Apply the patch to the kernel to add XHNewCookie function in
the kentry struct.
2) Driver as TSR to be loaded before MiNT kernel in the AUTO folder.
Here the main problem is how to communicate between the TSR and the
USB core module.
2.a) Using a pseudo-device "usb" in /dev that use to be
implemented for user space applications.
(see thread "[MiNT] Using device files in "/dev" from kernel space" in
http://sparemint.atariforge.net/mailinglist/Mailing-Lists/MiNT-List.201012/Index.html
). I think it can be done but I think is not correct to do it, but I'm
no really sure. In theory the TSR is kernel space.
If this is possible, we can also use it with the USB device drivers
modules, and allow the use of .km loadable/unloadable modules for the
device drivers too. This is a very nice feature for the USB drivers
development otherwise the USB core should be unloaded and loaded again
every time a new USB device driver must be loaded.
2.b) USB core places a cookie with a pointer to a table of
function pointers.
...hmmm
Does anybody think about another alternative? If not.... which one of
the mentioned above do you think is the less bad option?
Personally I think 1.a).