semantics: match a single line of text: ends with a \r\n

blocking calls to send / receive a single byte from the uart.

expect op

expect op

yield the current thread.

"what happens if we comment out?"

if adding 1 to head = tail, then we have no space.

returns <n> if wrote, 0 otherwise.

consumes a single char, verifies it matches what we expect.

read the entire line into <buf> and null terminate it. returns 0 if it was empty.

connect, disconnect. print wth messages. change the debugging.

returns a cursor to the current position in the stream. used to rewind after a failed match.

returns a cursor to the current position in the stream. used to rewind after a failed match.

read in more data.

can reset the stream to the snapshot in <l>

revert back to a checkpoint.

get a single character.

skip spaces? sometimes we get a \r\n sometimes a \n\r

Initialize the random number generator based on the given seed. If the type is the trivial no-state-information type, just remember the seed. O

* starts the thread system. * note: our caller is not a thread! so you have to figure * out how to handle this. */

https://clc-wiki.net/wiki/strncmp#Implementation

do this first: used timed_write to cleanup. recall: time to write each bit (0 or 1) is in <uart->usec_per_bit>

hack to see if the ttyusb serial was unplugged.

drain random data that appears after a reset. not sure a better way.

drain random data that appears after a reset. not sure a better way.

returns when <cmd> has been acknowledged (echoed) by the esp

echo the current line out, printing <msg>

checking if a single char matches what we expect.

check that we get what we expect.

returns 0 if not exited, 1 if exited cleanly, < 0 otherwise. should clean this up.

we could get rid of most of this if our gettok skipped sapces.

XXX: check sign promotion.

return pointer to the first free byte. for the current implementation: the address <addr> of any allocated block satisfies: assert(<addr> < kmalloc_he

skip spaces? sometimes we get a \r\n sometimes a \n\r

read and echo the characters from the usbtty until it closes (pi rebooted) or we see a string indicating a clean shutdown.

If we are using the trivial TYPE_0 R.N.G., just do the old linear congruential bit. Otherwise, we do our fancy trinomial stuff, which is the sa

send a string <msg> to the unix side to print. message format: [PRINT_STRING, strlen(msg), <msg>] DANGER DANGER DANGER!!! Be careful WHEN you call t

exit current thread.

fork the unix side bootloader code and return a file descriptor for communicating with the client. 1. create a pty and get fd. 2. fork/exec the client