Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 27 Sep 2002 19:41:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 27 Sep 2002 19:41:20 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.106]:34529 "EHLO e6.ny.us.ibm.com") by vger.kernel.org with ESMTP id ; Fri, 27 Sep 2002 19:41:20 -0400 Message-ID: <3D94ED88.5040407@us.ibm.com> Date: Fri, 27 Sep 2002 16:45:12 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (compatible; MSIE5.5; Windows 98; X-Accept-Language: en-us, en MIME-Version: 1.0 To: Russell King , linux-kernel@vger.kernel.org Subject: sysrq on serial console Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 21 Since the serial cleanups happened in 2.5, Magic Sysrq doesn't work for me on the serial console. It looks like the UART_LSR_BI bit needs to be set in the status variable for the break character to be interpreted as a break in the driver. I doubt that it is actually broken, but it isn't immediately obvious how that bit gets set. Is there something that I should have set when the device was initialized to make sure that UART_LSR_BI is asserted in "status" when the interrupt occurs? -- Dave Hansen haveblue@us.ibm.com - 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/