adjust security parameters for dvt build

This commit is contained in:
bunnie 2022-12-08 17:19:05 +08:00
parent fc08c3e29d
commit 4dd983bfc4
2 changed files with 6 additions and 2 deletions

View file

@ -741,8 +741,10 @@ fn main() -> ! {
// - status sub system (for setting the layout, autobacklight feature)
// - USB (for getting layout)
// - Preference manager
#[cfg(any(feature="precursor", feature="renode"))]
#[cfg(all(any(feature="precursor", feature="renode"), not(feature="utralib/precursor-2753c12-dvt")))]
let kbd_sid = xns.register_name(api::SERVER_NAME_KBD, Some(5)).expect("can't register server");
#[cfg(all(any(feature="precursor", feature="renode"), feature="utralib/precursor-2753c12-dvt"))] // dvt build has less in it
let kbd_sid = xns.register_name(api::SERVER_NAME_KBD, Some(4)).expect("can't register server");
#[cfg(not(target_os = "xous"))]
let kbd_sid = xns.register_name(api::SERVER_NAME_KBD, Some(5)).expect("can't register server");
log::trace!("registered with NS -- {:?}", kbd_sid);

View file

@ -125,8 +125,10 @@ fn main() -> ! {
// - time server
// - llio
// I2C can be used to set time, which can have security implications; we are more strict on counting who can have access to this resource.
#[cfg(any(feature="precursor", feature="renode"))]
#[cfg(all(any(feature="precursor", feature="renode"), not(feature="utralib/precursor-2753c12-dvt")))]
let i2c_sid = xns.register_name(api::SERVER_NAME_I2C, Some(3)).expect("can't register I2C thread");
#[cfg(all(any(feature="precursor", feature="renode"), feature="utralib/precursor-2753c12-dvt"))] // dvt build has less in it
let i2c_sid = xns.register_name(api::SERVER_NAME_I2C, Some(2)).expect("can't register I2C thread");
#[cfg(not(target_os = "xous"))]
let i2c_sid = xns.register_name(api::SERVER_NAME_I2C, Some(1)).expect("can't register I2C thread");
log::trace!("registered I2C thread with NS -- {:?}", i2c_sid);