All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Howard, Marc" <Marc.Howard@KLA-Tencor.com>
Cc: ppc <linuxppc-embedded@ozlabs.org>
Subject: RE: Deactivate serial console?
Date: Tue, 22 Aug 2006 13:57:38 -0400	[thread overview]
Message-ID: <1156269458.10565.182.camel@mindpipe> (raw)
In-Reply-To: <91B22F93A880FA48879475E134D6F0BE02EEA435@CA1EXCLV02.adcorp.kla-tencor.com>

On Tue, 2006-08-22 at 10:46 -0700, Howard, Marc wrote:
> "stty -F /dev/console 0" or the equivalent in code does the trick for me
> but it might be implementation dependent.
> 

That works for disabling the console but now I can't re-enable it.  stty
-F /dev/console 115200 does not restore serial console access.

Lee

> Marc W. Howard
> 
> > -----Original Message-----
> > From: 
> > linuxppc-embedded-bounces+marc.howard=kla-tencor.com@ozlabs.or
> g [mailto:linuxppc-embedded-bounces+marc.howard=kla->
> tencor.com@ozlabs.org] On Behalf Of Lee Revell
> > Sent: Tuesday, August 22, 2006 9:19 AM
> > To: ppc
> > Subject: Deactivate serial console?
> > 
> > We're developing a PPC440 based system for a customer who 
> > requires that
> > it be possible to disable/enable the serial console without a reboot.
> > Is this possible without hacking the kernel?
> > 
> > Lee
> > 
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> > 
> 

  parent reply	other threads:[~2006-08-22 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 17:46 Deactivate serial console? Howard, Marc
2006-08-22 17:55 ` Lee Revell
2006-08-23  1:26   ` Michael Richardson
2006-08-22 17:57 ` Lee Revell [this message]
2006-08-22 18:27   ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2006-08-22 16:18 Lee Revell

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=1156269458.10565.182.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=Marc.Howard@KLA-Tencor.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.