Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #25265
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: UART behavior for CTS/RTS - Kinetis bugs? |
| Date | 2016-10-28 11:21 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <nv04u5$ltp$1@dont-email.me> (permalink) |
| References | <93dc2e49-2495-4149-8f09-305b9038f599@googlegroups.com> <nutopp$7gr$1@dont-email.me> <4c2f9b2e-570c-475a-8838-ef024e90518b@googlegroups.com> <nv04k7$kl2$1@dont-email.me> |
On 10/28/2016 11:15 AM, Don Y wrote: > On 10/28/2016 10:42 AM, Dave Nadler wrote: >> On Thursday, October 27, 2016 at 4:42:07 PM UTC-4, Don Y wrote: >>> ...A TWX would handle this differently than a modern PC, etc.... >> >> Of course, as a 'modern' PC hasn't had a serial port in a decade ;-) >> >> Seriously Don, you haven't answered the question: >> Is there any specification on how this should be handled? >> Or even any consensus? > In your case, you have two specific devices talking to each other. > You can possibly tune your implementation to that scenario. > > In my projects, I typically only know ONE end of the link (the end > that I'm coding) and have to *hope* the other party (which will > be decided by the end user and may change, over time) will be > reasonable in its implementation. So, my driver and handler > tends to be very aggressive in ensuring that data is not lost > (because its often not possible to NAK a transmission; if I miss > it, its gone!) Additionally, I tend to write comm drivers/handlers that are more generic. I.e., that support full-fledged ioctl(2)'s. So, I can choose to configure the device to support XON/XOFF, RTR/CTS, breaks, bit rates, parity, etc. from the application layer AT RUN-TIME, based on the needs of the user's peripheral equipment. In that way, I don't have to keep reinventing the same wheel.
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
UART behavior for CTS/RTS - Kinetis bugs? Dave Nadler <drn@nadler.com> - 2016-10-27 13:21 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-27 13:41 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? Dave Nadler <drn@nadler.com> - 2016-10-28 10:42 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-28 11:15 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-28 11:21 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? antispam@math.uni.wroc.pl - 2016-10-29 00:17 +0000
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-28 19:28 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? upsidedown@downunder.com - 2016-10-29 13:57 +0300
Seriial ports on PCs. (was Re: UART behavior for CTS/RTS - Kinetis bugs?) Paul <paul@pcserviceselectronics.co.uk> - 2016-10-29 09:03 +0100
Re: Seriial ports on PCs. (was Re: UART behavior for CTS/RTS - Kinetis bugs?) upsidedown@downunder.com - 2016-10-29 14:12 +0300
Re: Seriial ports on PCs. (was Re: UART behavior for CTS/RTS - Kinetis bugs?) Paul <paul@pcserviceselectronics.co.uk> - 2016-10-30 09:34 +0000
Re: UART behavior for CTS/RTS - Kinetis bugs? Tim Wescott <seemywebsite@myfooter.really> - 2016-10-27 16:39 -0500
Re: UART behavior for CTS/RTS - Kinetis bugs? Dimiter_Popoff <dp@tgi-sci.com> - 2016-10-28 01:02 +0300
Re: UART behavior for CTS/RTS - Kinetis bugs? lasselangwadtchristensen@gmail.com - 2016-10-27 15:31 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? David Brown <david.brown@hesbynett.no> - 2016-10-28 10:17 +0200
Re: UART behavior for CTS/RTS - Kinetis bugs? Grant Edwards <invalid@invalid.invalid> - 2016-10-28 14:23 +0000
Re: UART behavior for CTS/RTS - Kinetis bugs? David Brown <david.brown@hesbynett.no> - 2016-10-28 16:34 +0200
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-28 12:02 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? Don Y <blockedofcourse@foo.invalid> - 2016-10-28 11:50 -0700
Re: UART behavior for CTS/RTS - Kinetis bugs? upsidedown@downunder.com - 2016-10-29 01:51 +0300
Re: UART behavior for CTS/RTS - Kinetis bugs? upsidedown@downunder.com - 2016-10-29 13:59 +0300
Re: UART behavior for CTS/RTS - Kinetis bugs? Wolfgang Mahringer <yeti201@gmx.at> - 2016-10-28 16:45 +0200
Re: UART behavior for CTS/RTS - Kinetis bugs? Hul Tytus <ht@panix.com> - 2016-10-28 22:28 +0000
csiph-web