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:01:39 -0400 [thread overview]
Message-ID: <9e47339104090723012190c73a@mail.gmail.com> (raw)
In-Reply-To: <200409072125.41153.jbarnes@engr.sgi.com>
On Tue, 7 Sep 2004 21:25:41 -0700, Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> you're up for it. My hope is that we can have a unified Linux device access
> method in X and get rid of all (or at least most) of the ppc/sparc/ia64/etc.
> specific hacks in the tree...
X on GL is going to eliminate all device access from X. Everything
will be handled from the OpenGL layer. When everything is finished
even the OpenGL layer won't do hardware access either, it will IOCTL
the DRM driver to do it. In the final solution the only user of the
VGA control should be the secondary card reset program.
Where is the PCI segment base address stored in the PCI driver
structures? I'm still having trouble with the fact that the PCI driver
does not have a clear structure representing a PCI segment. Shouldn't
there be a structure corresponding to a segment?
>From what I understand right now the SN2 machine can not have two
active VGA cards since it does not have two PCI segments. Without two
segments there is no way to tell the legacy addresses apart.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-09-08 6:01 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 [this message]
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
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=9e47339104090723012190c73a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox