Peter Maydell writes:
> I'm not sure what we should do with EOF, but presumably
> we should handle it in some way.
There's no correct answer here, which is why the current implementation
just ignores it. Here are a couple of options:
1. Just return whatever getchar() provides; if it returns EO
On Thu, 9 Jan 2020 at 14:19, Alex Bennée wrote:
>
> From: Keith Packard
>
> Provides a blocking call to read a character from the console using
> semihosting.chardev, if specified. This takes some careful command
> line options to use stdio successfully as the serial ports, monitor
> and semihost
