On Sun, Mar 28, 2004 at 05:14:39PM -0800, Lee Olsen wrote:That is exactly the misunderstanding I suffer from. If X -configure creates a config file, I expect it to work
Hello all;
The vesa driver probe/FindIsaDevice is doing a vga probe, not a vesa one.
It should be calling a vbe routine to check for a vesa signature.
The Probe() function should not change the hardware state and should be as non-intrusive as possible. When Probe() reports success, it does not mean that the driver's PreInit() will succeed. The vesa driver is not especially unusual in this respect. Why do you need to change this?
with the hardware just configured. If Probe succeeds and PreInit fails, then the configuration isn't valid. When
it's something like the ati driver configuring a screen for a VGA-less 8514 and failing in PreInit, that's not a big
deal because it's very likely there's a VGA head supported by another driver. I figured a single-headed configuration
shouldn't do this. With the trailing-edge cards I'm testing for vga/mono conflicts generally using the vesa driver, I
wanted to eliminate the "No screens found" distraction. Fortunately it's a "want" rather than a "need", and based
on Egbert's comments, a bigger can of worms than I want to deal with right now.
Since X -configure won't generate a vga device entry, Egbert's ideas about doing vga stuff in the vesa driver
might be the right long term solution. At least it brings Probe and PreInit back in sync.
Enjoy
Lee
_______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
