Re: [Dri-devel] Ok, how to get started hacking...
On Tue, 26 Nov 2002 09:52:31 -0800 (PST) Jon Smirl <[EMAIL PROTECTED]> wrote: > Would PCI cards work right as secondary displays if > the init code in the video BIOS was executed by X when > the driver gets initialized? Or is this a more > complicated problem having to do with plug and play > OSs and resource allocation? Actually... I just tried it the other way round (PCIU VD3 as primary). it still locks (apparently in an identical manner). BUT! when the VD3 is a secondary, X /does/ emulate the BIOS code (I see the BIOS screen the VD3 normally prints). so perhaps thats not the problem anyhow. Hm. whats annoying is that both card will work in the same session - I can run two copies of X as different displays, but only one card will display at a time (I need to press alt-ctrl-f7|8 to choose which I will see. I dont think this is a card init problem. I wonder if its possible to monitor what the X windows X86 emulator is passing to these cards so we can simply init them ourselves anyway? perhaps we can trap accesses to PCI space? it'd be slow, but... --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Ok, how to get started hacking...
--- Alan Cox <[EMAIL PROTECTED]> wrote: > The Voodoo3 needs to be your primary display or it > doesnt work dual > head. My 4500 works dual head if its primary I have a similar problem when using a PCI Rage128 with any AGP card. When booting the system BIOS executes the primary video card's BIOS initialization entry point. AGP cards seem to work without running the initial video BIOS but PCI ones don't. When I use windows it doesn't matter which card is set to primary. So the vendor supplied drivers probably know how to initialize a secondary PCI card after the OS is booted or Windows is initializing them by being a PnP OS. Would PCI cards work right as secondary displays if the init code in the video BIOS was executed by X when the driver gets initialized? Or is this a more complicated problem having to do with plug and play OSs and resource allocation? = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Ok, how to get started hacking...
On Tue, 2002-11-26 at 16:59, Ian Molton wrote: > the /only/ way I have gotten things to work at all without crashing > (solid!) is to run two completely seperate X servers. this works, but > only one display will work at a time - switching between them turns the > other one off (even if it just left it on it would be better). The Voodoo3 needs to be your primary display or it doesnt work dual head. My 4500 works dual head if its primary --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Ok, how to get started hacking...
Hi. Well, I have a Voodoo3 3000 PCI now thanks to Martin Spott, and am preparing to remove the GLIDE dependencies from the driver (thats why I have the card). So, where to start? I have the card installed and working (2d), but havent quite gotten things working - you see, I have a radeon 9000 as a primary head, so the voodoo3 needs to be a secondary head. the /only/ way I have gotten things to work at all without crashing (solid!) is to run two completely seperate X servers. this works, but only one display will work at a time - switching between them turns the other one off (even if it just left it on it would be better). Ideally I'd like to do: Screen "Screen1" Screen "Screen0" RightOf "Screen1" or something, to allow both displays to work simultaneously, but this doesnt work. The VD3 always initialises (I can see the BIOS emulation) but the Radeon only sometimes seems to make it (could be any reason though). X always dies before anything else happens in either case. Any ideas? --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
