From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Rahul Tank <rahul5311@yahoo.co.in>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial port multiplexing
Date: Wed, 31 Aug 2005 11:19:40 +0100 [thread overview]
Message-ID: <20050831111940.F26480@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050831101610.GB27695@lug-owl.de>; from jbglaw@lug-owl.de on Wed, Aug 31, 2005 at 12:16:10PM +0200
On Wed, Aug 31, 2005 at 12:16:10PM +0200, Jan-Benedict Glaw wrote:
> On Wed, 2005-08-31 11:10:48 +0100, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> > On Thu, Aug 25, 2005 at 01:20:45PM +0100, Rahul Tank wrote:
> > > I am a newbee tryinging for serial port
> > > multiplexing. Currently my driver supports for one
> > > port
> > > (/dev/ttyS0). However i want to use the same physical
> > > port for 2 virtual ports.I am NOT sending two type of
> > > data simultaneously. I want to first reigister my
> > > driver for /dev/ttyS0. When the kernel has booted ,i
> > > want to disable it. Then i want to enable the driver
> > > to register for say /dev/ttyS1.
> > > in short i don't want the console to have controle
> > > over the serial port.
> >
> > Try setting the kernel message level to zero after boot. That
> > will prevent the kernel from displaying any further messages to
> > that serial port, except when a serious problem (eg, oops) occurs.
>
> Alternatively, IIRC one of the printk-nullifying patches were taken
> some time ago. You should be able to eleminate any printk()s through
> kernel configuration in the embedded menu.
Yes, except I believe the OP wants to see the initial kernel messages,
and then want to shut the kernel up once it has booted.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-08-31 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 12:20 serial port multiplexing Rahul Tank
2005-08-31 10:10 ` Russell King
2005-08-31 10:16 ` Jan-Benedict Glaw
2005-08-31 10:19 ` Russell King [this message]
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=20050831111940.F26480@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul5311@yahoo.co.in \
/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