include/linux/consolemap.h

File Facts

System

Linux kernel

Corpus path

include/linux/consolemap.h

Extension

.h

Size

1698 bytes

Lines

87

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct vc_data
• enum translation_map
• function inverse_translate
• function conv_uni_to_pc
• function conv_8bit_to_uni
• function conv_uni_to_8bit
• function console_map_init
• function ucs_is_zero_width
• function ucs_recompose
• function ucs_get_fallback

Annotated Snippet

static inline void console_map_init(void) { }

static inline bool ucs_is_double_width(uint32_t cp)
{
	return false;
}

static inline bool ucs_is_zero_width(uint32_t cp)
{
	return false;
}

static inline u32 ucs_recompose(u32 base, u32 mark)
{
	return 0;
}

static inline u32 ucs_get_fallback(u32 cp)
{
	return 0;
}
#endif /* CONFIG_CONSOLE_TRANSLATIONS */

#endif /* __LINUX_CONSOLEMAP_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct vc_data`, `enum translation_map`, `function inverse_translate`, `function conv_uni_to_pc`, `function conv_8bit_to_uni`, `function conv_uni_to_8bit`, `function console_map_init`, `function ucs_is_zero_width`, `function ucs_recompose`, `function ucs_get_fallback`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.