From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754637Ab0ETJcO (ORCPT ); Thu, 20 May 2010 05:32:14 -0400 Received: from mail-qy0-f171.google.com ([209.85.221.171]:34126 "EHLO mail-qy0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753943Ab0ETJcM convert rfc822-to-8bit (ORCPT ); Thu, 20 May 2010 05:32:12 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=kV8F0UNZ9yYV40ln5DVLgydJ1h88rBzMzcwH6IGhrRkP2IKiFuYs9jwRxfrJiZ6C5p oWfCmNp2iPbH5ti4zWAQKZWAPd1AVroWYvceZzFevtu937lsHIPGoTf3VQ0hFlbMLjrC zrtJy5NnOnzm4Tcej6CXezmFl7uJwpBJCPcOA= MIME-Version: 1.0 In-Reply-To: References: <201005201233.56877@zigzag.lvk.cs.msu.su> Date: Thu, 20 May 2010 15:02:10 +0530 Message-ID: Subject: Re: PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init From: Sujit K M To: "Nikita V. Youshchenko" Cc: Thomas Gleixner , linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sorry does not help as it is very old and does not seem to provide information regarding Real Time Linux. But the section for setserial -g /dev/ttyS[01] and /etc/inittab modifications are pointer to the changes required for Real Timliness. The problem is that baud rate of the COM/TTY port may require some modification. I Think you will need to have an Critical Section for the Driver to timeout in sync with the baud rate. Hope what I have said makes sense. On Thu, May 20, 2010 at 2:55 PM, Sujit K M wrote: > http://www.vanemery.com/Linux/Serial/serial-console.html > > Could this be of help. > > On Thu, May 20, 2010 at 2:03 PM, Nikita V. Youshchenko wrote: >>> > I could not get dmesg output to console/serial and >>> > klogd(/var/log/messages) anymore with 2.6.33-rt17 _after_ the kernel >>> > boot is done(on non-RT kernel it works fine). I made below changes it >>> > starts to work again, however I'm unsure how safe the change is. >>> > Please advise. >>> >>> Well, obviously it's unsafe if you remove safety checks. And if you >>> care to look at the changelog of kernel/printk.c you'll find out why. >> >> Hmm... did a quick look and could not find anything related there. >> Could you please give a pointer? >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at  http://vger.kernel.org/majordomo-info.html >> > > > > -- > -- Sujit K M > > blog(http://kmsujit.blogspot.com/) > -- -- Sujit K M blog(http://kmsujit.blogspot.com/)