Commit graph

10340 commits

Author SHA1 Message Date
bunnie
1352e3f3df add a tiny target; testing some minimal builds 2022-10-02 21:50:05 +08:00
bunnie
33940aceb2 remove false dependency 2022-10-02 21:46:24 +08:00
bunnie
18e1d6e867 switch over to the log uart on boot
this helps minimal configurations to be more useful without pulling
in com/llio crates. The trade-off is that KP's early in boot
(or during resume) are not visible, but, these are (thankfully??)
less rare these days.
2022-10-02 21:45:36 +08:00
bunnie
4b293420c3 update utralib lockfile 2022-10-02 19:03:49 +08:00
bunnie
a303150687 fix kernel test build in hosted-ci 2022-10-02 17:56:51 +08:00
bunnie
b431059715 add hosted-ci target back in 2022-10-02 17:52:30 +08:00
bunnie
b4febb78ff convert all build targets to the new builder format
also organize the build targets and document what they do better.
remove bitrotted targets.
remove legacy frameworks.
2022-10-02 17:32:48 +08:00
bunnie
b1c3a70f35 cleanup bitrot in usb-test 2022-10-02 14:51:02 +08:00
bunnie
8340c65dfe fixup some comments 2022-10-02 03:00:52 +08:00
bunnie
0979a205c6 add the precursor feature flag to rust-analyzer 2022-10-02 03:00:28 +08:00
bunnie
4e40ae6c5d move from target selectors to feature selectors for back-ends
This will allow for e.g. xous on riscv32-imac but not a precursor
target, for example: by using feature selectors we get to have
a bigger range of targets that we support, such as for implementations
that haven't been upstreamed or have official target-triples.

The downsides are:

- patch override libraries don't absorb feature flags. so, for
example, the AES crate that is used to patch other crates won't
be aware of the target features without modifying the referencing
crates.

- features are normally meant to be additive, but target features
are mutually exclusive. The mutex is enforced by a check in
utralib that throws a panic on build if two targets are accidentally
selected at the same time.
2022-10-02 02:56:44 +08:00
bunnie
366434b015 initial cut at a refactored build process.
built renode, hosted, tts, app-image targets successfully.

now to finish porting over all the legacy targets and then
removing the old build method
2022-10-02 02:21:48 +08:00
bunnie
d699ddf998 also move utralib change into kernel, update cargo.lock 2022-10-02 02:21:27 +08:00
bunnie
776a47f4bc missed a file 2022-10-02 02:21:06 +08:00
bunnie
fb29c9b2c1 refactor utra target line to use explicit feature targets
still need to rework the crate feature selection
2022-10-02 02:20:03 +08:00
Gianguido Sorà
89f5d568ff root-keys: gracefully handle cases
where gateware signature is malformed, invalid public key or
signature type
2022-09-30 15:17:38 +02:00
bunnie
50d5a94270 this file wasn't saved for some reason 2022-09-29 22:38:12 +08:00
bunnie
e2d941e3b4 remove clap from svd2repl 2022-09-29 22:31:50 +08:00
bunnie
df96605531 update utralib reference 2022-09-29 22:22:33 +08:00
bunnie
3ff1b66d2f absorb svd2utra rev 2022-09-29 22:16:24 +08:00
bunnie
ee522c69a7 bump rev to remove clap 2022-09-29 22:15:22 +08:00
bunnie
7226b57a2f eliminate an instance of clap 2022-09-29 22:12:58 +08:00
bunnie
8af0ef7961 split xtask into file modules 2022-09-29 19:05:24 +08:00
bunnie
884e19b9de clean up an error 2022-09-28 01:35:19 +08:00
bunnie
96300db925 add license to kernel Cargo.toml 2022-09-27 18:43:39 +08:00
bunnie
f053fdb6cd note gdbstub removal 2022-09-27 18:43:27 +08:00
bunnie
b9dc7ccab5 bump release notes 2022-09-27 18:41:35 +08:00
bunnie
be0c503e1f bump lockfile 2022-09-27 18:32:36 +08:00
bunnie
878c822d9f fix renode paths 2022-09-27 18:32:30 +08:00
bunnie
c9f3d6a3d5 bump utralib ref in kernel so it works with the renode target 2022-09-27 18:32:04 +08:00
bunnie
cdd01de33e update path to renode target 2022-09-27 18:31:50 +08:00
bunnie
8e86b58f06 add renode artifacts 2022-09-27 18:31:28 +08:00
bunnie
e65884cf77 start cleanup on renode build 2022-09-27 18:10:15 +08:00
bunnie
d0dc2e2a9f add renode as a target to utralib 2022-09-27 18:09:33 +08:00
bunnie
4f2506f009 some housekeeping; remove bit-rotted test targets
these targets are so old they would need to be completely
re-written to be relevant, so just cull them.
2022-09-27 17:50:32 +08:00
bunnie
44cc459b33 fix hosted mode 2022-09-27 17:35:38 +08:00
bunnie
ab940e18db fixup warnings 2022-09-27 17:27:21 +08:00
bunnie
320a8e2b32 prep a fork of riscv package
for now, publish a xous-riscv package, until we can absorb
this into the kernel directly.

