From 5f5e3a2ada0e12cecb0b3a52a76ec384a30f06da Mon Sep 17 00:00:00 2001 From: bunnie Date: Sun, 21 May 2023 17:19:45 +0800 Subject: [PATCH] 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. --- services/spinor/src/main.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/services/spinor/src/main.rs b/services/spinor/src/main.rs index 4d186a1ce..5e6b6264f 100644 --- a/services/spinor/src/main.rs +++ b/services/spinor/src/main.rs @@ -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");