From: Adam Belay <abelay@novell.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [RFC] PCI bridge driver rewrite
Date: Thu, 24 Feb 2005 02:03:58 -0500 [thread overview]
Message-ID: <1109228638.28403.71.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050223224532239c9d@mail.gmail.com>
On Thu, 2005-02-24 at 01:45 -0500, Jon Smirl wrote:
> On Thu, 24 Feb 2005 01:22:01 -0500, Adam Belay <abelay@novell.com> wrote:
> > For the past couple weeks I have been reorganizing the PCI subsystem to
> > better utilize the driver model. Specifically, the bus detection code
> > is now using a standard PCI driver. It turns out to be a major
>
> What about VGA routing? Most PCI buses do it with the normal VGA bit
> but big hardware supports multiple legacy IO spaces via the bridge
> chips.
>
> Are you going to make sysfs entries for the bridges? If so I'd like a
> VGA attribute that directly reads the VGA bit from the hardware and
> display it instead of using the shadow copy.
Yeah, actually I've been thinking about this issue a lot. I think it
would make a lot of sense to export this sort of thing under the
"pci_bus" class in sysfs. The ISA enable bit should probably also be
exported. Furthermore, we should be verifying the BIOS's configuration
of VGA and ISA. I'll try to integrate this in my future releases. I
appreciate the code.
I also have a number of resource management plans for the VGA enable bit
that I'll get into in my next set of patches.
>
> Jesse can comment on the specific support needed for multiple legacy IO spaces.
>
That would be great. Most of my experience has been with only a couple
legacy IO port ranges passing through the bridge.
Thanks,
Adam
next prev parent reply other threads:[~2005-02-24 7:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 6:22 [RFC] PCI bridge driver rewrite Adam Belay
2005-02-24 6:45 ` Jon Smirl
2005-02-24 7:03 ` Adam Belay [this message]
2005-02-24 7:25 ` Jon Smirl
2005-02-28 23:39 ` Adam Belay
2005-02-24 23:02 ` Jesse Barnes
2005-02-28 23:27 ` Adam Belay
2005-02-28 23:38 ` Jesse Barnes
2005-03-01 0:13 ` Adam Belay
2005-03-01 0:34 ` Jesse Barnes
2005-02-24 10:03 ` Russell King
2005-02-28 23:50 ` Adam Belay
2005-02-25 23:38 ` Greg KH
2005-02-28 23:58 ` Adam Belay
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 16:33 Nguyen, Tom L
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=1109228638.28403.71.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=greg@kroah.com \
--cc=jbarnes@sgi.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.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