public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: linux-m68k@vger.kernel.org
Subject: Re: Atari ROM port ISA
Date: Thu, 19 Apr 2012 15:00:51 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120419T165359-796@post.gmane.org> (raw)
In-Reply-To: 20120417050500.GA14387@cynthia.pants.nu

Brad Boyer <flar <at> allandria.com> writes:

> On Mon, Apr 16, 2012 at 07:50:33PM +1200, Michael Schmitz wrote:

> > >So ISA memory space accesses (isa_readX()) are implemented the same as ISA 
I/O
> > >space accesses? That can't work. Or are they not supported?
> > 
> > There's no distinct 'IO' or 'memory' space on the ROM port adapter,
> > it's all memory mapped on ROM port addresses. How does access to ISA
> > card mem regions work on ix86? Different address range, or different
> > instructions?
> 
> The real x86 instruction set has separate instructions to access any
> ports in the IO space (in and out). The instruction also has an access

This maps to different lines being driven on the ISA side, see:
https://upload.wikimedia.org/wikipedia/commons/3/3d/XT_Bus_pins.png

There are I/O read/write and MEM read/write lines (B11‥B14).
So you need these that are actually wired up in the adapter.

Bascially, “PC” I/O ports have a separate 16-bit¹ address space
from the main (originally) 20-bit address space of the main
memory (RAM, ROM) which are addressed with different instructions
and may behave different when accessed as 8-bit vs. 16-bit slots.

① IIRC, only 12 bit were originally wired or used before the era
  of the various Local Buses, although according to the 8086 docs
  that seems to not have been a CPU issue but mainboard design.

bye,
//mirabilos

  reply	other threads:[~2012-04-19 15:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  9:34 Atari ROM port ISA Geert Uytterhoeven
2012-04-16  7:50 ` Michael Schmitz
2012-04-16  9:09   ` Andreas Schwab
2012-04-16  9:42   ` Geert Uytterhoeven
2012-04-16 20:21     ` Michael Schmitz
2012-04-17  5:05   ` Brad Boyer
2012-04-19 15:00     ` Thorsten Glaser [this message]
2012-04-19 20:38       ` Michael Schmitz
2012-04-19 20:43         ` Thorsten Glaser
2012-04-21 15:44           ` Michael Schmitz
2012-04-21  8:20             ` Geert Uytterhoeven
2012-04-21 19:39               ` Geert Uytterhoeven
2012-04-22 10:36                 ` Michael Schmitz
2012-05-13 10:33                   ` David Gálvez
2012-05-13 23:27                     ` Michael Schmitz
2012-05-14 11:17                       ` David Gálvez
2012-05-17  6:10                       ` David Gálvez
2012-05-17  6:51                         ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20120419T165359-796@post.gmane.org \
    --to=tg@mirbsd.de \
    --cc=linux-m68k@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox