- swap works on hardware (at least reading in the encrypted
images works)
- renode version is deliberately configured to trigger an edge
case in the swapper, and is broken -- to be debugged
Haven't dug into it, but the AES instruction is not working
correctly in MPW cramium target silicon. There isn't a great way
to selectively disable hardware acceleration for sub-targets of
patched crates. So, as a work-around, we use xtask to patch
the default arguments of the AES crate, just for cramium-soc
targets, to use software emulated AES. This allows us to move
on with bring-up. To wit, there is another AES accelerator
on-chip that could be much faster than RV32 AES acceleration
(and with better DPA characteristics), and to use that option,
we might have to use a patch like this anyways, because Rust
doesn't have a good way to pass feature flags through patched
crates like this.
its arguments require the 0x decorator to define hex,
whereas arguments to xtask don't. A little confusing, but
only if you actually ever call create-image -- which nobody
does, to a first order.
This is the weirdest damn thing. All the crates say 0.4.19 as
the chrono version, but the actual version in the lockfile
is 0.4.33. And there isn't an error about it?
Anyways, this update the pins to reflect what's in the lockfile.
The kernel and loader may need to use a different target, particularly
in the case of Precursor where the kernel and loader need an OS of
`none`.
Signed-off-by: Sean Cross <sean@xobs.io>
The problem is the original way of specifying crates for remote
download is the same that Rust uses to specify a version of a crate
(e.g. the @ symbol), and so I could not differentiate between the
two cases.
Switch to using a ^ symbol for remote download crates. Hopefully
that doesn't have conflicts??
this has become necessary because with the inclusion of a version
number in a crate name, rustc always consults the on-line index on
every build (even when it's not necessary), which can double the
build time. Using --offline reduces that thrashing.
this is because we are keeping an older version around
for a legacy ed25519 depedency, so we have to fully
specify which sha2 we want build as our server
