arch/parisc/kernel/hardware.c
Source file repositories/reference/linux-study-clean/arch/parisc/kernel/hardware.c
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/kernel/hardware.c- Extension
.c- Size
- 77470 bytes
- Lines
- 1375
- Domain
- Architecture Layer
- Bucket
- arch/parisc
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/hardware.hlinux/stddef.hlinux/kernel.hlinux/init.h
Detected Declarations
function parisc_hardware_descriptionfunction parisc_get_cpu_type
Annotated Snippet
switch (id->sversion) {
case 0x0D: return "MUX port";
case 0x0E: return "RS-232 port";
}
break;
case HPHW_MEMORY:
return "Memory";
}
return "unknown device";
}
/* Interpret hversion (ret[0]) from PDC_MODEL(4)/PDC_MODEL_INFO(0) */
enum cpu_type __init
parisc_get_cpu_type(unsigned long hversion)
{
struct hp_cpu_type_mask *ptr;
unsigned short model = ((unsigned short) (hversion)) >> 4;
for (ptr = hp_cpu_type_mask_list; 0 != ptr->mask; ptr++) {
if (ptr->model == (model & ptr->mask))
return ptr->cpu;
}
panic("could not identify CPU type\n");
return pcx; /* not reached: */
}
Annotation
- Immediate include surface: `asm/hardware.h`, `linux/stddef.h`, `linux/kernel.h`, `linux/init.h`.
- Detected declarations: `function parisc_hardware_description`, `function parisc_get_cpu_type`.
- Atlas domain: Architecture Layer / arch/parisc.
- 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.