[lkml]   [2005]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Fwd: Patch to control VGA bus routing and active VGA device.
On Friday, January 28, 2005 11:33 am, Grant Grundler wrote:
> > But
> > if you mean being able to access legacy ports at all, then no. On SGI
> > machines, there's a per-bus base address that can be used as the base for
> > port I/O, which is what I was getting at.
> Ok - my point was "0x3fc" will get routed to exactly one of those
> IO port address spaces.

Agreed, or it will cause a machine check if legacy I/O remapping isn't
supported (like on SGI).

> > There is no resource for some of the I/O port space that cards respond
> > to.
> Yes - I've heard several graphics cards are horrible broken WRT address
> decoding. Are PCI quirks supposed to handle that sort of thing?

I'm not sure if broken is the right work. All this stuff predates PCI by
quite a bit, so certain device classes claimed certain port ranges way before
cards were required to have programmable address decoders. VGA cards are
probably the most tenacious example of this, they respond to certain well
known ports after reset, regardless of BAR values.

> > I can set the I/O BAR of my VGA card to 0x400 and it'll still respond to
> > accesses at 0x3bc for example. That's what I mean by legacy space--space
> > that cards respond to but don't report in their PCI resources.
> Can't PCI quirks fix up the resources to reflect this?

Not sure, the I/O BAR may correspond to real registers too--and they may not
overlap with the ones in the well known space.

> I think one needs to fix up PCI IO Port resources to adjust
> for "The One" legacy IO port space getting routed to a different
> PCI segment - assuming no one submits a patch to change current
> behavior of using hard coded addresses.

I think we might just need a new resource for these well known ports, if my
last statement is true.

> Am I making more sense now?

Yeah, I think I understand. We could probably do the same thing on sn2 as you
do on parisc--add a 'segment 0' offset to the port so that it's routed
correctly. I think that's a little less flexible than adding a new resource
though, since it makes it harder for drivers to support more than one device
or devices on non-segment 0 busses.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:09    [W:0.101 / U:3.576 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site