Ryan O'Leary

I saw a blog post recently about this: https://adventures.michaelfbryan.com/posts/deserializing-binary-data-files/

With the `core` library alone, is there a non-`unsafe` way to convert a `&[u8]` to a `repr(C)` struct?

https://stackoverflow.com/questions/53670348/can-rusts-clippy-do-autocorrection-autofix shows multiple possibly ways to auto fix clippy issues. Perhaps: ``` First you need to install clippy nightly (rustup component add clippy --toolchain nightly-x86_64-unknown-linux-gnu), and after that run it...

This seemed to work for me: ``` diff --git a/Makefile b/Makefile index 88c99cda0c..40a269d3e9 100644 --- a/Makefile +++ b/Makefile @@ -116,7 +116,7 @@ BROKEN_CRATES_TO_CLIPPY := \ # TODO: Remove write_with_newline CRATES_TO_CLIPPY...

I imagine it would be in the payloader stage. You can see how coreboot does it here: https://github.com/coreboot/coreboot/blob/master/Documentation/cbfs.txt#L211

Yes, that sounds right. A simple CRC checksum would do (ex: https://crates.io/crates/crc). Nothing cryptographic is needed.

Just for the record, what kernel version is your image and which version of Ubuntu and Ubuntu's kernel? Sometimes when you don't see any prints, it's because the kernel doesn't...

I think it might be too late to re-license since most the code was contributed under a GPL license or ported from Coreboot.

I feel a good solution would be to have a `Console` Driver which re-writes the text passed through it. This driver would wrap the existing serial driver. Whenever a '\n'...

@sphinxc0re I set you as the assignee since you had a bunch of ideas on this topic.