On Wed, Jul 19, 2017 at 12:23:42PM -0400, David G. Simmons wrote: > > I've done a fair amount of digging around in the console in the past -- > implementing the cursor, etc. -- and I don't recall the os_time_delay() from > that, but it was admittedly a long time ago and I haven't looked at it > recently. I'd be curious to figure out why the os_time_delay() is needed, and > IF it is needed, in there at all. Simply taking it out may have some > unintended consequences that may or may not be catastrophic.
The os_time_delay() gets called when a write to the UART driver fails due to a full buffer. In this case, the code sleeps for one tick to let the output buffer drain, then attempts to write the character again. Chris
