Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux kernel <linux-kernel@vger.rutgers.edu>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
	Linux/MIPS Development <linux@cthulhu.engr.sgi.com>
Subject: Re: Proposal: non-PC ISA bus support
Date: Wed, 21 Jun 2000 16:57:44 -0700	[thread overview]
Message-ID: <20000621165744.C28857@twiddle.net> (raw)
In-Reply-To: <Pine.GSO.4.10.10006201254290.8592-100000@dandelion.sonytel.be>

On Tue, Jun 20, 2000 at 01:21:10PM +0200, Geert Uytterhoeven wrote:
>1. ISA I/O space is memory mapped on many platforms (e.g. PPC and MIPS). To
>   access it from user space, you cannot plainly use inb() and friends like on
>   PC, but you have to mmap() the correct region of /dev/mem first. This
>   region depends on the machine type and currently there's no simple way to
>   find out from user space.

You may wish to examine the pciconfig_iobase syscall used on Alpha.
It can be used to solve the multiple independant pci bus problem
as well as the ISA base address problem.

>2. ISA memory is not located at physical address 0 on many platforms (e.g. PPC
>   and some MIPS boxes). This means you cannot e.g. use
>   request_mem_region(0xa0000, 65536) to request the legacy VGA region.

This can be fiddled.  Basicly, you pretend that 0 is the base address,
then use ioremap to shift everything up into place.  This assumes that
the ISA bus is contained within exactly one PCI hose.


r~

  parent reply	other threads:[~2000-06-22  0:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-20 11:21 Proposal: non-PC ISA bus support Geert Uytterhoeven
2000-06-20 12:23 ` Benjamin Herrenschmidt
2000-06-20 12:41   ` Geert Uytterhoeven
2000-06-20 13:02     ` Benjamin Herrenschmidt
2000-06-20 13:09       ` Geert Uytterhoeven
2000-06-20 13:25   ` De Schrijver Peter
2000-06-20 13:30     ` Benjamin Herrenschmidt
2000-06-21 21:47   ` Michel Lanners
2000-06-20 17:11 ` Frank Rowand
2000-06-20 17:29   ` Geert Uytterhoeven
2000-06-20 20:10 ` Russell King
2000-06-20 20:10   ` Russell King
2000-06-21 23:57 ` Richard Henderson [this message]
2000-06-22  6:45   ` Geert Uytterhoeven
2000-06-22  7:19     ` Richard Henderson
2000-06-22  7:41       ` Geert Uytterhoeven
2000-06-22  8:59         ` Richard Henderson
2000-06-22  9:15           ` Geert Uytterhoeven

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=20000621165744.C28857@twiddle.net \
    --to=rth@twiddle.net \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=linuxppc-dev@lists.linuxppc.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