In general, hosted mode is assumed "by default" if the target
is not Xous. This allows packages to be built cleanly on command
lines that don't know to pass a --feature flag to specify a target.
However, an explicit "hosted" flag is still retained so that we
can confirm the build system intent. This saves us from the failure
mode that we thought we were building for target A, but accidentally
ommitted the flag, and instead we've been silently building for
"hosted" mode without any warning. The main consumer of the "hosted"
flag is now just the build.rs script inside of the utralib.
Look at `target_os` to determine whether to enter "hosted" mode or not.
If `target_os` is "xous", then the Xous standard library should default
to using builtin Rust libstd features.
If it is "xous", then we should instead use our arch-specific
implementations.
This enables third-party programs to directly use the `xous` crate
without specifying feature flags.
Signed-off-by: Sean Cross <sean@xobs.io>
the git release number on this is a lie. But, it also doesn't
matter since it's a test build. I just didn't want to bump the
whole OS package dependencies because I'm tweaking a non-deployed
configuration.
When we started this project, all Renode Litex modules were 8-bits, and
we had to custom-make a 32-bit timer module. However, in the interim,
upstream has grown a 32-bit variant of this timer. As of this writing,
this change was made two years ago.
Remove our custom variant and use the upstream version instead.
Signed-off-by: Sean Cross <sean@xobs.io>
Now that the peripherals are all namespaced, generate the repl files as
part of the build using this new convention.
Signed-off-by: Sean Cross <sean@xobs.io>
Give a "Betrusted" namespace to all of the peripherals. This will enable
us to upstream various modules without breaking compatibility with our
own versions of these peripherals.
Signed-off-by: Sean Cross <sean@xobs.io>
cargo debugging is so hard. If you're OK with it, I really would like gems like how to debug this code to be included as a comment in the source where you might look to fix such problems. Google turns up crap results when you try to search for these hints, and the results have been really unstable as well. I know such comments pollute the source code but it'll save a lot of time in the future trying to remember the trick to debug a tricky thing later on, I think.
We now use build flags to decide which version of utralib to use. This
makes `LAST_CONFIG` obsolete, since the version of utralib is decided
using a hash of build configs and build flags.
Signed-off-by: Sean Cross <sean@xobs.io>