From: Olaf Hering <olh@suse.de>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Sachin Sant <sachinp@in.ibm.com>
Subject: Re: [PATCH] Adding ctrl-o sysrq hack support to 8250 driver
Date: Fri, 9 Dec 2005 16:34:33 +0100 [thread overview]
Message-ID: <20051209153433.GB26963@suse.de> (raw)
In-Reply-To: <20051209152530.GE15372@harddisk-recovery.com>
On Fri, Dec 09, Erik Mouw wrote:
> > 'ctrl o' is currently mapped to 'flush output', see 'stty -a'
>
> Eww... If you can't use a serial break, why can't you use an
> established control character like ctrl-] (telnet) or [enter]~ (ssh) ?
There are many ways to get to the console session on the HMC. One is
ssh. But maybe this would work somehow.
> If you really want to use ctrl-o, could you make a way that pressing
> ctrl-o twice sends a single ctrl-o to the process attached to the
> console?
Sounds good. Have to check how to handle that.
> If it is a POWER4-only problem, why isn't there a dependency on
> CONFIG_POWER4 over here? I don't like to have the ctrl-o sysrq stuff
> enabled on my regular PC if it only matters to some rare (in absolute
> numbers) system.
More CONFIG_PPC_PSERIES, the mentioned option is for gcc optimization.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2005-12-09 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 14:05 [PATCH] Adding ctrl-o sysrq hack support to 8250 driver Olaf Hering
2005-12-09 14:10 ` Russell King
2005-12-09 15:13 ` Daniel Jacobowitz
2005-12-09 15:19 ` Olaf Hering
2005-12-09 15:26 ` Daniel Jacobowitz
2005-12-09 15:28 ` Olaf Hering
2005-12-09 15:25 ` Erik Mouw
2005-12-09 15:34 ` Olaf Hering [this message]
2005-12-09 20:47 ` Olaf Hering
2005-12-09 17:08 ` Russell King
2005-12-12 10:03 ` Olaf Hering
2006-01-03 12:44 ` Olaf Hering
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=20051209153433.GB26963@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.