Le vendredi 21 juin 2019 à 14:14 +0200, Wolfgang Denk a écrit :
> Dear Julien,
>
> The i.MX28 is a special beast.
>
> Your issue is most likely caused by a somewhat stup^H^H^H^Hsimple
> implementation of the UART driver. When it receives the interrupt
> after receiving a block of data, it stops D
Dear Julien,
In message <0881c8f094cabf8753b31f4899ce879658d204ae.ca...@sprinte.eu> you
wrote:
>
>
> > If the issue is on the receive side you probably need HW flow-control
> > via RTS/CTS pins to make sure you don’t lose anything.
>
> This proved to be a very good advice, as it seems to solve o
Le vendredi 14 juin 2019 à 13:19 +, Lange Norbert a écrit :
> If the issue is on the receive side you probably need HW flow-control
> via RTS/CTS pins to make sure you don’t lose anything.
This proved to be a very good advice, as it seems to solve our issues.
Why we did not think about enabl
> -Original Message-
> From: Julien Blanc
> Sent: Freitag, 14. Juni 2019 14:46
> To: Lange Norbert ; Xenomai
> (xenomai@xenomai.org)
> Subject: Re: serial driver for imx28
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION
Le vendredi 14 juin 2019 à 12:26 +, Lange Norbert via Xenomai a
écrit :
> > -Original Message-
> > From: Xenomai On Behalf Of Julien
> > Blanc
> > via Xenomai
> > Sent: Freitag, 14. Juni 2019 13:54
> > To: Xenomai@xenomai.org
> > Subject: serial driver for imx28
> >
> >
> > We’re cur
> -Original Message-
> From: Xenomai On Behalf Of Julien Blanc
> via Xenomai
> Sent: Freitag, 14. Juni 2019 13:54
> To: Xenomai@xenomai.org
> Subject: serial driver for imx28
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION WITH E-MAIL CONTENT AND AN
