mirror of
https://github.com/SerenityOS/serenity
synced 2024-09-06 17:06:31 +00:00
20743e8aed
As we removed the support of VBE modesetting that was done by GRUB early on boot, we need to determine if we can modeset the resolution with our drivers, and if not, we should enable text mode and ensure that SystemServer knows about it too. Also, SystemServer should first check if there's a framebuffer device node, which is an indication that text mode was not even if it was requested. Then, if it doesn't find it, it should check what boot_mode argument the user specified (in case it's self-test). This way if we try to use bochs-display device (which is not VGA compatible) and request a text mode, it will not honor the request and will continue with graphical mode. Also try to print critical messages with mininum memory allocations possible. In LibVT, We make the implementation flexible for kernel-specific methods that are implemented in ConsoleImpl class.
21 lines
552 B
C++
21 lines
552 B
C++
/*
|
|
* Copyright (c) 2021, Andreas Kling <kling@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
namespace Kernel {
|
|
|
|
[[noreturn]] void __panic(const char* file, unsigned int line, const char* function);
|
|
|
|
#define PANIC(...) \
|
|
do { \
|
|
critical_dmesgln("KERNEL PANIC! :^("); \
|
|
critical_dmesgln(__VA_ARGS__); \
|
|
__panic(__FILE__, __LINE__, __PRETTY_FUNCTION__); \
|
|
} while (0)
|
|
|
|
}
|