From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Simmons <jsimmons@pentafluge.infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Michal Januszewski <spock@gentoo.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: [Linux-fbdev-devel] [announce 0/7] fbsplash - The Framebuffer Splash
Date: Wed, 09 Mar 2005 22:40:50 +0000 [thread overview]
Message-ID: <1110408049.9942.275.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.56.0503092043380.7510@pentafluge.infradead.org>
On Mer, 2005-03-09 at 20:45, James Simmons wrote:
> Thank you. We need some kind of basic console in the kernel. I'm not the
> biggest fan of eye candy. So moving the console to userspace for eye candy
> is a dumb idea.
Thats why moving the eye candy console into user space is such a good
idea. You don't have to run it 8) It also means that the console
development is accessible to all the crazy rasterman types.
next prev parent reply other threads:[~2005-03-09 22:40 UTC|newest]
Thread overview: 43+ 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 1:57 ` Michal Januszewski
2005-03-08 19:46 ` James Simmons
2005-03-08 19:46 ` [Linux-fbdev-devel] " James Simmons
2005-03-08 20:52 ` Jon Smirl
2005-03-08 20:52 ` [Linux-fbdev-devel] " Jon Smirl
2005-03-08 22:27 ` James Simmons
2005-03-08 22:27 ` [Linux-fbdev-devel] " James Simmons
2005-03-09 11:38 ` Pavel Machek
2005-03-09 22:47 ` Christoph Hellwig
2005-03-10 3:29 ` Sebastian Kügler
2005-03-09 5:01 ` Antonino A. Daplas
2005-03-09 5:01 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-03-09 6:02 ` Jon Smirl
2005-03-09 6:02 ` [Linux-fbdev-devel] " Jon Smirl
2005-03-09 9:34 ` Geert Uytterhoeven
2005-03-09 9:34 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-03-09 18:16 ` Alan Cox
2005-03-09 20:33 ` Geert Uytterhoeven
2005-03-09 20:33 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-03-09 20:45 ` James Simmons
2005-03-09 20:45 ` [Linux-fbdev-devel] " James Simmons
2005-03-09 22:40 ` Alan Cox [this message]
2005-03-10 9:12 ` Geert Uytterhoeven
2005-03-10 9:12 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-03-10 14:54 ` Pavel Machek
2005-03-10 14:54 ` [Linux-fbdev-devel] " Pavel Machek
2005-03-11 18:03 ` James Simmons
2005-03-11 18:13 ` Jon Smirl
2005-03-11 18:13 ` [Linux-fbdev-devel] " Jon Smirl
2005-03-15 18:58 ` James Simmons
2005-03-15 18:58 ` [Linux-fbdev-devel] " James Simmons
2005-03-15 19:03 ` Jon Smirl
2005-03-15 19:03 ` [Linux-fbdev-devel] " Jon Smirl
2005-03-15 19:22 ` James Simmons
2005-03-15 19:22 ` [Linux-fbdev-devel] " James Simmons
2005-03-15 20:39 ` Lee Revell
2005-03-13 18:20 ` Pavel Machek
2005-03-13 18:53 ` Geert Uytterhoeven
2005-03-13 18:53 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-03-13 19:24 ` Jon Smirl
2005-03-13 19:24 ` [Linux-fbdev-devel] " Jon Smirl
2005-03-13 19:34 ` 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=1110408049.9942.275.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=adaplas@hotpop.com \
--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 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.