public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Michael Schmitz <schmitzmic@googlemail.com>, linux-m68k@vger.kernel.org
Subject: Re: Atari ROM port ISA
Date: Sun, 22 Apr 2012 03:44:10 +1200	[thread overview]
Message-ID: <4F92D5CA.1000205@gmail.com> (raw)
In-Reply-To: <Pine.BSM.4.64L.1204192041320.27380@herc.mirbsd.org>

Hi Thorsten,
>> Thanks for explaining this to me - to be honest I've never cared too
>> much about ISA and friends.
> No problem. (I practically grew up with them, so while the knowledge
> isn’t fresh, some is there.)
I grew up without computers - the first I used was a TR440 mainframe :-)
>> I'll check the layout - my guess would be that there's no memory
>> read/write selects wired up on the adapter. The RTL8019 doesn't need
>> them, the ISP1160  on the NetUSBee doesn't need them either.
> I’d guess the same. You’d need them for things like an ISA graphics
> card, but not (most) I/O devices.
Only /IOW and /IOR are wired up. Only A0 through A4 are wired up (from 
A9-A13).
>> If someone ever comes up with a way to hook up a fully featured ISA
>> slot to the ROM port (mapping ports 0x00 to 0x7f to IO and above to
>> mem access should be possible) we might revisit the code. For now,
>> anything except for 8 bit IO can be turned into dummy functions or
>> compile warnings.
> Might be nice, if possible. But for now, that would indeed be
> the way to go (and clean up code).
I've had a look at the NetUSBee docs and see that the USB part of it 
does require 8 bit writes but little endian 16 bit reads. So we will 
need to retain the 16 bit reads for potential USB support there.

Cheers,

   Michael

  reply	other threads:[~2012-04-21  7:49 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
2012-04-19 20:38       ` Michael Schmitz
2012-04-19 20:43         ` Thorsten Glaser
2012-04-21 15:44           ` Michael Schmitz [this message]
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=4F92D5CA.1000205@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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