Want to recode all the assembly files into inline-assembly now
that it is supported in Rust, but, let's not put that yak on
the list of yaks to shave before we have a separable kernel.
2022-09-27 17:23:25 +08:00
bunnie
755556611c prep kernel for packaging
- strip out gdb-stub. Per xobs, the feature never worked, and it
depends upon a branch of a git repo which is not allowed by crates.io
Since the feature hasn't been developed, and crates.io will not
allow even an optional feature that points to a git repo, the feature
was stripped out.

- rename "kernel" to "xous-kernel", so that we can live in a crates.io
package namespace that is specific to Xous.

still have to figure out the riscv package issue.
2022-09-27 17:02:20 +08:00
bunnie
4f7f5855ec add the generated.rs top file which routes to specific configs with feature flags 2022-09-27 16:32:40 +08:00
bunnie
0cfc09f523 stop ignoring the generated files
generated files are now committed to tracked repo history
2022-09-27 16:32:15 +08:00
bunnie
be7b77e52a bump lockfile 2022-09-27 16:31:05 +08:00
bunnie
b97a2f7042 bump rev and update readme 2022-09-27 16:30:57 +08:00
bunnie
fad43a1e0f add target routing to build.rs 2022-09-27 16:30:45 +08:00
bunnie
e35dc90ce5 add specific targets so we can pass crates.io guidelines 2022-09-27 16:30:09 +08:00
bunnie
895957e53a pass the SVD config back to xtask
this is necessary because we need the full SVD path to generate
the whitelist of physical pages that can be addressed. Since the
SVD path is now domiciled in utralib, a file called "SVD_PATH"
is created in the target/ directory which contains the resolved
path to the SVD file given the abstract target/rev feature pair.
2022-09-27 15:12:28 +08:00
bunnie
a4c9dabd0f add description 2022-09-27 03:14:45 +08:00
bunnie
2f016c3876 handle case of a "clean" build without failure 2022-09-27 03:12:08 +08:00
bunnie
15bcb6328f fixup other refs 2022-09-27 03:09:41 +08:00
bunnie
3a6f69a4ad fix SVD spec toggle trigger
this fix makes it so that

1) you always get a correct build when the SVD spec is toggled
2) you don't always rebuild when nothing has changed

(2) is with the caveat that the no-change flag is only clean
after your second build (i.e. your third run will be fast).
I'm not quite sure why but I think it's because the "changes"
to the config file tracker are computed throughout the first
build and the second build still sees that file as recently
changed, so, it'll trigger a rebuild (could also just be
a race condition because the timestamp of the rebuild is
at the same second that the file was regenerated, so conservatively
you'd rebuild the next time).
2022-09-27 03:06:42 +08:00