linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	James Simmons <jsimmons@pentafluge.infradead.org>,
	Michal Januszewski <spock@gentoo.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: [announce 0/7] fbsplash - The Framebuffer Splash
Date: Tue, 15 Mar 2005 14:03:50 -0500	[thread overview]
Message-ID: <9e4733910503151103b8a9c8f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0503151855430.5506@pentafluge.infradead.org>

On Tue, 15 Mar 2005 18:58:08 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
> 
> > > Why do we need patches in the kernel. Just set you config to
> > > CONFIG_DUMMY_CONSOLE, CONFIG_FB, CONFIG_INPUT and don't set fbcon or
> > > vgacon. Then have a userspace app using /dev/fb and /dev/input create a
> > > userland console. There is no need to do special hacks in the kernel.
> >
> > /dev/fb is not accelerated, if you want full acceleration use
> > /dev/dri. Using /dev/dri you can write a fully composited console that
> > displays dengavi in realtime. This is also a path to getting multiuser
> > working without a lot of kernel patches.
> 
> Not every device has a 3D core!!! DRM is not the answer for the entire graphics
> world. Its only for 3D functionality. If you want eye candy without 3D on small
> devices use fbdev.

DRM doesn't know a thing about 3D. All it does is DMA, memory
management and queue things up for the GPU to work on. You don't even
have to have a GPU processor you could use the CPU to execute the
commands.

It's the code up in mesa that knows about 3D and builds the commands
to be sent to DRM.


-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-15 19:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08  1:57 [announce 0/7] fbsplash - The Framebuffer Splash Michal Januszewski
2005-03-08 19:46 ` James Simmons
2005-03-08 20:52   ` Jon Smirl
2005-03-08 22:27     ` James Simmons
2005-03-09 11:38   ` [Linux-fbdev-devel] " Pavel Machek
2005-03-09 22:47     ` Christoph Hellwig
2005-03-09  5:01 ` Antonino A. Daplas
2005-03-09  6:02   ` Jon Smirl
2005-03-09  9:34     ` Geert Uytterhoeven
2005-03-09 18:16       ` [Linux-fbdev-devel] " Alan Cox
2005-03-09 20:33         ` Geert Uytterhoeven
2005-03-09 20:45         ` James Simmons
2005-03-09 22:40           ` [Linux-fbdev-devel] " Alan Cox
2005-03-10  9:12             ` Geert Uytterhoeven
2005-03-10 14:54               ` Pavel Machek
2005-03-11 18:03                 ` [Linux-fbdev-devel] " James Simmons
2005-03-11 18:13                   ` Jon Smirl
2005-03-15 18:58                     ` James Simmons
2005-03-15 19:03                       ` Jon Smirl [this message]
2005-03-15 19:22                         ` James Simmons
2005-03-15 20:39                       ` [Linux-fbdev-devel] " Lee Revell
2005-03-13 18:20                   ` Pavel Machek
2005-03-13 18:53                     ` Geert Uytterhoeven
2005-03-13 19:24                       ` Jon Smirl
2005-03-13 19:34                   ` [Linux-fbdev-devel] " Elladan

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=9e4733910503151103b8a9c8f@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@pentafluge.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spock@gentoo.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).