device_manager: Move init_node_tree to after kdl cmd registration
This helps when debugging, since when a driver/module causes a crash while registering with the device manager, you can actually look at the device manager state ;-)
This commit is contained in:
parent
102ce4652a
commit
dfa5aa0c98
@ -2280,7 +2280,6 @@ device_manager_init(struct kernel_args* args)
|
||||
dm_init_io_resources();
|
||||
|
||||
recursive_lock_init(&sLock, "device manager");
|
||||
init_node_tree();
|
||||
|
||||
register_generic_syscall(DEVICE_MANAGER_SYSCALLS, control_device_manager,
|
||||
1, 0);
|
||||
@ -2300,6 +2299,9 @@ device_manager_init(struct kernel_args* args)
|
||||
"dump an I/O operation");
|
||||
add_debugger_command("io_buffer", &dump_io_buffer, "dump an I/O buffer");
|
||||
add_debugger_command("dma_buffer", &dump_dma_buffer, "dump a DMA buffer");
|
||||
|
||||
init_node_tree();
|
||||
|
||||
return B_OK;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user