From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Zack <plinius@comcast.net>
Subject: Re: fbdraw 0.1 available
Date: Sun, 12 Sep 2004 03:40:03 +0800 [thread overview]
Message-ID: <200409120340.04133.adaplas@hotpop.com> (raw)
In-Reply-To: <41426651.2010201@comcast.net>
On Saturday 11 September 2004 10:43, Zack wrote:
> My changes to permit (optional) in-kernel drawing for applications
> are available. It's only version 0.1 at this point, meaning alpha,
> but I'm happy with the performance and structure. I've included
> a test application that allows benchmarking.
>
> home.comcast.net/~plinius/fbdraw-0.1.tar.gz
>
> To install, move the tarfile to the 2.6.8.1 root dir, and use
> tar zxfv fbdraw-0.1.tar.gz.
>
> Constructive criticism is welcome.
(Better if you provided an inlined file so it's easier to make comments)
Here's a few, just from a quick scan:
1. First, you need to follow Documentation/CodingStyle.
2. Do not directly access framebuffer memory, use:
fb_{read|write}{b|w|l}
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).
Tony
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-09-11 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 2:43 fbdraw 0.1 available Zack
2004-09-11 10:53 ` Geert Uytterhoeven
2004-09-11 18:09 ` Zack
2004-09-11 19:40 ` Antonino A. Daplas [this message]
2004-09-13 0:31 ` Zack
2004-09-13 11:18 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409120340.04133.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=plinius@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).