Hi, again (sorry for that),

I noticed this code:

https://github.co...b/denebusb

I am getting in a complicated scenario (at least for me).

I would need an usb support from the arm side (it is allready working, I have emulated keyboard and mouse)

I would need an early init usb support (for the mass storage device)

And, in the end I would need a dwc2.device to be presented in the OS installation.

I am not sure if I’m thinking of this properly but I woul like to avoid duplicate code, and have lots of unanswered questions.

Should I use hidd approach? Have an expansion/autoconfig is correct for the initial resident support that later will be replaced by the os .device?

Have the usb exposed on the autoconfig will be enough to aros search for bootable files?

Questions, that I don’t even know if it make sense. But I would get rid of Gayle/atapi/CD-ROM at once as none of this would exists on raspberry pi 3b

I am not sure if I’m going to the right path, maybe the adf and automount iso would be the right step for the moment

I allready have floppy and atapi somewhat alive, and go to usb would be more complex and even more moving parts.

If someone more experienced could give a hint, at least for what path I should pursue first I would appreciate,

Kind regards,

Ps: this an xhci device reference

https://github.co...hci-driver

(I would need to make a dwc2 in the case of raspberry pi 3b, to be installed in the os)

And this is the emu68 sdcard driver (rom) also for reference https://github.co...s/sdcard.h

(I would need some usb driver/rom for the early init support)

I didn’t approached the hidd stuff just to don’t go crazy in just one move 🙃

I am talking of 3 handsoff of the stack (arm->early init->OS), it sounds crazy enough allready.