From: Otto Solares <solca@guug.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: I want to use fb device for my 3D game. Can it do what I need?
Date: Fri, 9 Jan 2004 16:34:21 -0600 [thread overview]
Message-ID: <20040109223421.GC20620@guug.org> (raw)
In-Reply-To: <200401092200.10820.andrew@walrond.org>
On Fri, Jan 09, 2004 at 10:00:10PM +0000, Andrew Walrond wrote:
> Hello list!
>
> I have developed a software library for rendering 3D scenes.
Hmm.. cool! how you construct the 3D scenes?
> It would be very cool if I could use the fb device so that X needn't be
> running, freeing considerable resources for the application
> Note that it is a _software_ renderer, I don't need access to 3D hardware
> acceleration, just a means of copying/bliting frames to the screen as fast as
> possible, and a double buffering facility
>
> So what I need is an api allowing me to
>
> - Set the screen resolution/colour depth. (16bit colour depth or better is
> required)
Already part of fbdev.
> - Allocate front and back buffers
>
> - Copy scene to back buffer
>
> - Swap buffers synced with vertical refresh
>
> Does fbdev have the facilities I need?
You would probably want to look at SDL's fbdev backend.
-solca
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-09 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 22:00 I want to use fb device for my 3D game. Can it do what I need? Andrew Walrond
2004-01-09 22:34 ` Otto Solares [this message]
2004-01-10 0:03 ` Andrew Walrond
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=20040109223421.GC20620@guug.org \
--to=solca@guug.org \
--cc=andrew@walrond.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.