From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org, Sachin Sant <sachinp@in.ibm.com>
Subject: Re: [RFC] [PATCH] Adding ctrl-o sysrq hack support to 8250 driver
Date: Wed, 7 Dec 2005 23:39:11 +0000 [thread overview]
Message-ID: <20051207233911.GP6793@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051207222246.GA22558@suse.de>
On Wed, Dec 07, 2005 at 11:22:46PM +0100, Olaf Hering wrote:
> On Tue, Dec 06, Russell King wrote:
>
> > I'm still highly concerned about this whole idea. Applying this patch
> > _will_ without doubt inconvenience a lot of people who expect ^O to be
> > received as normal.
>
> If one boots with 'console=ttyS0', the 'ctrl o' should be handled only
> on ttyS0. However, I'm not sure if anyone uses ^O in this situation via
> the system console. In our case, ttyS0 is automatically activated via
> add_preferred_console in arch/powerpc/kernel/setup-common.c.
> If there is a clever way to handle ^O only for the system console, would
> such a patch be accepted? I'm currently looking through the code to see
> how it could be done.
Easily. Have a look at the internals of uart_handle_break() in
include/linux/serial_core.h
However, please be aware that ^O is the default control character for
"flush output" which I think is something you may want to use with a
serial console. Eg:
speed 38400 baud; rows 0; columns 0; line = 1;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
^^^^^^^^^^^
Hence it's a poor choice. Maybe picking a character which isn't
already used by default for another purpose would be appropriate?
'^]', the classic telnet escape character maybe?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-07 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 11:17 [RFC] [PATCH] Adding ctrl-o sysrq hack support to 8250 driver Sachin Sant
2005-11-30 12:12 ` Arjan van de Ven
2005-11-30 13:04 ` Russell King
2005-12-06 6:48 ` Sachin Sant
2005-12-06 17:16 ` Russell King
2005-12-07 6:31 ` Sachin Sant
2005-12-07 22:22 ` Olaf Hering
2005-12-07 23:39 ` Russell King [this message]
2005-12-08 14:58 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 1:38 Milton Miller
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=20051207233911.GP6793@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=sachinp@in.ibm.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