On Gwe, 2004-09-10 at 14:31, Felix KÃhling wrote: > The first region (frame buffer and apperture) is claimed (partially) by > vesafb, the second one (MMIO registers) is not claimed at all. I don't > see an obvious way to fix this.
Its already fixed in the stuff I'm working on. Given the list of all video devices its simply a matter of taking the mmio address and seeing who owns it. That gives you the PCI device so you now know what the VESA console is Linux pci_device terms. At that point VESA is attachable to the PCI device and so it can veto DRI attaches. I've not addressed what occurs if you get an answer in the ISA window because for VESA2 allocations I don't think it can occur. If it does then Jon's code dealing with finding the live VGA route will handle it for most boxes. (Anyone using VESA video on an IBM summit can fix it themselves). Alan ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
