arch/m68k/sun3/prom/printf.c
Source file repositories/reference/linux-study-clean/arch/m68k/sun3/prom/printf.c
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/sun3/prom/printf.c- Extension
.c- Size
- 975 bytes
- Lines
- 56
- Domain
- Architecture Layer
- Bucket
- arch/m68k
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
linux/kernel.hasm/openprom.hasm/oplib.h
Detected Declarations
function prom_printf
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* printf.c: Internal prom library printf facility.
*
* Copyright (C) 1995 David S. Miller (davem@caip.rutgers.edu)
*/
/* This routine is internal to the prom library, no one else should know
* about or use it! It's simple and smelly anyway....
*/
#include <linux/kernel.h>
#include <asm/openprom.h>
#include <asm/oplib.h>
#ifdef CONFIG_KGDB
extern int kgdb_initialized;
#endif
static char ppbuf[1024];
void
prom_printf(char *fmt, ...)
{
va_list args;
char ch, *bptr;
va_start(args, fmt);
#ifdef CONFIG_KGDB
ppbuf[0] = 'O';
vsnprintf(ppbuf + 1, sizeof(ppbuf) - 1, fmt, args);
#else
vsnprintf(ppbuf, sizeof(ppbuf), fmt, args);
#endif
bptr = ppbuf;
#ifdef CONFIG_KGDB
if (kgdb_initialized) {
pr_info("kgdb_initialized = %d\n", kgdb_initialized);
putpacket(bptr, 1);
} else
#else
while((ch = *(bptr++)) != 0) {
if(ch == '\n')
prom_putchar('\r');
prom_putchar(ch);
}
#endif
va_end(args);
return;
}
Annotation
- Immediate include surface: `linux/kernel.h`, `asm/openprom.h`, `asm/oplib.h`.
- Detected declarations: `function prom_printf`.
- Atlas domain: Architecture Layer / arch/m68k.
- 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.