From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Olaf Hering <olh@suse.de>
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 14:10:49 +0000 [thread overview]
Message-ID: <20051209141049.GA31708@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051209140559.GA23868@suse.de>
On Fri, Dec 09, 2005 at 03:05:59PM +0100, Olaf Hering wrote:
>
> If you can queue this up in -mm for a decade or two, just to make sure
> it doesnt make some setup unhappy.
>
>
> a POWER4 system in 'full-system-partition' mode has the console device
> on ttyS0. But the user interface to the Linux system console may still
> be on the hardware management console (HMC). If this is the case, there
> is no way to send a break to trigger a sysrq.
> Other setups do already use 'ctrl o' to trigger sysrq. This includes iSeries
> virtual console on tty1, and pSeries LPAR console on hvc0 or hvsi0.
>
> 'ctrl o' is currently mapped to 'flush output', see 'stty -a'
I still strongly disagree with the idea of using a well defined
control character which already has an expected purpose for this.
--
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-09 14:10 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 [this message]
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
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=20051209141049.GA31708@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--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 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.