saymrwulf/xous-core
1
0
Fork 0
mirror of https://github.com/saymrwulf/xous-core.git synced 2026-11-08 04:56:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
xous-core/services/spinor/Cargo.toml

43 lines
1.1 KiB
TOML
Raw Normal View History

push of spinor changes to validate l2cache
2021-07-04 16:08:58 +00:00
[package]
name = "spinor"
version = "0.1.0"
authors = ["bunnie <bunnie@kosagi.com>"]
edition = "2018"
description = "SPINOR ROM operations server"
fix #174
2022-06-10 13:36:53 +00:00
# Dependency versions enforced by Cargo.lock.
push of spinor changes to validate l2cache
2021-07-04 16:08:58 +00:00
[dependencies]
bump xous version
2023-01-17 16:02:46 +00:00
xous = "0.9.31"
log-server = { package = "xous-api-log", version = "0.1.26" }
ticktimer-server = { package = "xous-api-ticktimer", version = "0.9.26" }
xous-names = { package = "xous-api-names", version = "0.9.28" }
pin down versions and harmonize versions across servers Versions are pinned down to the minor number. Yes, this means that we don't automatically pull in features and bug updates from crates.io, but it also means we don't pull in new attack surfaces and code that hasn't been tested or reviewed. I'd like this process to be very deliberate and not automatic for Xous. The `rand` crate is almost pinned down to a single version, except for an odd dependency that's pulled in by hosted mode that depends on rand 0.8.4 via a subordinate dependency via the `tempfile` crate. Pondering if it's worth it to try and eliminate that, because the 0.8.4 version doesn't get compiled into any version that touches real hardware. It just makes it harder to analyze the Cargo.lock file, mostly. I think I'll leave it as-is.
2022-01-10 07:39:55 +00:00
log = "0.4.14"
bump xous version
2023-01-17 16:02:46 +00:00
susres = {package = "xous-api-susres", version = "0.9.26"}
stash commit to fix a bootloader issue
2021-07-13 14:28:46 +00:00
trng = { path = "../trng" }
pivot spinor implementation realizing some core assumptions were wrong, so, scrapping and restarting
2021-07-15 15:00:50 +00:00
com = { path = "../com" }
add some real-hardware tests for spinor writes definitely still bugs. need to sleep on it.
2021-07-17 18:36:31 +00:00
llio = { path = "../llio" }
stash commit to fix a bootloader issue
2021-07-13 14:28:46 +00:00
rkyv = {version = "0.4.3", default-features = false, features = ["const_generics"]}
bump xous version
2023-01-17 16:02:46 +00:00
xous-ipc = "0.9.31"
pin down versions and harmonize versions across servers Versions are pinned down to the minor number. Yes, this means that we don't automatically pull in features and bug updates from crates.io, but it also means we don't pull in new attack surfaces and code that hasn't been tested or reviewed. I'd like this process to be very deliberate and not automatic for Xous. The `rand` crate is almost pinned down to a single version, except for an odd dependency that's pulled in by hosted mode that depends on rand 0.8.4 via a subordinate dependency via the `tempfile` crate. Pondering if it's worth it to try and eliminate that, because the 0.8.4 version doesn't get compiled into any version that touches real hardware. It just makes it harder to analyze the Cargo.lock file, mostly. I think I'll leave it as-is.
2022-01-10 07:39:55 +00:00
num-derive = {version = "0.3.3", default-features = false}
num-traits = {version = "0.2.14", default-features = false}
push of spinor changes to validate l2cache
2021-07-04 16:08:58 +00:00
bump all revs due to SoC artifact update
2022-12-12 08:07:20 +00:00
utralib = { version = "0.1.13", optional = true, default-features = false }
push of spinor changes to validate l2cache
2021-07-04 16:08:58 +00:00
start of some basic tests
2021-07-17 09:12:23 +00:00
[dev-dependencies]
lazy_static = "1.4.0"
harmonize rand crate to 0.7.4 (version used by ed25519-dalek)
2022-01-10 07:03:23 +00:00
rand = "0.7.3"
start of some basic tests
2021-07-17 09:12:23 +00:00
push of spinor changes to validate l2cache
2021-07-04 16:08:58 +00:00
[features]
Remove xous-rs unused features The rationale is that xous-rs should have only architecture specific code, e.g.: riscv, arm, x86, etc. To make other crates that depend on it not specify the features. This could be useful when using xous-rs with `libstd` for example. Signed-off-by: Jean-Pierre De Jesus DIAZ <me@jeandudey.tech>
2022-10-25 11:29:02 +00:00
precursor = ["utralib/precursor"]
refactor utra target line to use explicit feature targets still need to rework the crate feature selection
2022-10-01 18:20:03 +00:00
hosted = ["utralib/hosted"]
Remove xous-rs unused features The rationale is that xous-rs should have only architecture specific code, e.g.: riscv, arm, x86, etc. To make other crates that depend on it not specify the features. This could be useful when using xous-rs with `libstd` for example. Signed-off-by: Jean-Pierre De Jesus DIAZ <me@jeandudey.tech>
2022-10-25 11:29:02 +00:00
renode = ["utralib/renode"]
make the extra buffer flush a feature, so we can experiment more easily
2022-10-19 15:42:19 +00:00
extra_flush = []
re-introduce extra flush to see if this fixes things
2022-10-20 20:24:45 +00:00
default = ["extra_flush"]
start of some basic tests
2021-07-17 09:12:23 +00:00
[lib]
test = true
[[bin]]
name = "spinor"
test = false
Reference in a new issue Copy permalink