Re: Clarification on IO Operations
From: Gary Kato (garykato_at_aol.com)
Date: 12/29/04
- Next message: Gary Kato: "Re: Clarification on IO Operations"
- Previous message: guruteck_at_gmail.com: "Re: Clarification on IO Operations"
- In reply to: guruteck_at_gmail.com: "Re: Clarification on IO Operations"
- Next in thread: Nick Andrew: "Re: Clarification on IO Operations"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 29 Dec 2004 08:42:52 GMT
>How I/O ports are distiguished???
They have an I/O address just as memory locations have an address. Usually,
this address is sent out the same lines are a memory address would. What
distinguishes them is that there might be a memory/io line which signals if the
address is a memory address or an I/O port address.
>How write to a port is achieved (outb)??
In Linux, yes.
> Is Writing to port equivalent
>to writing to "registers in controllers"
Yes.
>How I/O devices assigned differnt I/O ports??
Someone decides how to decode the I/O port address in the hardware design. In
the case of the IBM PC, it was IBM that set the standard that everyone
followed. Some designs have switches to enable a board to be configured at
different addresses. Some boards use a configuration memory (usually an EEPROM)
so that the I/O port address can be software configured (of course there must
be a way somehow to do that when the I/O device is first installed).
- Next message: Gary Kato: "Re: Clarification on IO Operations"
- Previous message: guruteck_at_gmail.com: "Re: Clarification on IO Operations"
- In reply to: guruteck_at_gmail.com: "Re: Clarification on IO Operations"
- Next in thread: Nick Andrew: "Re: Clarification on IO Operations"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|