From: Torgeir Veimo <torgeir@pobox.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Plans for 2D acceleration
Date: Wed, 26 Sep 2007 12:45:27 +0100 [thread overview]
Message-ID: <1190807127.27064.2.camel@tveimo-laptop> (raw)
In-Reply-To: <46FA4579.6040905@freemail.gr>
On Wed, 2007-09-26 at 04:41 -0700, Jerald Fitzjerald wrote:
>
>
> Are there any plans to expose simple 2D acceleration to userland?
> I'm talking about the very basic operations:
>
> - fill rectangle (graphics memset)
> - blit (graphics memcpy)
>
> and possibly
>
> - copyarea (graphics memmove)
> - waitretrace
>
> Is there a reason we _don't_ want these exposed to userland or
> just nobody has taken the time to do it?
You can do all of these using DirectFB. Is that not an option for you?
--
-Tor
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-26 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 11:41 Plans for 2D acceleration Jerald Fitzjerald
2007-09-26 11:45 ` Torgeir Veimo [this message]
2007-09-26 14:29 ` Jerald Fitzjerald
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=1190807127.27064.2.camel@tveimo-laptop \
--to=torgeir@pobox.com \
--cc=linux-fbdev-devel@lists.sourceforge.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