From: "Martin J. Bligh" <mbligh@aracnet.com>
To: James Simmons <jsimmons@infradead.org>,
Anton Blanchard <anton@samba.org>
Cc: 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 13:49:07 -0700 [thread overview]
Message-ID: <40570000.1034542147@flay> (raw)
In-Reply-To: <Pine.LNX.4.33.0210131338400.6800-100000@maxwell.earthlink.net>
>> > Are you going to have early console support (ie printk from before
>> > what is now console_init) done before the freeze, or should I just
>> > submit our version?
>>
>> On ppc64 Im currently setting a console up very early in arch init code
>> and using the CONFIG_EARLY_PRINTK hook to disable it at console_init
>> time. Works OK for me, do you guys need something on top of that?
>
> 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.
Cool, as long as it gets merged by the freeze. We've been waiting for you
to do this for a long time, but if it's not ready, then we need the hacky versions
in order to get the functionality.
M.
next prev parent reply other threads:[~2002-10-13 20:49 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 [this message]
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
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=40570000.1034542147@flay \
--to=mbligh@aracnet.com \
--cc=anton@samba.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--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.