Block a user
consolidate all
write..file()
into config.py
and update zc706.py
to follow artiq repo
Now I'm thinking that since write_...
functions are shared between zc706 and kasli-soc, they could be just extracted into e.g. config.py
- but it's not a big deal if it isn't.
kasli_soc.py: change write_rustc_cfg_file() to follow artiq repo on release-7
Shouldn't this be applied to zc706 as well?
717848e022
rtio_mgt: remove support for async messages
1890e443d1
check subkernel exceptions only when awaited
f6ed2604e6
subkernel: port master support
615f2e3d37
remove misleading 'Actively' from docs at main.rs
Satellite: support subkernels
36d6d14e60
satellite: process kernel requests more often
58a73a7154
subkernel: send async statuses when requested
41100f62b9
satellite: support subkernels
c2672f5d55
libkernel -> ksupport
48d96b71f6
satellite gateware: add kernel rtio to cri
23cecc3081
rtio_mgt: remove support for async messages
312d0bfdf6
check subkernel exceptions only when awaited
8d5472e5cb
fix warning
9b48e6952d
libio: fix alloc feature
82c25030be
libkernel -> ksupport
afb33bdd11
satellite gateware: add kernel rtio to cri
Subkernels: port support for master
dae1a6b323
subkernel: port master support
37df7fd45b
cargo fmt
c9b574f5c7
flake: update dependencies
2ac7eedec1
firmware: fix compilation without virtual LEDs
c61017fbe6
fix compiling error when cfg has has_rtio_moninj
satellite: SYS CLK did not switch
A question I would rather have is why would the lock time differ between SD boot and netboot? It could be useful to know of any issues where things work in a developer (netboot) but suddenly break…
Turn off LED L3 only when all channels have no PID
channel ^ 1
while quick, would cause weird behavior if e.g. we create a new version of the thermostat with more than two channels and re-used the code.
use csr::virtual_leds for SFP0..3 LED indication
Could save a CSR call by getting the value before the if
use csr::virtual_leds for SFP0..3 LED indication
Doesn't it spam the UART logs? Seems could be removed