From: Anton Blanchard <anton@samba.org>
To: James Simmons <jsimmons@infradead.org>
Cc: "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: Mon, 14 Oct 2002 08:31:14 +1000 [thread overview]
Message-ID: <20021013223114.GA26506@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.33.0210131338400.6800-100000@maxwell.earthlink.net>
> 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.
Where is the hack? The ppc64 early console code uses a hypervisor call
or a serial port routine which have no business being in a generic
console infrastructure.
At the moment its two lines called before start_kernel to register the
console, and 4 lines of disable_early_printk. We use existing routines
to talk to the hypervisor or serial console.
How is the reworked console system going to reduce this? :)
Anton
next prev parent reply other threads:[~2002-10-13 22:28 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
2002-10-13 21:23 ` Andrew Morton
2002-10-14 1:18 ` Andi Kleen
2002-10-13 22:31 ` Anton Blanchard [this message]
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=20021013223114.GA26506@krispykreme \
--to=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 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.