From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
geert@linux-m68k.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org,
wli@holomorphy.com
Subject: Re: [Linux-fbdev-devel] Help re Frame Buffer/Console Problems
Date: Wed, 3 Nov 2004 07:19:04 +0800 [thread overview]
Message-ID: <200411030719.06138.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10411022257010.5391-100000@mtfhpc.demon.co.uk>
On Wednesday 03 November 2004 06:57, Mark Fortescue wrote:
> Will this work for a kernel Panic ?
>
Probably not, unless the 'Panic' tells fbcon to release the console and
tells promcon to take over the console again. That in itself is problematic
as fbcon cannot be safely unloaded yet.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
geert@linux-m68k.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org,
wli@holomorphy.com
Subject: Re: [Linux-fbdev-devel] Help re Frame Buffer/Console Problems
Date: Tue, 02 Nov 2004 23:19:04 +0000 [thread overview]
Message-ID: <200411030719.06138.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10411022257010.5391-100000@mtfhpc.demon.co.uk>
On Wednesday 03 November 2004 06:57, Mark Fortescue wrote:
> Will this work for a kernel Panic ?
>
Probably not, unless the 'Panic' tells fbcon to release the console and
tells promcon to take over the console again. That in itself is problematic
as fbcon cannot be safely unloaded yet.
Tony
next prev parent reply other threads:[~2004-11-02 23:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 18:22 Help re Frame Buffer/Console Problems Mark Fortescue
2004-10-29 18:22 ` Mark Fortescue
2004-10-29 18:27 ` William Lee Irwin III
2004-10-29 18:27 ` William Lee Irwin III
2004-10-29 20:29 ` SPARC argument passing bug in sd.c Keith M Wesolowski
2004-10-29 20:29 ` Keith M Wesolowski
2004-10-30 0:25 ` [Linux-fbdev-devel] Help re Frame Buffer/Console Problems Antonino A. Daplas
2004-10-30 0:25 ` Antonino A. Daplas
2004-11-01 17:32 ` Mark Fortescue
2004-11-01 17:32 ` Mark Fortescue
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-01 23:46 ` Antonino A. Daplas
2004-11-02 0:26 ` Helge Deller
2004-11-02 0:26 ` Helge Deller
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 14:26 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 18:03 ` Mark Fortescue
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 21:40 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 21:40 ` Antonino A. Daplas
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 22:57 ` Mark Fortescue
2004-11-02 23:19 ` Antonino A. Daplas [this message]
2004-11-02 23:19 ` Antonino A. Daplas
2004-11-03 0:01 ` Mark Fortescue
2004-11-03 0:01 ` Mark Fortescue
2004-11-03 0:01 ` Mark Fortescue
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=200411030719.06138.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=ultralinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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.