FBLOG: A Frame-Buffer Driver Just For Kernel Logs
Appearing this weekend on the Linux kernel mailing list was a new frame-buffer driver with the sole purpose of the "fblog" driver being for showing the kernel logs.
David Herrmann is the developer who has been trying to kill CONFIG_VT from the Linux kernel, a.k.a. virtual terminal support. Herrmann was responsible for developing KMSCOM, a DRM-based terminal emulator. Now his latest work on the VT-killing spree is fblog. This is just a frame-buffer driver for displaying kernel logs across all connected frame-buffers.
In David's mailing list message he describes fblog as "This driver simply writes the kernel log to all connected framebuffers. It works similar to fbcon but removes all the complexity of the virtual terminals. There is a sysfs attribute called "active" that allows to enable/disable fblog so user-space can start an xserver or similar. The main purpose is debugging kernel boot problems. Therefore, it is not optimized for speed and I tried keeping it simple. I splitted the patches into 10 small chunks to make review easier."
It's unsure at this point whether the kernel log frame-buffer driver, which is less than 1,000 lines of code, will be accepted to the mainline kernel.
David Herrmann is the developer who has been trying to kill CONFIG_VT from the Linux kernel, a.k.a. virtual terminal support. Herrmann was responsible for developing KMSCOM, a DRM-based terminal emulator. Now his latest work on the VT-killing spree is fblog. This is just a frame-buffer driver for displaying kernel logs across all connected frame-buffers.
In David's mailing list message he describes fblog as "This driver simply writes the kernel log to all connected framebuffers. It works similar to fbcon but removes all the complexity of the virtual terminals. There is a sysfs attribute called "active" that allows to enable/disable fblog so user-space can start an xserver or similar. The main purpose is debugging kernel boot problems. Therefore, it is not optimized for speed and I tried keeping it simple. I splitted the patches into 10 small chunks to make review easier."
It's unsure at this point whether the kernel log frame-buffer driver, which is less than 1,000 lines of code, will be accepted to the mainline kernel.
12 Comments