From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: DirectFB vs. DRI
Date: Fri, 17 Sep 2010 19:05:44 +0000 [thread overview]
Message-ID: <4C93BC08.1050001@gmx.de> (raw)
In-Reply-To: <AANLkTinsZB9RCh6SNeAL5ROYjn=GD3cQ8ijz9r8jmNGC@mail.gmail.com>
Hi,
*wonders about the subject as neither DirectFB nor DRI are topic of this mailing
list*
Perhaps you should also try:
directfb-dev@directfb.org
dri-devel@lists.freedesktop.org
But I'll try to answer your question anyway (see below)
Timur Tabi schrieb:
> Hi,
>
> I have a question about providing Linux support for a new video device
> that has 2D and 3D acceleration. I'm trying to figure out how this
> device should be supported in Linux. That is, what drivers need to be
> written? After doing a little research, it appears to me that
> DirectFB is the primary interface for hardware 2D acceleration, and
> DRI is used to provide hardware 3D acceleration for OpenGL. But then
> I see stuff about projects that seem to fix DRI with DirectFB, or use
> one of the two when the other makes more sense. For example,
> DirectFBGL. Then there's this Slashdot article from 2003 about DRI
> "coming to" DirectFB
> (http://developers.slashdot.org/article.pl?sid\x03/05/01/120254), but
> most of the links don't seem to go anywhere. And then there's also
> SDL.
>
> Anyway, the point I'm trying to make is that I can't figure out
> exactly which drivers need to be written to get my 2D/3D video
> hardware supported in Linux. Can anyone help me?
So your question is
What do you need under Linux to get your hardware working?
Well it depends on what applications you want to run and how much effort you are
spending on it.
If you are talking about a full blown desktop system where you want to run an X
server and have everything accelerated than you'll probably have to go down the
road, write an kernel drm module that supports GEM/TTM and KMS
(kernel-based-modesetting) and also the userspace parts like a X driver and
parts of mesa. That is what is currently done for Intel, AMD/ATI and Nvidia
hardware.
If you are talking about smaller/embedded devices or acceleration is not as
important there are framebuffers. Basically the framebuffer API supports
modesetting and a way to modify pixels. For in-kernel use there is also the
possibility to add hardware acceleration. Those can be also used from userspace
by programs (for example SDL programs can run in frambuffers) or you can start
an X server in the framebuffer. This can be done relatively easy/fast but is
essentially not accelerated. As far as I know you can add acceleration on top of
that with the DirectFB library so if you add support there it can speed up
applications that support directFB.
Hope that was a bit of help,
Florian Tobias Schandinat
prev parent reply other threads:[~2010-09-17 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 16:04 DirectFB vs. DRI Timur Tabi
2010-09-17 19:05 ` Florian Tobias Schandinat [this message]
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=4C93BC08.1050001@gmx.de \
--to=florianschandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
/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).