Date: Wed, 7 Dec 2005 23:22:46 +0100
From: Olaf Hering <olh@suse.de>
To: linux-kernel@vger.kernel.org, Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Sachin Sant <sachinp@in.ibm.com>
Subject: Re: [RFC] [PATCH] Adding ctrl-o sysrq hack support to 8250 driver
Message-ID: <20051207222246.GA22558@suse.de>
References: <438D8A3A.9030400@in.ibm.com> <20051130130429.GB25032@flint.arm.linux.org.uk> <43953440.9070102@in.ibm.com> <20051206171633.GB19664@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20051206171633.GB19664@flint.arm.linux.org.uk>
User-Agent: Mutt und vi sind doch schneller als Notes (und GroupWise)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 22

 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.

-- 
short story of a lazy sysadmin:
 alias appserv=wotan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/