From: Sujit K M <sjt.kar@gmail.com>
To: "Nikita V. Youshchenko" <yoush@cs.msu.su>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init
Date: Thu, 20 May 2010 15:02:10 +0530 [thread overview]
Message-ID: <AANLkTil18TnOR9D-dSFsSFA74Q4UFnldrGLhG1H4jwhf@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilEbFndi-rPczi6OBxeU8p87gOz4yfveEsyHqcE@mail.gmail.com>
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 <sjt.kar@gmail.com> 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 <yoush@cs.msu.su> 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/)
next prev parent reply other threads:[~2010-05-20 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 13:13 PREEMPT_RT (2.6.33-rt17) disabled printk-to-console after console_init Xianghua Xiao
2010-05-18 19:28 ` Xianghua Xiao
2010-05-18 19:47 ` Thomas Gleixner
2010-05-18 20:49 ` Xianghua Xiao
2010-05-20 8:33 ` Nikita V. Youshchenko
2010-05-20 9:25 ` Sujit K M
2010-05-20 9:32 ` Sujit K M [this message]
2010-05-20 9:47 ` Thomas Gleixner
2010-05-20 10:23 ` Nikita V. Youshchenko
2010-05-20 10:52 ` Thomas Gleixner
2010-05-20 11:12 ` Nikita V. Youshchenko
2010-05-20 11:23 ` Thomas Gleixner
2010-05-20 11:40 ` Nikita V. Youshchenko
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=AANLkTil18TnOR9D-dSFsSFA74Q4UFnldrGLhG1H4jwhf@mail.gmail.com \
--to=sjt.kar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yoush@cs.msu.su \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).