Marc Aurele La France wrote:


if ((pATI->Adapter != ATI_ADAPTER_VGA) &&
((pATI->Adapter != ATI_ADAPTER_8514A) ||
((pATI->VGAAdapter != ATI_ADAPTER_VGA) &&
(pATI->VGAAdapter != ATI_ADAPTER_NONE))))





Changing the second line to test pATI->ChipHasSUBSYS_CNTL will treat mach8
and mach32 as 8514 devices here.



Yes, but I don't want it to do that. While you are correct in saying I don't currently support VGA-less adapters, I'd prefer to keep that decision in ATIPreInit().



That works for me as long as there's no separate 8514 driver as there was in 3.x.

The third and fourth lines test if the
VGA is disabled.



It does more than that. This statement appears at a point where
ATIProbe() has already collected all adapters it is interested in
(including non-ATI VGA and/or 8514 clones), _and_ there is no XF86Config
available. The intent of this statement is to prevent the driver from
generating device sections for non-ATI adapters. This is independent of
whether or not the adapter(s) actually provide(s) VGA.


Good point. There's much more to the ativga vs vga decision than I can see with a vga-disabled gup.

On a separate front, I don't want you to think that your work on ISA
multihead is falling on deaf ears, as I am keenly interested in it.  It is
just that I currently don't have time to properly (re-)delve into it.

I do however wish to be supportive and, towards that end, I'm attaching a
hercules driver I wrote back in 1998, which I never integrated (no
appropriate hardware).  This pre-dates RAC and the xf86Match???Instances()
scheme that so greatly complicated ISA multihead and ended up entrenching
PCI's "supremacy" into the server.  While I doubt this driver was
functional even back then, my main purpose with it was to demonstrate how
to use mibank to deal with HGA's oddball addressing of video memory.



I'll take a look. I have a fully functional xf86Match???Instances() compliant one I wrote against 4.2. about 18
months ago. 4.3 was already out and I was bandwidth limited and not able/willing to get current, so nothing happened
with it.
As the ati driver is the only one to call AddDeviceToConfigure() directly rather than going through the Match???Instances()
routines, I was hoping you were watching. I'm still sorting through sparse resource implications and getting the ati
resource maps right. All three of my ati cards (VGA Wonder, GUP, mach64) stomp all over the hercules and the
GUP and mach64 lock up when adaptec scsi controllers are present (which my thin client has). I'll have a refined
set of proposed changes in the next few days.
Enjoy
Lee


_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to