Re: fbdraw 0.1 available

On Sun, 12 Sep 2004, Zack wrote:

quoted

2. Do not directly access framebuffer memory, use:
3. Do not use copy_{to|from}_user when the destination/source is the
framebuffer.
4. Do not memset the framebuffer.  You can probably create an equivalent
function using fb_read/write.  (Once, we have fb_memset and fb_memcpy, but
they're gone in 2.6).

Fixed.

Incidentally I am wondering, with cross-platform compatibility
in mind I have been coding assuming that fb_{read|write}[wl] must be
short/long aligned. Is that assumption correct?

Yes, that's the safest.

I've also added my copyarea routine. At first I tried to make use
of cfb_copyarea but it proved very buggy in 24bpp.

What about fixing the bugs in the existing code, instead of adding a new
routine that does the same? ;-)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


-------------------------------------------------------
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