From: Dan Malek <dan@mvista.com>
To: Rob Taylor <robt@flyingpig.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: switching linux kernels
Date: Wed, 27 Sep 2000 12:03:45 -0400 [thread overview]
Message-ID: <39D21A61.445CC61F@mvista.com> (raw)
In-Reply-To: 001801c02865$c71c1c10$b400a8c0@eventhorizon
Rob Taylor wrote:
> presumably this is due to int in/out macros adding _IO_BASE to the pointer?
Yes.
> ... So
> am I right in thinking that it makes sense to use in/out for ISA accesses (if
> _IO_BASE is set correctly for your platform) and readb/writeb/.. for the rest of
> your memory mapped registers?
Well, yes, today. Some of us have been "fighting" about this lately.
I'm not a fan of address arithmetic in the inb/outb, so probably on
8xx and 82xx you will always have some "opaque" handle to in/out that
doesn't resemble any notion of x86 "ports". The reason is that on
these 8xx and 82xx systems (and potentially others) we don't have very
flexible host bridges, or the processors are used in complex multiple
PCI bus configurations where the notion of "bus 0" may not exist. You
can't assume using a hard coded (or legacy) port number will get you
anywhere but a bus fault.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-27 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 22:34 switching linux kernels Julia Elbert
2000-09-27 0:40 ` Graham Stoney
2000-09-27 5:59 ` Dan Malek
2000-09-27 6:41 ` Graham Stoney
2000-09-27 9:31 ` Rob Taylor
2000-09-27 16:03 ` Dan Malek [this message]
2000-10-06 16:50 ` Rob Taylor
-- strict thread matches above, loose matches on Subject: below --
2000-09-26 18:24 Julia Elbert
2000-09-26 16:59 Julia Elbert
2000-09-26 0:02 Julia Elbert
2000-09-26 0:25 ` Graham Stoney
2000-09-26 15:54 ` Dan Malek
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=39D21A61.445CC61F@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=robt@flyingpig.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.