From: Ralf Baechle <ralf@oss.sgi.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: set_io_port_base()?
Date: Thu, 21 Feb 2002 02:57:55 +0100 [thread overview]
Message-ID: <20020221025755.B29466@dea.linux-mips.net> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIOEKBCFAA.mdharm@momenco.com>; from mdharm@momenco.com on Wed, Feb 20, 2002 at 05:36:05PM -0800
On Wed, Feb 20, 2002 at 05:36:05PM -0800, Matthew Dharm wrote:
> Now, I'm pretty sure this has something to do with the initcall to
> set_io_port_base() and ioremap(), which are in my setup.c (copied from
> linux/arch/mips/gt64120/momenco_ocelot/setup.c and modified). Without
> that bit of code at the bottom of that function, I don't even get
> this -- it just crashes. So I know I need this code, but I'm just not
> certain what/how I should be using it...
>
> My initial guess is that it's used to map some virtual address space
> onto the physical addresses needed to actually generate PCI I/O
> transactions, but that's just a guess. If that's right, then the code
> I'm using _should_ work... I call ioremap() with the physical base and
> size, and then set_io_port_base() using the result of ioremap().
That is exactly the intended use.
Ralf
next prev parent reply other threads:[~2002-02-21 2:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 1:36 set_io_port_base()? Matthew Dharm
2002-02-21 1:57 ` Ralf Baechle [this message]
2002-02-21 2:05 ` set_io_port_base()? Matthew Dharm
2002-02-21 2:13 ` set_io_port_base()? Ralf Baechle
2002-02-21 2:27 ` set_io_port_base()? Jun Sun
2002-02-21 2:48 ` set_io_port_base()? Matthew Dharm
2002-02-21 2:48 ` set_io_port_base()? Matthew Dharm
2002-02-21 3:03 ` set_io_port_base()? Jason Gunthorpe
2002-02-21 5:35 ` set_io_port_base()? Jun Sun
2002-02-21 3:30 ` set_io_port_base()? Ralf Baechle
2002-02-21 16:34 ` pthread support in mipsel-linux Wayne Gowcher
2002-02-21 17:55 ` H . J . Lu
2002-02-21 18:12 ` Wayne Gowcher
2002-02-21 18:25 ` H . J . Lu
2002-02-21 18:45 ` Wayne Gowcher
2002-02-22 8:52 ` Florian Lohoff
2002-02-22 13:38 ` Maciej W. Rozycki
2002-02-22 13:45 ` Hiroyuki Machida
2002-02-22 14:28 ` Maciej W. Rozycki
2002-02-22 16:53 ` H . J . Lu
2002-02-22 16:57 ` H . J . Lu
2002-02-22 17:06 ` Maciej W. Rozycki
2002-02-22 17:14 ` H . J . Lu
2002-04-19 17:06 ` Equivalent of ioperm / iopl in linux mips ? Wayne Gowcher
2002-04-20 9:03 ` Geert Uytterhoeven
2002-04-22 11:35 ` Maciej W. Rozycki
2002-04-22 14:55 ` Geert Uytterhoeven
2002-04-22 15:30 ` Maciej W. Rozycki
2002-04-22 15:33 ` Geert Uytterhoeven
2002-04-22 17:44 ` Ralf Baechle
2002-04-22 18:01 ` Maciej W. Rozycki
2002-02-21 2:08 ` set_io_port_base()? Matthew Dharm
2002-02-21 2:16 ` set_io_port_base()? 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=20020221025755.B29466@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.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