public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans-Peter Jansen" <hpj@urpla.net>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"R.L. Horn" <lists@eastcheap.org>,
	Olivier Galibert <galibert@pobox.com>
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Fri, 20 Jun 2008 01:46:03 +0200	[thread overview]
Message-ID: <200806200146.03805.hpj@urpla.net> (raw)
In-Reply-To: <20080618185534.5f969f63@lxorguk.ukuu.org.uk>

Am Mittwoch, 18. Juni 2008 schrieb Alan Cox:
> On Wed, 18 Jun 2008 02:15:45 +0200
>
> "Hans-Peter Jansen" <hpj@urpla.net> wrote:
> > Am Dienstag, 17. Juni 2008 schrieb Alan Cox:
> > > On Mon, 16 Jun 2008 23:22:54 -0500 (CDT)
> > >
> > > Ah ok I know what the bug is - it was fixed in 2.6.26-rc as follows
> > >
> > > +       /* Don't rewrite B0 */
> > > +       if (tty_termios_baud_rate(termios))
> > > +               tty_termios_encode_baud_rate(termios, baud, baud);
> > >  }
> >
> > Alan, could this issue lead to dysfunctional serial dcf77 receivers,
> > too? (and could you point my to the related git changeset?)
>
> I don't generally work via git so I don't offhand know the changeset id.
> I guess it could do. If its causing this many actual problem cases it
> might also want to go into stable.

Alan, I got to test this by applying the changeset (Olivier, many thanks 
for your valuable hint, I'm sure, I will reuse this knowledge soon), to 
the otherwise unchanged kernel, but unfortunately, it doesn't solve my 
issue.

A different patch must have changed the behavior/state of some RS232 lines  
in the 2.6.25 time frame, since the device still doesn't get any power at 
all. Hopefully I get round bisecting it this weekend, but any hints are 
greatly appreciated.

As another data point: using a usb <-> rs232 converter, the dcf device got 
back to life again. It still doesn't work in its entirety, but at least, 
some data arrives in ntpd. Expected is something similar to:
-#--#-#####-###--D--S124--2-p------p-----21-4-24-----8-- (incomplete)
but it reads:
###############RADMLS1248124P124812P1248121241248112481248P
thus, obviously it doesn't get any 0 values back (displayed as - above).

The setting of the serial interfaces was equivalent, but maybe the usb 
converter cannot handle the rather strange 50 baud setting properly.

~# stty -a < /dev/ttyUSB0 
speed 50 baud; rows 0; columns 0; line = 0;
intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>; eol = <undef>; eol2 = <undef>;
swtch = <undef>; start = <undef>; stop = <undef>; susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
flush = <undef>; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke

Pete

  parent reply	other threads:[~2008-06-19 23:46 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 [this message]
2008-06-20 11:22                 ` R.L. Horn
2008-06-17 10:50       ` R.L. Horn
  -- 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=200806200146.03805.hpj@urpla.net \
    --to=hpj@urpla.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@eastcheap.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