mirror of
https://github.com/subhobhai943/SUB-OS.git
synced 2026-10-25 16:52:29 +00:00
Boot logo (init/bootlogo.c, init/logo_data.c, scripts/mklogo.py): The logo appears in two forms because the framebuffer does not exist for the first third of boot. An ASCII rendition goes to the text console and serial line from the first moments; once the video driver is up at step [5/14] the real bitmap takes over as a graphical splash with a progress bar tied to the actual boot stages. The asset is 4-bit palette indexed, so 160x160 pixels cost 12.5 KB instead of 100 KB, and carries a transparency mask so the mark composites onto the gradient rather than stamping a flat rectangle over it. scripts/mklogo.py regenerates init/logo_data.c from the source PNG. Boot reaches the desktop in well under a second, so the splash is held for a minimum duration and the bar sweeps to 100% during the hold; without that the logo would flash past unseen. `splashtime=<ms>` tunes it and `nosplash`, `nogui` or `text` skip it. Bootloader (boot/stage2.asm): stage2 staged the whole kernel in conventional RAM before copying it to 1 MB, which capped the kernel at roughly 576 KB before the load ran into video memory at 0xA0000. The logo pushed it over that line and the kernel stopped booting. Each 32 KB chunk now goes into one fixed low buffer and is copied straight to its final address, using unreal mode for the 32-bit reach. The ceiling is now the image itself, 1.375 MB. Console font (lib/font8x8.c): fb_draw_char was a stub that ignored its character argument and drew a filled rectangle, which is why the splash rendered its text as solid blocks. It now renders real glyphs, and the table it uses is shared: the framebuffer console, the canvas rasterizer and the desktop compositor had three divergent private copies, two of which still carried the `// \` line-continuation defect. printk console sink (kernel/printk.c): printk output can be redirected to a callback, so a caller can run a subsystem that reports via printk and capture what it printed. Serial and the dmesg ring still see everything, which keeps a captured run debuggable. Shell builtins (userland/lazybox/shell.c): The builtin chain is extracted into shell_execute_builtin(), so the kernel TTY and the desktop terminal accept the same vocabulary instead of the GUI seeing only the applet table. Callers that cannot be suspended pass allow_blocking = false to refuse the animating ones. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01L5yKJT4Wo2cV3rfPrwY5MP
30 lines
1.0 KiB
C
30 lines
1.0 KiB
C
#ifndef _USERLAND_SHELL_H
|
|
#define _USERLAND_SHELL_H
|
|
|
|
#include <stdbool.h>
|
|
|
|
#define MAX_COMMAND_LENGTH 256
|
|
|
|
void shell_init(void);
|
|
void shell_run(void);
|
|
|
|
// Shared builtin dispatcher.
|
|
//
|
|
// Some commands (neofetch, calc, matrix, history, tty, ...) are shell builtins
|
|
// rather than LazyBox applets. Both the kernel TTY shell and the desktop
|
|
// terminal route through this so the two consoles accept the same vocabulary.
|
|
//
|
|
// `raw_cmd` is the untokenized line, which the argument-slurping builtins such
|
|
// as calc and hexdump need. Returns true if the command was recognised.
|
|
//
|
|
// `allow_blocking` is false for callers that must not be suspended -- the
|
|
// desktop compositor drives input from its own frame loop, so builtins that
|
|
// animate or wait for a key are refused there.
|
|
bool shell_execute_builtin(const char* raw_cmd, int argc, char** argv, bool allow_blocking);
|
|
|
|
// True when the name is a builtin, regardless of whether it can run here.
|
|
bool shell_is_builtin(const char* name);
|
|
bool shell_builtin_blocks(const char* name);
|
|
|
|
#endif // _USERLAND_SHELL_H
|