public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "R.L. Horn" <lists@eastcheap.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Tue, 17 Jun 2008 05:50:09 -0500 (CDT)	[thread overview]
Message-ID: <alpine.LNX.1.00.0806170511270.11745@hani.compact.internal> (raw)
In-Reply-To: <20080616111329.3ae97879@lxorguk.ukuu.org.uk>

On Mon, 16 Jun 2008, Alan Cox wrote:

> Whatever it implies the behaviour should not have changed between 2.6.24 
> and 2.6.25.

Okay, I think I may have figured this out.

serial8250_set_termios() (8250.c) gets a baud rate using 
uart_get_baud_rate() (serial_core.c) which returns 9600 if the termios 
rate is B0.

The function does some stuff.

Right before returning, it calls tty_termios_encode_baud_rate() with the 
abovementioned rate.  That function obediently changes the c_cflag baud 
bits from B0 to B9600.  Presumably, this causes confusion in other 
functions (they never know that B0 was set).

I've now changed:

   tty_termios_encode_baud_rate(termios, baud, baud);

to:

   if ((termios->c_cflag & CBAUD) == B0)
       baud = 0;
   tty_termios_encode_baud_rate(termios, baud, baud);

And everybody's happy, I guess.

It looks like the DECstation DZ driver (drivers/serial/dz.c) will have the 
same problem, but I believe the others are okay (as of 2.6.25.6).

  parent reply	other threads:[~2008-06-17 10:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 21:36 2.6.25.3: serial problem (minicom) R.L. Horn
2008-06-14  9:29 ` Alan Cox
2008-06-15  7:04   ` R.L. Horn
2008-06-16 10:13     ` Alan Cox
2008-06-17  4:22       ` R.L. Horn
2008-06-17  8:58         ` Alan Cox
2008-06-17 11:03           ` R.L. Horn
2008-06-18  0:15           ` Hans-Peter Jansen
2008-06-18 17:55             ` Alan Cox
2008-06-18 20:07               ` Olivier Galibert
2008-06-19  8:20               ` R.L. Horn
2008-06-19 23:46               ` Hans-Peter Jansen
2008-06-20 11:22                 ` R.L. Horn
2008-06-17 10:50       ` R.L. Horn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-15 19:06 Chris Rankin
2008-05-16  3:23 ` Andrew Morton
2008-05-16  7:28   ` Chris Rankin
2008-05-16 17:33 ` Jay Cliburn
2008-05-17 12:29   ` Chris Rankin
2008-05-17 13:22     ` Jay Cliburn
2008-05-17 13:32       ` Jay Cliburn
2008-05-17 14:49       ` Chris Rankin
2008-05-17 15:10         ` Jay Cliburn
2008-05-17 18:46           ` Bart Van Assche

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=alpine.LNX.1.00.0806170511270.11745@hani.compact.internal \
    --to=lists@eastcheap.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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