From: Pavel Machek <pavel@ucw.cz>
To: James Simmons <jsimmons@www.infradead.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
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: [Linux-fbdev-devel] [announce 0/7] fbsplash - The Framebuffer Splash
Date: Sun, 13 Mar 2005 19:20:32 +0100 [thread overview]
Message-ID: <20050313182032.GA1427@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.56.0503111801550.10827@pentafluge.infradead.org>
Hi!
> > > > 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.
> > >
> > > Yep. The basic console we already have. Everyone who wants eye candy can switch
> > > from basic console to user space console in early userspace.
> > >
> >
> > Heh, I'm afraid it does not work like that. Anyone who wants eye-candy
> > simply applies broken patch to their kernel... unless their distribution applied one
> > already.
> >
> > Situation where we have one working eye-candy patch would certainly
> > be an improvement.
>
> 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.
Except that I'll not get usefull reports from Oopsen and panic's,
right? Ideally I'd also like high-priority kernel messages to be
displayed during boot.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-03-13 18:20 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
2005-03-15 19:22 ` James Simmons
2005-03-15 20:39 ` [Linux-fbdev-devel] " Lee Revell
2005-03-13 18:20 ` Pavel Machek [this message]
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=20050313182032.GA1427@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=adaplas@hotpop.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=jsimmons@pentafluge.infradead.org \
--cc=jsimmons@www.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).