io port list?

[assembler01]

Is there any place where one can find a list of the io ports when using the in/out instructions? I have checked all over the internet but could not find anything.
PS: I do not use Google because they track you, duckduckgo.com does not track you.

[bubach]

Seriously?
http://bochs.sourceforge.net/techspec/PORTS.LST

First Google hit... -.-

PS: saw that remark about google now. are you so afraid of some ad-showing algorithm that you can't use a good search engine? subscribe to a proxy service or better yet, take that paranoia down a notch.

[Brynet-Inc]

With the exception of some standard devices, which may not always exist, an all encompassing list can often be found in the chipsets documentation.

[gerryg400]

PS: I do not use Google because they track you, duckduckgo.com does not track you.

Go to the library and use google.

[Combuster]

Paranoid and no Tor?

Anyway, this should go into the FAQ sometime...

[bubach]

Anyway, this should go into the FAQ sometime...

http://wiki.osdev.org/I/O_ports

Not exactly pretty (not at home with wiki markup), but at least it's preserved now.

[Brendan]

Hi,

Anyway, this should go into the FAQ sometime...

http://wiki.osdev.org/I/O_ports

Not exactly pretty (not at home with wiki markup), but at least it's preserved now.

Who owns the copyright to that list, and do we have permission to include it on the wiki?


Cheers,

Brendan

[Combuster]

I just turned the 1:1 copy into a link at the reference section where it should have been in the first place, and added some flesh around it for the interesting parts. I think this is the better solution in general.

[bubach]

The file was first created well before this hysteria with putting a label on everything came about. It's been passed along freely for like 20 years now and information has been added by several people since the first versions.

Here is what seem to be an even newer version, apparently part of Ralf Browns interrupt list. Looks like he added a text about distribution that says it should be accompanied by the original interrupt list. Outdated BBS/FTP "rules". Whatever rights he had to make such a demand in the first place since he's not the original author...

http://www.eithel.net/download/assembler/ports.txt


I understand the need to be careful, but there has to be some limits. Outdated information from what obviously is "that eras" version of freeware/pd? Like i said, most stuff from this time period never even mentions a license, it's implied to be free. Who would possibly even care now days about this old stuffs distribution on a wiki when it's been all over the net for 10+ years already?

Anyway, whatever. If you rather copy paste out the information by hand to sleep better at night, go right ahead. As long as it's used and I don't have to be the one to do it.

Let the flamefest about my ignorance and stupidity beeeegin!

[Brendan]

Hi,

Like i said, most stuff from this time period never even mentions a license, it's implied to be free.

I'm not a lawyer; but as I understand it that is definitely not how copyrights work, or have ever worked. If there's no mention of a licence, then by default it's copyrighted by it's original author/s and no copy can be legally made until copyright expires (excluding "fair use" exclusions).

Anyway, whatever. If you rather copy paste out the information by hand to sleep better at night, go right ahead. As long as it's used and I don't have to be the one to do it.

It's probably better to provide a link to it.

I'd also point out that nobody should actually need a list of all IO ports. If you're writing PIT code you find out the IO ports to use (and how to use them) from the PIT page, if you're writing a floppy driver you use the floppy page, if you want to write a serial port driver you see the serial port page, etc. People only think they need a list of all IO ports when they're planning to implement all of the device drivers they'll ever want in the same 2 hours of coding (and I'm sure when they do find a list of IO ports they say "Doh!" and never read it)..


Cheers,

Brendan

[bubach]

I'm not a lawyer; but as I understand it that is definitely not how copyrights work, or have ever worked. If there's no mention of a licence, then by default it's copyrighted by it's original author/s and no copy can be legally made until copyright expires (excluding "fair use" exclusions).

Yes of course, I didn't mean copyright doesn't apply. I meant that they allowed free distribution of the information - in the same way that CC0 works for all countries where there is no such thing as public domain and the author always hold copyright.


That's basically why I thought it was a bit silly to hunt down all old contributers of the OS-FAQ to get everything covered by CC0. It's a wiki, if someone writes something on it - that in itself should be evidence enough that you can freely use it. For code samples it's another thing, for shorter snippets without license mention (again - on a wiki) I would assume it's PD unless otherwise mentioned. For bigger code peaces a license would probably be mentioned anyway - or you would assume it's the same as for the OS it originates from. Common sense is never enough these days, bureaucracy is getting the better of us. Now that it's done, I suppose it doesn't matter, but my opinion will remain that it was an unnecessary step.

I'd also point out that nobody should actually need a list of all IO ports. If you're writing PIT code you find out the IO ports to use (and how to use them) from the PIT page, if you're writing a floppy driver you use the floppy page, if you want to write a serial port driver you see the serial port page, etc.

While that is true in most cases, there might be rare occasions where a list like this clarifies why you need to do something in a certain way - instead of using it like magic numbers you get very specific information what each port does, whats bits to set for different configurations not otherwise covered in a quick and dirty tutorial.

But never mind, Combuster did a good job on the design of that page and I think that most of the info will eventually find it's way onto that page.

[Solar]

That's basically why I thought it was a bit silly to hunt down all old contributers of the OS-FAQ to get everything covered by CC0. It's a wiki, if someone writes something on it - that in itself should be evidence enough that you can freely use it.

But it's not. Not in the US, not in the UK, in Germany or elsewhere. Of course you and I and everybody else on this board understand what it should mean morally, but morals don't hold up in court.

Even the understanding of the term "free" varies significantly! Some understand "free" to mean copyleft, others understand "free" to mean PD/CC0. Did you know that putting GFDL texts into Wikipedia will be considered a copyright violation? Copyright law is a b*tch.

...I would assume...

Don't. "Assuming" in the world of cease & desist letters can cost you dearly.

Common sense is never enough these days, bureaucracy is getting the better of us.

+1.

[assembler01]

Hey its me again. I've been away because my computer crashed and I needed to reinstall everything, anyway, I found out that if you are using linux with kde desktop you can open an application called kinfocenter, then you go to device information and IO-Ports and there all your io ports are listed.

http://bochs.sourceforge.net/techspec/PORTS.LST

First Google hit... -.-

Great list. Google is the best search engine out there but they have only one problem, they track you, and I for one do not want to be tracked, (not because I have something to hide but I just don't wana be tracked).

[Solar]

Google is the best search engine out there but they have only one problem, they track you..., and I for one do not want to be tracked, (not because I have something to hide but I just don't wana be tracked).

I can actually understand that.

But that only means you should use a different search engine, not that you are excused from trying to find information yourself first. I found the desired information via e.g. duckduckgo.com with equal ease.

That being said, +1 for Tor.

[assembler01]

Great list. Google is the best search engine out there but they have only one problem, they track you, and I for one do not want to be tracked, (not because I have something to hide but I just don't wana be tracked).

Hey, cut the bullfeces please. Use TOR or anonymous proxies. This forum also tracks you, so you might want to consider not using it anymore.

What I meant when I said that google tracks you is that google sends information about you to the website you clicked on. When you use a proxy you are using SOMEBODY ELSE'S ip num, and also, then google tracks that somebody else.