UART flushing may use hardware implemented flag about rust-raspberrypi-os-tutorials HOT 6 CLOSED

Hmm interesting. This somehow escaped me until now, and it would be an awesome improvement.

I‘ll check it out.
did you give it a try already?

Thanks!

from rust-raspberrypi-os-tutorials.

I did try it, and the UART output is as expected (in the 06_drivers_gpio_uart tutorial).
However it doesn't seems to me to be a good test case, since we check if the UART was flushed just after the first time we started it. But I don't know how to make a "good" test of this function.

from rust-raspberrypi-os-tutorials.

Tutorial 12 can be abused as a test. If the UART is not flushed first during its init(), some characters of the output in the main file are swallowed by the exception dump (which makes use of the panic-console that re-inits the UART).

Works only on the real device though, not QEMU.
Anyways, I’ll test and implement it once I find some time to do so.

from rust-raspberrypi-os-tutorials.

I can to that of you want, I've got plenty of time. I'd be really happy to contribute. I've never done this before, but I read the GitHub tutorial, so I think that I should do a pull request, of course if that's what you want and how it works. I can also make your test on tutorial 12, unless you want to check it by your self.

Hoping to help.

from rust-raspberrypi-os-tutorials.

Thanks for the offer!
Regarding pull request, I am in the middle of a refactoring of some tutorial code, so I would want to defer any changes until the refactor is done.

Just checking if it works as the documentation suggests would be enough for the time being, and we can do the PR later 👍

from rust-raspberrypi-os-tutorials.

Ok 👍

from rust-raspberrypi-os-tutorials.