From: Timothy Covell <timothy.covell@ashavan.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] Re: Framebuffer...Why oh Why???
Date: Sun, 30 Dec 2001 16:27:40 -0600 [thread overview]
Message-ID: <200112302231.fBUMVTSr012088@svr3.applink.net> (raw)
In-Reply-To: <20011227195037.GA229@znex> <200112302117.fBULHISr011887@svr3.applink.net> <3C2F8727.5D4AAE21@zip.com.au>
In-Reply-To: <3C2F8727.5D4AAE21@zip.com.au>
On Sunday 30 December 2001 15:29, you wrote:
> Timothy Covell wrote:
> > When X11 locks up, I can still kill it and my box lives. When
> > framebuffers crash, their is no recovery save rebooting. Back in 1995
> > I thought that linux VTs and X11 implemenation blew Solaris out of the
> > water, and now we want throw away our progress? I'm still astounded
> > by the whole "oooh I can see a penquin while I boot-up" thing?
> > Granted, frame buffers have usage in embedded systems, but do they
> > really have to be so deeply integrated??
>
> Well that's news to me....
>
> If you can send me a simple step-by-step means by which to
> reproduce this, I'll take a shot at fixing it.
Andrew,
Well, I was making reference to Solaris where I have seen
lots of X11 crashes mean framebuffer crashes which means the console
is unusable. I haven't played with it on Linux enough to know for sure that
Linux doesn't suffer the same problems. If that's true, then hats off to you
all for again showing how Solaris sucks.
--
timothy.covell@ashavan.org.
next prev parent reply other threads:[~2001-12-30 22:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 19:50 Framebuffer, mmap(), hanging in D state, root FS unmount failure Mark J Roberts
2001-12-29 0:23 ` Andrew Morton
2001-12-30 8:34 ` [patch] " Andrew Morton
2001-12-30 21:13 ` [patch] Re: Framebuffer...Why oh Why??? Timothy Covell
[not found] ` <3C2F8727.5D4AAE21@zip.com.au>
2001-12-30 22:27 ` Timothy Covell [this message]
2001-12-31 1:51 ` James Simmons
2001-12-31 2:49 ` Andrew Morton
2001-12-31 3:23 ` James Simmons
2001-12-31 12:07 ` Geert Uytterhoeven
2001-12-31 13:18 ` Alan Cox
2001-12-31 21:53 ` Oliver Xymoron
2001-12-31 0:19 ` Linus Torvalds
2001-12-31 1:54 ` [Linux-fbdev-devel] " James Simmons
2001-12-31 8:03 ` gmack
2001-12-31 9:05 ` Benjamin Herrenschmidt
2001-12-31 21:41 ` Rob Landley
2002-01-01 7:00 ` Werner Puschitz
2002-01-01 7:00 ` Timothy Covell
2002-01-01 10:42 ` Alan Cox
2002-01-01 20:36 ` Rob Landley
2002-01-02 11:36 ` Daniel Phillips
2002-01-01 14:31 ` Marius Gedminas
2002-01-03 22:26 ` Marco Ermini
2002-01-04 13:27 ` [OT] " Tommi Kyntola
2002-01-04 14:04 ` Marco Ermini
2001-12-31 21:42 ` Scott McDermott
2001-12-31 21:56 ` Arnaldo Carvalho de Melo
2001-12-31 22:26 ` James Simmons
2001-12-31 22:31 ` Arnaldo Carvalho de Melo
2002-01-01 2:43 ` Bill Nottingham
2002-01-01 6:15 ` Arnaldo Carvalho de Melo
2002-01-01 18:42 ` Joachim Steiger
2002-01-01 10:21 ` Alan Cox
2002-01-01 0:23 ` Ken Moffat
2002-01-01 7:03 ` Timothy Covell
2001-12-31 12:10 ` Geert Uytterhoeven
2002-01-07 6:36 Zwane Mwaikambo
2002-01-07 11:11 ` Marco Ermini
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=200112302231.fBUMVTSr012088@svr3.applink.net \
--to=timothy.covell@ashavan.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®