Searched hist:f72d1684e521ba60da5fce8a71ae90494b960164 (Results 1 – 5 of 5) sorted by relevance
| /haiku/src/system/kernel/debug/ |
| H A D | blue_screen.h | f72d1684e521ba60da5fce8a71ae90494b960164 Wed Nov 20 02:35:31 UTC 2024 Augustin Cavalier <waddlesplash@gmail.com> kernel/debug: Initialize the frame buffer console much earlier, if possible.
Previously it was not initialized until "post-VM", but there are
a number of ways VM initialization can go wrong that it would
be nice to know about without needing a serial port.
On arches which map the whole physical memory into the kernel
address space (x86_64, at least), we can get the bluescreen facility
initialized using KERNEL_PMAP_BASE. On other architectures, we
just fail to init then, and do the usual setup later on.
A slight bit of extra code cleanup in blue_screen_init_early:
we now just call module->info.std_ops() rather than a
frame-buffer-console specific method.
|
| H A D | blue_screen.cpp | f72d1684e521ba60da5fce8a71ae90494b960164 Wed Nov 20 02:35:31 UTC 2024 Augustin Cavalier <waddlesplash@gmail.com> kernel/debug: Initialize the frame buffer console much earlier, if possible.
Previously it was not initialized until "post-VM", but there are
a number of ways VM initialization can go wrong that it would
be nice to know about without needing a serial port.
On arches which map the whole physical memory into the kernel
address space (x86_64, at least), we can get the bluescreen facility
initialized using KERNEL_PMAP_BASE. On other architectures, we
just fail to init then, and do the usual setup later on.
A slight bit of extra code cleanup in blue_screen_init_early:
we now just call module->info.std_ops() rather than a
frame-buffer-console specific method.
|
| H A D | frame_buffer_console.cpp | f72d1684e521ba60da5fce8a71ae90494b960164 Wed Nov 20 02:35:31 UTC 2024 Augustin Cavalier <waddlesplash@gmail.com> kernel/debug: Initialize the frame buffer console much earlier, if possible.
Previously it was not initialized until "post-VM", but there are
a number of ways VM initialization can go wrong that it would
be nice to know about without needing a serial port.
On arches which map the whole physical memory into the kernel
address space (x86_64, at least), we can get the bluescreen facility
initialized using KERNEL_PMAP_BASE. On other architectures, we
just fail to init then, and do the usual setup later on.
A slight bit of extra code cleanup in blue_screen_init_early:
we now just call module->info.std_ops() rather than a
frame-buffer-console specific method.
|
| H A D | debug.cpp | f72d1684e521ba60da5fce8a71ae90494b960164 Wed Nov 20 02:35:31 UTC 2024 Augustin Cavalier <waddlesplash@gmail.com> kernel/debug: Initialize the frame buffer console much earlier, if possible.
Previously it was not initialized until "post-VM", but there are
a number of ways VM initialization can go wrong that it would
be nice to know about without needing a serial port.
On arches which map the whole physical memory into the kernel
address space (x86_64, at least), we can get the bluescreen facility
initialized using KERNEL_PMAP_BASE. On other architectures, we
just fail to init then, and do the usual setup later on.
A slight bit of extra code cleanup in blue_screen_init_early:
we now just call module->info.std_ops() rather than a
frame-buffer-console specific method.
|
| /haiku/headers/private/kernel/ |
| H A D | frame_buffer_console.h | f72d1684e521ba60da5fce8a71ae90494b960164 Wed Nov 20 02:35:31 UTC 2024 Augustin Cavalier <waddlesplash@gmail.com> kernel/debug: Initialize the frame buffer console much earlier, if possible.
Previously it was not initialized until "post-VM", but there are
a number of ways VM initialization can go wrong that it would
be nice to know about without needing a serial port.
On arches which map the whole physical memory into the kernel
address space (x86_64, at least), we can get the bluescreen facility
initialized using KERNEL_PMAP_BASE. On other architectures, we
just fail to init then, and do the usual setup later on.
A slight bit of extra code cleanup in blue_screen_init_early:
we now just call module->info.std_ops() rather than a
frame-buffer-console specific method.
|