All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Navin Boppuri <navin.boppuri@newisys.com>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Ctrl-C does not work
Date: Thu, 06 Sep 2001 10:37:48 -0500	[thread overview]
Message-ID: <3B97984C.CCE09FE7@mvista.com> (raw)
In-Reply-To: 3A494DE356A49A40B37442E1E0D9F3B506343E@ptah.ad.newisys.com


Navin Boppuri wrote:
>
> Hello everyone,
>
> Ctrl-C does on work on my serial console when I use the sample file
> system from Hardhat 1.0 toolkit. It , however, works with the Hardhat
> 1.2 toolkit sample file system. I am using the same kernel to test both
> the file systems. What could be different between these two file
> systems?
>
> Thank you,
> Navin

Actually control-c should _NOT_ be working on Cross Dev Kit 1.0, or
1.2.  If it does work in one you are lucky.  There is a problem with the
way the serial consoles are started on CDK 1.0 and 1.2, it was left up
to the serial driver to turn on or off the control-c activation.

Under HHL 2.0, this problem has been resolved by using getty and login
to start a serial connection.  login has a patch that ensures that the
control-c stuff is enabled.

I would highly recommend that you move forward to HHL 2.0 if you can, it
has a lot of these minor annoyances fixed.

--Mark Hatle
MontaVista Software, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-09-06 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 20:57 Ctrl-C does not work Navin Boppuri
2001-09-05 21:53 ` Cal Erickson
2001-09-06 15:37 ` Mark Hatle [this message]
2001-09-06 17:56   ` Dan Malek
2001-09-06 18:11     ` Mark Hatle

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=3B97984C.CCE09FE7@mvista.com \
    --to=fray@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=navin.boppuri@newisys.com \
    /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.