From: Greg KH <greg@kroah.com>
To: Larry Baker <baker@usgs.gov>
Cc: linux-serial@vger.kernel.org
Subject: Re: How can I help?
Date: Fri, 18 Apr 2014 16:19:40 -0700 [thread overview]
Message-ID: <20140418231940.GA3833@kroah.com> (raw)
In-Reply-To: <AD1ED14D-A603-4E02-8A2E-4E5113E20FBD@usgs.gov>
On Fri, Apr 18, 2014 at 04:11:26PM -0700, Larry Baker wrote:
> Greg,
>
> On 18 Apr 2014, at 3:43 PM, Greg KH wrote:
>
> > On Fri, Apr 18, 2014 at 03:37:53PM -0700, Larry Baker wrote:
> >> Greg,
> >>
> >> Any suggestions how to trace what is going on?
> >
> > Going on with what? Was there a bug report in that wall of text that I
> > missed? :)
>
> "It sort of works. What happens is, after about 8 or 9 hours, the RX
> to the TTY port times out. Sometimes it happens in only an hour,
> other times it takes about 14 hours."
>
> "I am suspicious, for example, that the CTS grant is getting lost."
>
> Should I report this on the linux-usb@vger.kernel.org mailing list?
Yes, that would be good.
But failures like this is going to be hard to track down, as you said,
how do you know it's not just the uart in the chip that drops this?
These chips are really not meant to be run all the time like this, with
constant data streams. They are really cheep chips.
I'd go buy a few different types, of different cores, and try to find
one that works for your workload. That's going to be the simplest, and
probably cheapest, way to do this.
best of luck,
greg k-h
next prev parent reply other threads:[~2014-04-18 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 21:53 How can I help? Larry Baker
2014-04-18 22:09 ` Greg KH
2014-04-18 22:37 ` Larry Baker
2014-04-18 22:43 ` Greg KH
2014-04-18 23:11 ` Larry Baker
2014-04-18 23:19 ` Greg KH [this message]
2014-04-18 23:43 ` Larry Baker
2014-04-18 22:54 ` Theodore Ts'o
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=20140418231940.GA3833@kroah.com \
--to=greg@kroah.com \
--cc=baker@usgs.gov \
--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;
as well as URLs for NNTP newsgroup(s).