OSDev.org

Octocontrabass wrote: ↑Fri Aug 29, 2025 3:57 pm How good do you want your driver to be? If it only needs to work on your computers, you can detect the model with something like SMBIOS and apply whatever model-specific workarounds you need that way. If you want it to work on lots of computers, it'll be faster to implement a proper USB driver.

I'd rather have a clean OS, that works on most-ish computers. I guess I'm gonna have to go USB then...

Thanks a lot BenLunt for the insights. I haven't written an NVMe driver yet, but I plan to. Do you think it would be better to write it before or after USB controllers drivers ?
I think I will start with UHCI driver, then jump to xHCI. And thanks for the book's link

Magyar57 wrote: ↑Sat Sep 06, 2025 3:59 am I haven't written an NVMe driver yet, but I plan to. Do you think it would be better to write it before or after USB controllers drivers?

I favor the USB, but either/or. One has little or nothing to do with the other.

Starting with the UHCI, even though it is obsolete, is a wise decision in my opinion, as it is a learning experience. You will learn the basics of the USB while using the simplicity of the UHCI.

While you start writing your code, keep in mind that you need to keep the Controller code and the USB code as separate as possible, not allowing one to rely upon the other. At first this isn't a big deal, since you will be learning as you go, but if you keep this in mind as you go along, it will make it much easier when you get to one of the other controllers.

Ben