public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe@lineo.fr>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial console and kernel 2.4
Date: Mon, 30 Jul 2001 18:21:24 +0200	[thread overview]
Message-ID: <20010730182124.C20366@pc8.lineo.fr> (raw)
In-Reply-To: <200107301520.f6UFKtT06867@localhost.localdomain> <20010730173702.C19605@pc8.lineo.fr> <035001c1190f$c6b46700$294b82ce@connecttech.com>
In-Reply-To: <035001c1190f$c6b46700$294b82ce@connecttech.com>; from stuartm@connecttech.com on lun, jui 30, 2001 at 17:53:28 +0200

I fully agree with you that the patch is not correct and I'm sure that Reto
agree too.
I'm looking in the code to find the reason but it sounds not easy (termio
stuff ever scare me).
Do you remember a related thread ? with a correct solution ?

Christophe


Le lun, 30 jui 2001 17:53:28, Stuart MacDonald a écrit :
> From: "christophe barbé" <christophe.barbe@lineo.fr>
> > "it works for me" is better that no answer for me. So Thank you for
> your
> > answer.
> > Reto give me a solution : because of a flag all incomming char are
> ignored.
> > So now I need to find why this flag is ok for you and not for me.
> 
> The patch breaks the correct operation of the serial driver.
> CREAD is the flag that enables/disables the rx side of the serial
> port. The kernel or whatever service is trying to use the console
> doesn't set CREAD, so rxed (incoming) characters are ignored.
> 
> You need to find out why the CREAD handling isn't done properly.
> This has come up a number of times on lkml recently; you should
> be able to find an appropriate answer or pointer in the right
> direction by checking the archives.
> 
> Patching the driver breaks the driver instead of fixing the problem.
> 
> ..Stu
> 
> 
> -
> 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/
> 
-- 
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

  reply	other threads:[~2001-07-30 16:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 15:20 serial console and kernel 2.4 James Bottomley
2001-07-30 15:37 ` christophe barbé
2001-07-30 15:53   ` Stuart MacDonald
2001-07-30 16:21     ` christophe barbé [this message]
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é
  -- strict thread matches above, loose matches on Subject: below --
2002-01-16 14:29 Eric Lamarque
2001-07-30 14:54 christophe barbé
2001-07-30 15:18 ` baettig
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

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=20010730182124.C20366@pc8.lineo.fr \
    --to=christophe.barbe@lineo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stuartm@connecttech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox