Dualhead... Right now there is dualhead support for the following cards in xfree86: radeon matrox sis via chips 3dlabs (Sven mentioned that he had this quasi-working on the newer cards, although I don't know the state of his driver)
The following cards have hw dualhead support, but no driver support for it: i830/845 mach64 rage128 savage trident smi I don't suppose there is much interest in adding dualhead support for these cards. Is there anything in the pipeline? I've studied the other dualhead drivers pretty extensively, and I think I could provide a generic dualhead capable skeleton driver and a howto document. Would anyone find this to be a benefit? perhaps to be included in xfree for future driver writers? Are databooks for any of these cards readily available anywhere? I might be willing to try my hand at this again if I could get databooks. Next, mergedfb... I've been thinking about creating generic xfree support functions to replace the chipset specific ones for mergedfb. This would make it easier to add mergedfb to other chipsets that support dualhead. Where should this live? also, as far as pseudo-xinerama, should that be made part of the generic mergedfb code or part of xinerama proper? i.e., to extend xinerama to handle both multi-card and single card xinerama. Or is all of this going to be refactored in xfree 5? multihead and DRI... There's been some recent work in the DRI tree to track GLX extension state per screen (http://marc.theaimsgroup.com/?l=dri-patches&m=106123210307564&w=2). What other things need to happen to get the DRI working on multiple graphics cards? On a related note, I've been thinking about alternative ways to implement mergedfb on radeon hardware. what if instead of creating a single framebuffer with two viewports, we stuck with the old style pScrn based multi-head code, but made each head a client of the DRI? the 3D engine would be shared by each head. This seems to be the way the 2D engine works in pScrn based multi-head now. I can see this working ok for independant heads, but what about when using xinerama? what would need to be done in that case? perhaps glxproxy from dmx (dmx.sf.net) would be of use in this case. would doing this potentially get around the issues with the scissor registers limiting us to 2048x2048 for 3D? I could see potential issues with 3D windows that spanned heads since they would be trading access to the hardware back and forth. Thanks, Alex __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
