On Thu, Oct 30, 2003 at 11:06:45AM +0000, Alan Hourihane wrote: > On Thu, Oct 30, 2003 at 10:07:13AM +0000, Alan Hourihane wrote: > > On Thu, Oct 30, 2003 at 08:09:05AM +0000, Andrew C Aitchison wrote: > > > On Wed, 29 Oct 2003, Alan Hourihane wrote: > > > > > > > On Wed, Oct 29, 2003 at 12:26:45PM -0800, Alex Deucher wrote: > > > > > As I recall we had problems with allocating additional memory for Xv on > > > > > neomagic chips (hence the overly_mem option). As I recall there was an > > > > > issue with allocating memory beyond the limits of the blitter, similar > > > > > to the problems with Xv on via (bug 525). Could this issue be resolved > > > > > with Alan H's new linear allocator? > > > > > > > > >From looking at the driver. Yes it can. But I don't have a neomagic > > > > chipset to test. > > > > > > I have a chipset, if someone can can give me pointers to what to look at. > > > > > > I wont be able to look for a week or two, since the hard disk on the > > > laptop has died, and needs to be replaced. > > > > Well, if someone else has a chip, or wants to update and test other > > drivers (but be careful with DRI enabled drivers as it needs more work > > in the driver). Here's a patch to the neomagic that should work, and > > could be used as a template for the other drivers. > > > > That's all. Most Xv (if not all) use linear allocation already and will > > take advantage of it straight away without any furthur modifications. > > Actually, > > Due to the neomagic driver having different use of NeoFbMapSize, here's > a new followup.
Sorry, another followup for Andrew really..... The hardware cursor code should be made to use the linear allocator too, and the overlay_mem code could be removed. Alan. _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
