From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Jim Paris <jim@jtan.com>, linux-mips@oss.sgi.com
Subject: Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA]
Date: Tue, 18 Dec 2001 11:36:50 -0800 [thread overview]
Message-ID: <3C1F9AD2.1269192E@mvista.com> (raw)
In-Reply-To: 20011218173118.C28080@dea.linux-mips.net
Ralf Baechle wrote:
>
> On Tue, Dec 18, 2001 at 11:16:24AM -0800, Jun Sun wrote:
>
> > I see. So isa_slot_offset is for isa_read/isa_write, although I still don't
> > see what kind of drivers would use isa_read/isa_write.
>
> Dumb answer - ISA drivers.
>
(Hmm, do you mean "dumb question"? :-0)
I was thinking most ISA dirvers should simply use inb/outb to access ioports.
Don't really any ISA devices have their own memory space. But, anyway, who
can still remember those dark ages?
Jun
next prev parent reply other threads:[~2001-12-18 20:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 20:15 [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA] Jim Paris
2001-12-17 21:34 ` Ralf Baechle
2001-12-18 5:45 ` Jim Paris
2001-12-18 7:03 ` Jim Paris
2001-12-18 4:03 ` hanishkvc
2001-12-18 18:10 ` Jun Sun
2001-12-18 18:45 ` Jim Paris
2001-12-18 18:45 ` Jim Paris
2001-12-18 19:09 ` Jun Sun
2001-12-18 19:30 ` Ralf Baechle
2001-12-19 9:40 ` Geert Uytterhoeven
2001-12-18 18:25 ` Ralf Baechle
2001-12-18 18:57 ` Jim Paris
2001-12-18 19:21 ` Jun Sun
2001-12-18 20:58 ` Ralf Baechle
2001-12-18 21:28 ` Jim Paris
2001-12-18 21:53 ` Maciej W. Rozycki
2001-12-19 9:34 ` Geert Uytterhoeven
2001-12-22 12:47 ` Ralf Baechle
2001-12-18 19:16 ` Jun Sun
2001-12-18 19:31 ` Ralf Baechle
2001-12-18 19:36 ` Jun Sun [this message]
2001-12-18 20:02 ` Karsten Merker
2001-12-18 20:22 ` Maciej W. Rozycki
2001-12-18 22:28 ` Ralf Baechle
2001-12-19 9:34 ` Geert Uytterhoeven
2001-12-19 16:47 ` Ralf Baechle
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=3C1F9AD2.1269192E@mvista.com \
--to=jsun@mvista.com \
--cc=jim@jtan.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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