public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Ruud Linders <kernelml@xs4all.nl>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	Johan Hovold <jhovold@gmail.com>, Alan Cox <alan@linux.intel.com>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb-serial/ftdi_sio: fix DTR/RTS line modes
Date: Sun, 6 Jun 2010 11:44:07 +0200	[thread overview]
Message-ID: <20100606094407.GN2695@buzzloop.caiaq.de> (raw)
In-Reply-To: <4C0B6B52.5050702@xs4all.nl>

On Sun, Jun 06, 2010 at 11:33:06AM +0200, Ruud Linders wrote:
> Hmm, I tried this patch on plain 2.6.34 but still have a problem.
> As you indicated since 2.6.31-something something is broken.
> 
> I'm using a receive only device (http://rfxcom.com/receivers.htm)
> which works fine until the system becomes more busy, usually it runs
> almost idle and all is fine.
> 
> However, when this happens, it appears the received characters get
> buffered somewhere as nothing seems to get through or is delayed for
> many minutes.
> When I then =write= a character to the serial device
> 	echo > /dev/ttyUSB0
> the data is received in sudden burst, seems no data is actually lost
> just seriously delayed.
> 
> Any ideas ?

Hmm, no, sorry. Things work fine for me again now.

Did you try reverting the commit I blamed in the commit log? If this
doesn't help, I can only suggest you run a bisect to see which commit
between 2.6.31 and 2.6.34 broke it for you.

Daniel


      reply	other threads:[~2010-06-06  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 11:55 [PATCH] usb-serial/ftdi_sio: fix DTR/RTS line modes Daniel Mack
2010-06-03 11:32 ` Alan Cox
2010-06-03 12:23   ` Daniel Mack
2010-06-03 11:57 ` Daniel Mack
2010-06-03 14:27   ` Greg KH
2010-06-03 16:21   ` Gene Heskett
2010-06-03 16:26     ` Greg KH
2010-06-03 16:53       ` Gene Heskett
2010-06-06  9:33   ` Ruud Linders
2010-06-06  9:44     ` Daniel Mack [this message]

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=20100606094407.GN2695@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alan@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=jhovold@gmail.com \
    --cc=kernelml@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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