From: Richard Hirst <rhirst@linuxcare.com>
To: Helge Deller <deller@gmx.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] sticon/sercon patch for new bootfloppies...
Date: Wed, 13 Jun 2001 13:40:56 +0100 [thread overview]
Message-ID: <20010613134056.E16532@linuxcare.com> (raw)
In-Reply-To: <20010613002536.AB3E8482A@dsl2.external.hp.com>; from deller@gmx.de on Wed, Jun 13, 2001 at 02:24:49AM +0200
On Wed, Jun 13, 2001 at 02:24:49AM +0200, Helge Deller wrote:
> Hi,
>
> the attached patch enables only those consoles, which are given on the linux
> kernel command line.
> Examples: "console=tty0" activates STIcon only, "console=ttyS0" activates
> serial console only and if you use both on the commandline you will get the
> system messages on both consoles.
>
> Known bugs:
> - STIcon will not show any messages which happened before the STI
> initialisation
Just tried a kernel with serial console, sti console, and sti fb all
compiled in, with palo/unstable. Seems to do the right thing on my B180 :)
The kernel knows it cannot support b180 fb, so uses sti console automatically
but this kernel should use sti fb on those machines that we support.
I left the b180 alone until the "screen blanking" cut in. It just turns
off the cursor, btw, doesn't blank the screen.
When I came back to it the cursor had gone back to top-left, and all
chars are printed as blobs of garbage. System is still happy apart from
that.
I think the cursor going to top-left on a screen blank is a result of
your last lot of bug fixes, but not certain of that.
The other thing for people to note is that if you specify both
console=ttyS0 and console=tty0, then the order is important. The
real console is the second one you specify, the other just gets
a copy of boot messages (all kernel printk's, I guess).
Richard
prev parent reply other threads:[~2001-06-13 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 0:24 [parisc-linux] sticon/sercon patch for new bootfloppies Helge Deller
2001-06-13 12:40 ` Richard Hirst [this message]
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=20010613134056.E16532@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=deller@gmx.de \
--cc=parisc-linux@lists.parisc-linux.org \
/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