From: "R.L. Horn" <lists@eastcheap.org>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Fri, 20 Jun 2008 06:22:20 -0500 (CDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0806200314190.1258@hani.compact.internal> (raw)
In-Reply-To: <200806200146.03805.hpj@urpla.net>
On Fri, 20 Jun 2008, Hans-Peter Jansen wrote:
> 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,
There was a deliberate change in DTR behavior, though I'm not up on the
details. If you have a copy of 2.6.25.something handy and want to check
that that's the problem, you might look at drivers/serial/serial_core.c.
Round about line 2160 (in uart_configure_port()), you'll see:
/*
* Ensure that the modem control lines are de-activated.
* keep the DTR setting that is set in uart_set_options()
* We probably don't need a spinlock around this, but
*/
spin_lock_irqsave(&port->lock, flags);
port->ops->set_mctrl(port, port->mctrl & TIOCM_DTR);
Change the last line to:
port->ops->set_mctrl(port, 0);
which reverts to 2.6.24 behavior.
If your problem isn't resolved here, please contact me off-list with some
details about your receiver, ntpd version, etc. and I'll look into it
further. I've been thinking about building a WWVB doodad, and a solution
to this might save me some grief later on.
> 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).
That looks like a hardware problem. Odds are, something here (and it
could be the USB<->RS232 converter or the DCF receiver or both) either
isn't up to RS-232 specs or the receiver is making unfounded assumptions
about the DTE port. In particular, I'd want to know the mark/space
voltages coming out of that USB thingy.
next prev parent reply other threads:[~2008-06-20 11:23 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 [this message]
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=alpine.LNX.1.00.0806200314190.1258@hani.compact.internal \
--to=lists@eastcheap.org \
--cc=hpj@urpla.net \
--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