[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [Anders Gnistrup <agn@city.dk>] (fwd)
- To: rtl@rtlinux.org
- Subject: BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [Anders Gnistrup <agn@city.dk>] (fwd)
- From: Der Herr Hofrat <der.herr@hofr.at>
- Date: Thu, 7 Jun 2001 05:49:50 +0200 (CEST)
>From owner-rtl Wed Jun 6 13:41:02 2001
Received: from emdrupborg.dk (emdrupborg.dk [130.226.204.250])
by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f56Jf1C20167
for <rtl@fsmlabs.com>; Wed, 6 Jun 2001 13:41:02 -0600
Received: from city.dk (unknown [10.0.0.24])
by emdrupborg.dk (Postfix) with ESMTP id D54FE8C002
for <rtl@fsmlabs.com>; Wed, 6 Jun 2001 21:35:24 +0200 (CEST)
Sender: agn@emdrupborg.dk
Message-ID: <3B1EA0D4.75D01F4B@city.dk>
Date: Wed, 06 Jun 2001 20:29:56 -0100
From: Anders Gnistrup <agn@city.dk>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.4 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: rtl@fsmlabs.com
Subject: Re: [rtl] rt_com
References: <32055449.991727270126.JavaMail.imail@dotty.excite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I think it is some internel timing in the UART. If the time between to chars
is "small" this might be the answer. If the time between to chars is large I
don not no.
Anders Gnistrup
Evgeni Dobrev wrote:
> Hello Anders,
>
> thank you for the advice. Now the char is sent back between 0.055mS and
> 0,089 mS after the serial port receives the char (@19200). The response
> time fluctuates though between those two values in "regular" (periodic) way.
> What could be the cause for this fluctuation?
>
> Anyway now I am within the 3bits limit :). thank you very much once again.
>
> evgeni
>
> > The problem is not the driver but the way the register in the serial port
> is
> > set up.
> > The UART does not generate a interrupt for every char it recived if it
> has't
> > been
> > tould to do so. It is the register for the input fifo.
> > I think this is what happens. ->
> > the computer recives a char.
> > It does NOT make a interrups at once but wait's.
> > It ganerate a interrupt when "No Charecters have Been removed From or
> input to
> > the RCVR FIFO During the last 4 Char."
> > (thats 1/(19200/10bits) ~2mSec.)
> > The driver catch the interrupt. do what ever you wont it to and send a
> byte
> > (0.2~ mSec).
> >
> > I can't remeber if it is posible to set the number of chars before
> interrups
> > with the rt_setup call. If not you have to make some minor changes in the
> > driver.
> >
> > Anders Gnistrup
> >
> > -- [rtl] ---
> > To unsubscribe:
> > echo "unsubscribe rtl" | mail majordomo@rtlinux.org OR
> > echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.org
> > --
> > For more information on Real-Time Linux see:
> > http://www.rtlinux.org/rtlinux/
> >
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
>
> ----- End of forwarded message from owner-rtl@fsmlabs.com -----
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail majordomo@rtlinux.org OR
> echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.org
> --
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/