public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: ecos-devel@ecos.sourceware.org
Subject: Re: Handling RTS with an UART that doesn't directly drives the RTS pin
Date: Tue, 12 Jun 2012 13:12:00 -0000	[thread overview]
Message-ID: <4FD7402F.2040602@meduna.org> (raw)
In-Reply-To: <4FD7374A.1090602@kuantic.com>

On 12.06.2012 14:34, Bernard Fouché wrote:

> I think the change is to be done in serial.c, since it's the part of the
> code that takes the decision to call throttle_rx() or restart_rx()

Is this the correct place at all? As far as I can tell the
flow-control here depends on channel buffer watermarks. It does
not protect you from overflowing the 16x5x FIFO; it does not
even know how deep it is.

I do not know what UART speeds, UART FIFO sizes and maximum
guaranteed DSR latency do you have in your system, but in case
you want to protect against UART FIFO overflow I'm afraid
the only reliable way is to modify the low level driver's ISR.

Regards
-- 
                                      Stano

  reply	other threads:[~2012-06-12 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:34 Bernard Fouché
2012-06-12 13:12 ` Stanislav Meduna [this message]
2012-06-12 13:16 ` Nick Garnett
2012-06-12 16:56   ` Bernard Fouché
2012-06-13 10:10     ` Nick Garnett
2012-06-13 16:37       ` Bernard Fouché
2012-06-14 15:33         ` Bernard Fouché
     [not found] ` <4FDF355B.2010209@mindspring.com>
2012-06-18 14:34   ` Closing devices Frank Pagliughi
2012-06-19 13:36     ` Bernard Fouché
2012-06-20 13:38       ` Frank Pagliughi
2012-06-20 15:20         ` Bernard Fouché
2012-06-21 18:20           ` Frank Pagliughi
2012-06-22  8:33             ` Bernard Fouché
2012-06-22 14:48               ` Frank Pagliughi

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=4FD7402F.2040602@meduna.org \
    --to=stano@meduna.org \
    --cc=ecos-devel@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).