Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-)
From: James Simmons <hidden>
Date: 2004-04-21 18:14:04
Possibly related (same subject, not in this thread)
- 2004-04-30 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · James Simmons <hidden>
- 2004-04-29 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Otto Solares <hidden>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Benjamin Herrenschmidt <benh@kernel.crashing.org>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · James Simmons <hidden>
- 2004-04-21 · Re: [PATCH] radeonfb(): memmove() fix -- this one works ;-) · Benjamin Herrenschmidt <benh@kernel.crashing.org>
quoted
quoted
This is true for PCI/AGP, but may not be true for unified memory systems.Right, but that confirms my opinion that the choice of the technique used shall be under control of the driverAgreed. So a hint would be the most appropriate.
Hi Antonino. Haven't heard from you in a while. I agree. What if we add to vmode in struct fb_screeninfo. We have FB_VMODE_YWRAP 256 FB_VMODE_SMOOTH_XPAN 512 We can add more fields. Of course we have to figure out what the common case would be. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click