Proper way to enable port access tracing with current xserver

[Tiago Vignatti]

Alex Villací­s Lasso escreveu:
>  From what I glean from the traces, it seems that using VESA to start up 
> the primary Savage chipset works correctly. However, when trying to 
> initialize the Oak chipset as secondary (just that one, without 
> reference to the primary Savage chipset), it ends up in a loop of 
> in(3da) = ff and hangs. Interestingly, I saw no hint that the Savage 
> chipset was ever moved out of the legacy  VGA mapping in order to 
> initialize the Oak chipset via POST. Which ties back to my previous 
> question: what measures (if any) are supposed to be taken by the xserver 
> in order to hand over the legacy VGA ports to a secondary chipset that 
> needs access to them for POST, when run with a different chipset as 
> primary? As in, Savage is mapped to legacy VGA, I want to POST the Oak 
> chipset, which needs a mapping to the VGA ports too, so what should the 
> xserver do?

yeah, this is pretty much the task of the vga arbiter. See my next email...

-- 
Tiago Vignatti
C3SL - Centro de Computação Científica e Software Livre
www.c3sl.ufpr.br