Re: [RFC] [PATCH] Adding ctrl-o sysrq hack support to 8250 driver

[Sachin Sant <sachinp@in.ibm.com>]

> Frown.  Sorry, I'm not sure what "p615", "power4" and "no-hmc" is.  I
> also don't know what an IBM 3153 is.
>
> However, you seem to be suggesting that a terminal application somehow
> forwards the ctrl-sysrq (and it's actually alt-sysrq).  Maybe it does,
> maybe it doesn't.  Probably depends on the terminal application itself.
>
> Eg, with minicom, you need to ask minicom to create the serial break
> event itself, normally by (assuming default configuration) <ctrl-a> <f>.
>
>  
Sorry about using all those cryptic terms. I was trying to explain with
the help of few test scenario's. I had tested on couple of PowerPC processor
based machines which can be configured either as a standalone machine 
[ Without any Logical Partitions ] or can be logically partitioned.
One can use a Hardware Management console [HMC] to manage the machine.


> I don't think you've addressed my concern... but I'm afraid I haven't
> been able to properly follow what you're saying.
>
> In any case, applying this patch means that you _permanently_ prevent
> the reception of ^O on _ANY_ 8250 serial port, whether it be a serial
> console or not.
>
> With this patch, I guess it's tough luck if you have a modem connected
> to your PC and you want to run ppp or x,y,z modem protocols.
>
>  
The point i was trying to make was to have a consistent behavior across
virtual and real consoles connected to certain kind of machines. 
But as stated by you this patch might cause lot of inconvenience to 
other user. So it's best not to introduce this patch.

>  

-
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/