OSDev.org

tatOS now has support for the EHCI usb controller for both the flash drive and usb mouse.

The source code may be a worthwhile study for those who are interested in developing their own drivers for usb.

To boot tatOS, copy the file tatos.img to floppy or cd. I have also been able to boot several newer computers using a flash drive.

For those who are able to boot this OS, I would be interested in knowing your usb controller DID (deviceID) and VID (vendorID). This info can be obtained by pressing F6 after boot up and scrolling thru the dump messages.

Thanks for trying tatOS

TomT

http://code.google.com/p/tatos/

Great job, nice to see full asm OS's

Thanks Dex.

Long live the assembly language OS developer.

We must be crazy, or there would be more of us.

So why do you program in assembly ?

TomT

Your welcome, i code in asm because at the time i started coding, i found it the easiest to lean, I could just not get my head around C.
I learnt pascal, which i found fine, as a project i started to code a pascal OS, but the pascal OS end up 10% pascal, 90% inline asm, so i switched to full asm.

The best part is as theres no libs, any faults is down to you, the coder.

PS: I have no EHCI support in my OS, so when i get time i will port your code (giving you credit) to my OS.
So thanks for posting it.

Hi TomT

I tested tatOS jan10 on some real hardware. Test farm details.

You can find pictures of tatos running on 4 machines here: http://softwarewizard.dk/mojo/index.php ... album&id=5

It starts up alright on all machines although it doesn't recognize the USB controllers correctly in all cases. You can see the details on the screen shots.

I only tested briefly and took pictures of the CPUID output. I didn't test any of the USB functionality (I only have PS/2 HID devices attached right now and no USB sticks). But if you make a brief outline of what you would like tested I would gladly do it. Something like:

• 1. do this,

• 2. do that,

• expected output or take a picture.

I just don't want to waste time (mine or yours) by fumbling around and testing the wrong stuff.

If you need more info about the test machines let me know.

Last but not least: nice project - a looked briefly at the code and I like it. Keep up the good work - I'll be happy to help you test.

clange

EDIT: grammar

Hi clange,

Thanks for trying tatOS.

Your "CPUID on Lithium" screenshot is very interesting. I did not know that tatOS graphics could display a fractured screen with such clarity

On those machines where it did not detect the USB controller properly, could you do the following:

1) press F6 immediately after you get to the plain blue startup screen. This displays the contents of the "dump" which would be the equivalent of dmesg on linux. You can pageup/dn and view a bunch of USB controller parameters like the DID and VID of your controller... If you would take a picture of this dump screen I would be grateful.

thanks,

TomT