public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: folkert <folkert@vanheusden.com>
To: Greg KH <greg@kroah.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: 2.6.25 upgraded to 2.6.36: serial app stops working
Date: Wed, 27 Jun 2012 22:26:54 +0200	[thread overview]
Message-ID: <20120627202654.GI24858@belle.intranet.vanheusden.com> (raw)
In-Reply-To: <20101130164232.GB18017@kroah.com>

> > I upgraded my linux system to 2.6.36. Now suddenly my serial driver for
> > my MSF receiver stopped working. Two things I noticed: I need to open
> > the serial device (/dev/ttyS0, a regular uart, see below) with O_NDELAY
> > for open() to return at all. Then something funny happens: I read bytes
> > from the device (at 50bps) which runs fine for a while but then suddenly
> > I get a burst of '0x00' bytes - precisely at the point at which the MSF
> > radio device sends a timecode! So I think the device fiddles with one of
> > the pins of the serial port confusing the linux serial driver. This
> > worked fine upto and including 2.6.25 (maybe later too) but with 2.6.36
> > this fails.
> > Anyone an idea what might go wrong here? And how to fix it?
> 
> Any chance you could use 'git bisect' on the kernel tree to see what
> caused the change?  Moving from .25 to .36 is a huge jump, many many
> years of development and loads of things have changed so we need some
> help to narrow the problem down.

Hmmm, I might have missed this message :-)
Anyway a few months ago I retried it and had same problem. BUT: the
other receiver I have, has a serial-to-usb converter in it. So it is an
USB device but maybe a special one? Anyway: it has exact the same
problem. It is possible that maybe they're just broken both.
As you may deduct from my replying-delay, it has no great priority for
me.


Folkert van Heusden

-- 
http://www.vanheusden.com/sysopview/ - for the real sysop
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

  reply	other threads:[~2012-06-27 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 16:27 2.6.25 upgraded to 2.6.36: serial app stops working folkert
2010-11-30 16:42 ` Greg KH
2012-06-27 20:26   ` folkert [this message]
2010-12-07 12:08 ` folkert

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=20120627202654.GI24858@belle.intranet.vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=greg@kroah.com \
    --cc=linux-serial@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