From: "Stuart MacDonald" <stuartm@connecttech.com>
To: slack@slackware.ru, alan@redhat.com
Cc: linux-serial@vger.kernel.org
Subject: Re: problems with serial driver
Date: Tue, 3 Sep 2002 10:56:17 -0400 [thread overview]
Message-ID: <010501c2535a$0fe62be0$294b82ce@connecttech.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209021345330.21930-100000@scil.sinp.msu.ru
From: <slack@slackware.ru>
> 1. Starting receiver, sender: all is OK.
> 2. Starting sender, receiver: sometimes OK, sometimes I've got damaged
> data. Sometimes - IRQ overruns (losting NULL pointer etc). Kernel down.
I'm not convinced this is a problem. The sender starts sending data
right away, correct? Well, that data is discarded by the receiver port
since it's not open for reading. The port knows it's not opened, and
thus nobody is interested in the data coming in, so it drops it. This
is correct behaviour.
> Progs are very simple: send/receive (like in HOWTO). So,
> operations are intensive. Installation of some
> usleeps before read() from port solves the problem.
> Kernels are up to 2.4.18 and on modern up to 2.5.17.
Installation of usleep()s where? In the user space application? That
shouldn't make a difference. Actually it should make it worse.
..Stu
next prev parent reply other threads:[~2002-09-03 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 9:55 problems with serial driver slack
2002-09-03 14:56 ` Stuart MacDonald [this message]
2002-09-03 14:30 ` slack
2002-09-03 15:29 ` Stuart MacDonald
2002-09-03 15:34 ` slack
2002-09-03 18:21 ` Stuart MacDonald
2002-09-04 5:39 ` slack
2002-09-04 12:57 ` Stuart MacDonald
2002-09-04 14:21 ` slack
2002-09-04 16:22 ` Stuart MacDonald
2002-09-03 19:17 ` David Lawyer
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='010501c2535a$0fe62be0$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=alan@redhat.com \
--cc=linux-serial@vger.kernel.org \
--cc=slack@slackware.ru \
/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