From: Benjamin Reed <breed@almaden.ibm.com>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: BUG/PATCH: Unable to specify console=ttyX where X != 0
Date: Wed, 22 Aug 2001 16:35:03 -0700 [thread overview]
Message-ID: <3B8441A7.63D721B@almaden.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
The serial_console.txt file implies that you can specify other vt's
beside tty0 to use as a console using the console= kernel parameter.
However, if you specify any ttyX it always goes to tty0. Closer
examination shows that when the console is registered it is ignoring the
specified tty.
Basically, I want all the kernel messages to go to tty2 so that I can
have a nice clean user interaction on tty1, but still allow access to
kernel messages on tty2.
The following patch sets up the correct tty to send the messages to
based on the console= parameter and initializes the virtual terminal.
enjoy
ben
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1844 bytes --]
--- console.c.old Sun Aug 12 10:02:17 2001
+++ console.c Wed Aug 22 16:17:11 2001
@@ -2369,6 +2369,21 @@
DECLARE_TASKLET_DISABLED(console_tasklet, console_softint, 0);
+void __init con_setup_vt(unsigned int currcons)
+{
+ if (vc_cons[currcons].d) return;
+
+ vc_cons[currcons].d = (struct vc_data *)
+ alloc_bootmem(sizeof(struct vc_data));
+ vt_cons[currcons] = (struct vt_struct *)
+ alloc_bootmem(sizeof(struct vt_struct));
+ visual_init(currcons, 1);
+ screenbuf = (unsigned short *) alloc_bootmem(screenbuf_size);
+ kmalloced = 0;
+ vc_init(currcons, video_num_lines, video_num_columns,
+ currcons || !sw->con_save_screen);
+}
+
void __init con_init(void)
{
const char *display_desc = NULL;
@@ -2427,15 +2442,7 @@
* kmalloc is not running yet - we use the bootmem allocator.
*/
for (currcons = 0; currcons < MIN_NR_CONSOLES; currcons++) {
- vc_cons[currcons].d = (struct vc_data *)
- alloc_bootmem(sizeof(struct vc_data));
- vt_cons[currcons] = (struct vt_struct *)
- alloc_bootmem(sizeof(struct vt_struct));
- visual_init(currcons, 1);
- screenbuf = (unsigned short *) alloc_bootmem(screenbuf_size);
- kmalloced = 0;
- vc_init(currcons, video_num_lines, video_num_columns,
- currcons || !sw->con_save_screen);
+ con_setup_vt(currcons);
}
currcons = fg_console = 0;
master_display_fg = vc_cons[currcons].d;
@@ -2452,6 +2459,11 @@
#ifdef CONFIG_VT_CONSOLE
register_console(&vt_console_driver);
+ if (vt_console_driver.index > 0 &&
+ vt_console_driver.index < MAX_NR_CONSOLES) {
+ con_setup_vt(vt_console_driver.index-1);
+ kmsg_redirect = vt_console_driver.index;
+ }
#endif
tasklet_enable(&console_tasklet);
next reply other threads:[~2001-08-22 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 23:35 Benjamin Reed [this message]
2001-09-10 3:21 ` Paul
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=3B8441A7.63D721B@almaden.ibm.com \
--to=breed@almaden.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®