From: Jon Smirl <jonsmirl@gmail.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: "David S. Miller" <davem@davemloft.net>,
willy@debian.org, linux-kernel@vger.kernel.org
Subject: Re: multi-domain PCI and sysfs
Date: Wed, 8 Sep 2004 02:55:15 -0400 [thread overview]
Message-ID: <9e47339104090723554eb021e4@mail.gmail.com> (raw)
In-Reply-To: <200409072125.41153.jbarnes@engr.sgi.com>
Another part I don't understand... PCI VGA hardware is designed to
respond to IN/OUT instructions to port space. ppc64/ia64 don't have
IN/OUT port instructions. Is there some special hardware on ppc64/ia64
that declares part of the PCI IO space "legacy space" and turns
read/writes there into IN/OUT port cycles on the PCI bus so that the
legacy hardware can see the accesses?
On machines without this "legacy space" translation hardware (ie all
32b x86 bit machines) I can only have a single VGA adapter active
since there is only a single legacy space and inb/outb are real
instructions.
On machines with "legacy space" translation I can have one active VGA
card per translator. How do I know how many translators there are? Is
only one per domain/segment allowed?
How does ppc32 handle VGA port instructions, is the "legacy
translation" space at the bottom of the PCI address space?
I looked at io.h on IA64, how do apps select which legacy IO space
they are using? Now I see add_io_space() and related code.
Maybe it's not a good idea to have a 32b x86 person writing this
driver. Is there a cross platform structure that corresponds to IO
spaces?
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-08 6:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 20:00 multi-domain PCI and sysfs Jon Smirl
2004-09-04 21:57 ` Jesse Barnes
2004-09-04 22:12 ` Jon Smirl
2004-09-04 22:27 ` Jesse Barnes
2004-09-04 22:45 ` Jon Smirl
2004-09-04 23:03 ` Jesse Barnes
2004-09-05 23:04 ` Matthew Wilcox
2004-09-05 23:50 ` Jon Smirl
2004-09-05 23:00 ` Alan Cox
2004-09-06 1:40 ` Matthew Wilcox
2004-09-07 22:58 ` Jon Smirl
2004-09-07 23:11 ` David S. Miller
2004-09-08 3:39 ` Jon Smirl
2004-09-08 4:12 ` David S. Miller
2004-09-08 4:16 ` Jesse Barnes
2004-09-08 4:15 ` Jesse Barnes
2004-09-08 4:16 ` David S. Miller
2004-09-08 4:25 ` Jesse Barnes
2004-09-08 6:01 ` Jon Smirl
2004-09-08 13:02 ` Alan Cox
2004-09-08 16:02 ` Jesse Barnes
2004-09-08 18:20 ` David S. Miller
2004-09-08 18:32 ` Jesse Barnes
2004-09-08 18:54 ` David S. Miller
2004-09-08 6:55 ` Jon Smirl [this message]
2004-09-08 11:11 ` Geert Uytterhoeven
2004-09-08 11:38 ` Matthew Wilcox
2004-09-08 18:21 ` David S. Miller
2004-09-08 22:41 ` Alan Cox
2004-09-09 0:31 ` Jon Smirl
2004-09-09 13:06 ` Alan Cox
2004-09-08 15:03 ` Matthew Wilcox
2004-09-06 0:06 ` Jesse Barnes
2004-09-06 0:31 ` Jon Smirl
2004-09-06 1:38 ` Jon Smirl
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=9e47339104090723554eb021e4@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=davem@davemloft.net \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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 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.