> If a conflict can't be avoided, we could fail gracefully upfront > (suggesting to make the GART aperture smaller, ...) instead of risking > subtle breakage?
Well, I don't know of any clean platform independant way to know if there is a conflict or not, that is to know where RAM is in bus space. Especially from the PCI view, it can be anywhere. In some cases, you have to go through an iommu, that on most ppc64 machines (and I suppose sparc64 and x86_64). So the space you are looking for "preserving" is the iommu virtual space, which may even be different than the real ram space. Something that would probably work as good we can for now is to assume RAM at 0, check for overlap above framebuffer and eventually move the GART below the fb if it does, though ... maybe Michel is right and just ask the user to reduce the GART when it doesn't fit above the fb ? I hope firmwares will usually be smart enough to map the fb not at the top of the address space... Ben. ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
