public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Anton Blanchard <anton@samba.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [BK PATCH] console changes 1
Date: Sun, 13 Oct 2002 22:00:42 +0100	[thread overview]
Message-ID: <20021013220041.G23142@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0210131338400.6800-100000@maxwell.earthlink.net>; from jsimmons@infradead.org on Sun, Oct 13, 2002 at 01:40:50PM -0700

On Sun, Oct 13, 2002 at 01:40:50PM -0700, James Simmons wrote:
> Ugh!!! The reason I reworked the console system is because over the years
> hack after hack has been added. It now has lead to this twisted monster.
> Take a look at the fbdev driver codes in 2.4.X. Instead of another hack
> the console system should be cleaned up with a well thought out design to
> make the code base smaller and more effiencent.

There is a very good reason why stuff like this is needed.  Its to get
the boot messages out of a non-booting box, when you know that its oopsed
before fbcon can be initialised.

fbcon can't be initialised before PCI setup on many systems because the
PCI bus may not be setup, and therefore the VGA card may very well not
be accessible.

I think you'll find that virtually every architecture has some method
to get real early boot time messages out of the box in some way (on ARM,
it involves enabling CONFIG_DEBUG_LL and adding a function call into
printk.c, and attaching a machine to a serial port - this works from
the moment that we start executing any kernel image.)

You're not going to be able to design something to cover all cases.
Especially the ones where the normal C environment isn't up and running
yet. 8)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2002-10-13 20:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12  1:06 [BK PATCH] console changes 1 James Simmons
2002-10-12  1:29 ` Martin J. Bligh
2002-10-12  1:40   ` James Simmons
2002-10-12  1:43   ` Anton Blanchard
2002-10-12  2:24     ` Martin J. Bligh
2002-10-13 20:40     ` James Simmons
2002-10-13 20:49       ` Martin J. Bligh
2002-10-13 21:00       ` Russell King [this message]
2002-10-13 21:23         ` Andrew Morton
2002-10-14  1:18           ` Andi Kleen
2002-10-13 22:31       ` Anton Blanchard
2002-10-12 19:22   ` Dave Hansen
2002-10-12 19:23     ` William Lee Irwin III
2002-10-12 23:43     ` Anton Blanchard

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=20021013220041.G23142@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=anton@samba.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=mbligh@aracnet.com \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox