Searched refs:emergency_write_str (Results 1 – 3 of 3) sorted by relevance
18 console::emergency_write_str,52 emergency_write_str("irq_current\n"); in irq_current()58 emergency_write_str("fiq_current\n"); in fiq_current()64 emergency_write_str("serr_current\n"); in serr_current()71 emergency_write_str("sync_lower\n"); in sync_lower()78 emergency_write_str("irq_lower\n"); in irq_lower()84 emergency_write_str("fiq_lower\n"); in fiq_lower()90 emergency_write_str("serr_lower\n"); in serr_lower()
58 pub fn emergency_write_str(s: &str) { in emergency_write_str() function100 () => ($crate::console::emergency_write_str("\n"));103 $crate::console::emergency_write_str("\n");
79 use vmbase::{console::emergency_write_str, power::reboot};82 emergency_write_str("sync_exception_current\n");96 Instead you can use `emergency_write_str` and `eprintln!`, which will re-initialize the UART every101 properly, `eprintln!` may hang. `emergency_write_str` may be more reliable as it seems to avoid102 any stack allocation. This is why the example above uses `emergency_write_str` first to ensure that