don't monitor connection count on spinor block during hosted mode

this makes it a little more flexible to do diagnostics/debugging
in hosted mode. It's not secure, but hosted mode is not meant to be
secure.
This commit is contained in:
bunnie 2023-05-21 17:19:45 +08:00
parent 3aeb360a18
commit 5f5e3a2ada

View file

@ -765,7 +765,7 @@ fn main() -> ! {
#[cfg(any(feature="precursor", feature="renode"))]
let spinor_sid = xns.register_name(api::SERVER_NAME_SPINOR, Some(5)).expect("can't register server");
#[cfg(not(target_os = "xous"))]
let spinor_sid = xns.register_name(api::SERVER_NAME_SPINOR, Some(2)).expect("can't register server");
let spinor_sid = xns.register_name(api::SERVER_NAME_SPINOR, None).expect("can't register server"); // hosted mode we don't care about security of the spinor server
log::trace!("registered with NS -- {:?}", spinor_sid);
let handler_conn = xous::connect(spinor_sid).expect("couldn't create interrupt handler callback connection");