Re: UART driver: read function

2015-03-20 Thread Joel Sherrill
On 3/20/2015 10:12 AM, Sebastian Huber wrote: > - Daniel Krüger schrieb: >> Beside some problems/differences between newlibc and glibc, one >> RTEMS-specific questions remains unanswered: >> >> What is the right implementation for the UART driver read function

Re: UART driver: read function

2015-03-20 Thread Sebastian Huber
- Daniel Krüger schrieb: > Beside some problems/differences between newlibc and glibc, one > RTEMS-specific questions remains unanswered: > > What is the right implementation for the UART driver read function > (console_fns.deviceRead)? It seems to be implemented d

Re: UART driver: read function

2015-03-20 Thread Joel Sherrill
On 3/20/2015 9:59 AM, Daniel Krüger wrote: > Beside some problems/differences between newlibc and glibc, one > RTEMS-specific questions remains unanswered: > > What is the right implementation for the UART driver read function > (console_fns.deviceRead)? It seems to be implemen

Re: UART driver: read function

2015-03-20 Thread Daniel Krüger
Beside some problems/differences between newlibc and glibc, one RTEMS-specific questions remains unanswered: What is the right implementation for the UART driver read function (console_fns.deviceRead)? It seems to be implemented differently from target to target. Some implementations return

Re: UART driver: read function

2015-03-20 Thread Daniel Krüger
Am 20.03.2015 um 11:11 schrieb Sebastian Huber: On 20/03/15 11:03, Daniel Krüger wrote: Am 20.03.2015 um 10:02 schrieb Sebastian Huber: On 20/03/15 09:42, Daniel Krüger wrote: Am 06.03.2015 um 11:20 schrieb Sebastian Huber: I would not use the C stdio for this and instead directly use the PO

Re: UART driver: read function

2015-03-20 Thread Sebastian Huber
On 20/03/15 11:03, Daniel Krüger wrote: Am 20.03.2015 um 10:02 schrieb Sebastian Huber: On 20/03/15 09:42, Daniel Krüger wrote: Am 06.03.2015 um 11:20 schrieb Sebastian Huber: I would not use the C stdio for this and instead directly use the POSIX read/write. You have to set up the right

Re: UART driver: read function

2015-03-20 Thread Daniel Krüger
Am 20.03.2015 um 10:02 schrieb Sebastian Huber: On 20/03/15 09:42, Daniel Krüger wrote: Am 06.03.2015 um 11:20 schrieb Sebastian Huber: I would not use the C stdio for this and instead directly use the POSIX read/write. You have to set up the right Termios settings. In case you use RTEMS 4.11

Re: UART driver: read function

2015-03-20 Thread Sebastian Huber
Hello Daniel, On 20/03/15 09:42, Daniel Krüger wrote: Hello Sebastian, Am 06.03.2015 um 11:20 schrieb Sebastian Huber: Hello Daniel, I would not use the C stdio for this and instead directly use the POSIX read/write. You have to set up the right Termios settings. In case you use RTEMS 4.11 I

Re: UART driver: read function

2015-03-20 Thread Daniel Krüger
gards, Daniel Krüger On 06/03/15 10:52, Daniel Krüger wrote: Hello, what is the right implementation for the UART driver read function (console_fns .deviceRead)? It seems to be implemented differently from target to target. Some implementations return -1 if the receive FIFO is empty and some imp

Re: UART driver: read function

2015-03-06 Thread Sebastian Huber
wrote: Hello, what is the right implementation for the UART driver read function (console_fns .deviceRead)? It seems to be implemented differently from target to target. Some implementations return -1 if the receive FIFO is empty and some implementations do a busy waiting for new characters. I

UART driver: read function

2015-03-06 Thread Daniel Krüger
Hello, what is the right implementation for the UART driver read function (console_fns .deviceRead)? It seems to be implemented differently from target to target. Some implementations return -1 if the receive FIFO is empty and some implementations do a busy waiting for new characters. I