public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: baettig@scs.ch
To: christophe.barbe@lineo.fr (christophe barbé)
Cc: linux-kernel@vger.kernel.org (lkml)
Subject: Re: serial console and kernel 2.4
Date: Mon, 30 Jul 2001 17:18:12 +0200 (CEST)	[thread overview]
Message-ID: <200107301518.f6UFICd25941@rage.scs.ch> (raw)
In-Reply-To: <20010730165453.A19255@pc8.lineo.fr> from "christophe barbé" at Jul 30, 2001 04:54:53 PM

Hi! 

I had the same problem and I attached you a patch how I'm working
around this problem.

	Reto

--- drivers/char/serial.c.orig  Thu May  3 09:29:00 2001
+++ drivers/char/serial.c       Thu May  3 09:29:34 2001
@@ -1764,8 +1764,8 @@
        /*
         * !!! ignore all characters if CREAD is not set
         */
-       if ((cflag & CREAD) == 0)
-               info->ignore_status_mask |= UART_LSR_DR;
+//     if ((cflag & CREAD) == 0)
+//             info->ignore_status_mask |= UART_LSR_DR;
        save_flags(flags); cli();
        if (uart_config[info->state->type].flags & UART_STARTECH) {
                serial_outp(info, UART_LCR, 0xBF);

> 
> I recently upgraded a linux box to the kernel 2.4.4 (from 2.2.18). This box
> has no display and use the serial console. Since the upgrade I can see the
> boot output on the remote console but I can't use the keyboard. Each time I
> press a key, an interrupt is seen by the no-display machine but no char
> appears in the console. 
> Today I've upgraded an another box to 2.4.7 with a similar setup and I've
> the same problem.
> 
> Is there something that I'm missing ? (something new with the kernel 2.4
> that is required for a serial console that was not required with the 2.2 ?)
> 
> Is sombody else experienciong the same problem ?
> 
> Christophe
> 
> 
> -- 
> Christophe Barbé
> Software Engineer - christophe.barbe@lineo.fr
> Lineo France - Lineo High Availability Group
> 42-46, rue Médéric - 92110 Clichy - France
> phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
> http://www.lineo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2001-07-30 15:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 14:54 serial console and kernel 2.4 christophe barbé
2001-07-30 15:18 ` baettig [this message]
2001-07-30 15:33   ` christophe barbé
2001-07-30 15:19 ` Steve Hill
2001-07-30 20:43 ` Fabrice Gautier
2001-07-30 20:59   ` Miquel van Smoorenburg
  -- strict thread matches above, loose matches on Subject: below --
2001-07-30 15:20 James Bottomley
2001-07-30 15:37 ` christophe barbé
2001-07-30 15:53   ` Stuart MacDonald
2001-07-30 16:21     ` christophe barbé
2001-07-30 16:55       ` Chris Wedgwood
2001-07-30 20:36         ` Thomas Duffy
2001-07-30 21:41           ` Chris Wedgwood
2001-07-30 22:24             ` Miquel van Smoorenburg
2001-07-31  7:51               ` christophe barbé
2002-01-16 14:29 Eric Lamarque

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=200107301518.f6UFICd25941@rage.scs.ch \
    --to=baettig@scs.ch \
    --cc=christophe.barbe@lineo.fr \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox