Hello all,
I've got a quick question:
Currently, I've been working off of examples and tutorials, which has gotten me pretty far.
I'd like to get a reference of sorts so I can try things on my own, rather than following a tutorial.
The main thing I haven't seen, is a list of outb uses.
E.g, what ports do what, and take what args, etc.
Is there a reference for this somewhere?
Also, I think the PDF manuals would be really useful from intel.
Is there a chm/html version around, somewhere?
PAdobi and pdf don't work well with the reader, and the pdf conversions usually end up looking really horrible.
Thanks,
AzAr
outb list?
Re: outb list?
Use the search function.
http://forum.osdev.org/viewtopic.php?f=1&t=17588
http://forum.osdev.org/viewtopic.php?f=1&t=17588
managarm: Microkernel-based OS capable of running a Wayland desktop (Discord: https://discord.gg/7WB6Ur3). My OS-dev projects: [mlibc: Portable C library for managarm, qword, Linux, Sigma, ...] [LAI: AML interpreter] [xbstrap: Build system for OS distributions].
- naiksidd_85
- Member
- Posts: 76
- Joined: Thu Jan 17, 2008 1:15 am
Re: outb list?
http://bochs.sourceforge.net/techspec/PORTS.LST this link to bochs site may be handy but you will have to read all the manuals and specification its the only way out.
Learning a lot these days THANKS to OSdev users
- AndrewAPrice
- Member
- Posts: 2309
- Joined: Mon Jun 05, 2006 11:00 pm
- Location: USA (and Australia)
Re: outb list?
This is a really tricky question and there is no definite list. outb (along with outw, outl, etc) writes a value out on an IO port. There is no definite list (that I know of) that describes every device on every possible port, and every value that device accepts.
For your common hardware (pic, floppy controller, etc) there is a lot of documentation available that describes the IO port to use, and what value you can pass to it.
For the rest of your hardware, usually this information is proprietary. There may have be attempts to reverse engineer your hardware, and even the majority of attempts that succeed don't document their findings.
Overall, I wouldn't worry too much about trying to document every possible device and what you can send to it. Rather, do your research as it's needed (as you require hard drive access, research the the hardware controller then).
For your common hardware (pic, floppy controller, etc) there is a lot of documentation available that describes the IO port to use, and what value you can pass to it.
For the rest of your hardware, usually this information is proprietary. There may have be attempts to reverse engineer your hardware, and even the majority of attempts that succeed don't document their findings.
Overall, I wouldn't worry too much about trying to document every possible device and what you can send to it. Rather, do your research as it's needed (as you require hard drive access, research the the hardware controller then).
My OS is Perception.