linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Richard Smith <rsmith@bitworks.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Telling libSDL that my fbdev can do acclerated fills
Date: Wed, 30 Jun 2004 12:38:06 +0800	[thread overview]
Message-ID: <200406301238.06406.adaplas@hotpop.com> (raw)
In-Reply-To: <40E239F8.7070909@bitworks.com>

On Wednesday 30 June 2004 11:56, Richard Smith wrote:
> I'm working on a app that runs on the STPC Atlas and uses libSDL with
> the stpcfb from STPC.  Kernel 2.4.x. I'm currently using 2.4.23 but any
> of later kernels will work.
>
> The Atlas video accelerator supports hardware assisted fills.  I've been
> looking over the stpcfb code and some of the other framebuffer drivers
> and its not obvious to me how the fb system exports out what kind of
> graphics hardware assisted abilities it has.  Or even how you would call
> those abilities if you knew they were avaiable.
>
> All I see is stuff for text related console work.
>
> The STPC is a pretty slow device and my app needs all the speed help it
> can get. libSDL is currently doing software fills since it dosen't know
> otherwise.
>
> I see in the libSDL source code that the FillHWRect funciton pointer for
> the fb driver is set to NULL as if its not possible to realize hardware
> assisted graphics functions via fbdev.
>
> Is this the case or what am I missing?
>

All hardware-assisted drawing functions in fbdev are for use by the console
only.  You might want to try DirectFB (www.directfb.org), I believe they have
ported a lot of libs, including SDL.  However, I doubt they have a gfxdriver for
your hardware though.

Tony




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-06-30  4:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30  2:47 [PATCH][FBCON]: Mode Switch in fbcon_blank() Antonino A. Daplas
2004-06-30  2:53 ` Benjamin Herrenschmidt
2004-06-30  3:56   ` Telling libSDL that my fbdev can do acclerated fills Richard Smith
2004-06-30  4:38     ` Antonino A. Daplas [this message]
2004-06-30  4:45       ` Richard Smith
2004-06-30  6:14         ` Antonino A. Daplas
2004-07-02 10:25   ` [PATCH][FBCON]: Mode Switch in fbcon_blank() Javier Marcet
2004-07-02 15:37     ` Antonino A. Daplas
2004-07-03  0:43       ` Javier Marcet
2004-07-04  0:05       ` [PATCH] radeonfb: mode switch work around David Eger
2004-07-04  0:46         ` David Eger
2004-07-04  1:00           ` Antonino A. Daplas
2004-07-04  2:13             ` David Eger
2004-07-04  2:59               ` Jon Smirl
2004-07-04  8:35                 ` Geert Uytterhoeven
2004-07-04  9:35                   ` David Eger
2004-07-04 15:47     ` Re: [PATCH][FBCON]: Mode Switch in fbcon_blank() Antonino A. Daplas
2004-07-04 19:32       ` David Eger
2004-07-04 22:35         ` Antonino A. Daplas

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=200406301238.06406.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rsmith@bitworks.com \
    /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).