Laptop Hub
A laptop guide for integrated components, docking relationships, wireless paths, input hardware, selection, and lifecycle states.
Treat the laptop as a collection
The laptop lifecycle page frames a portable computer as a set of integrated components, platform relationships, records, and runtime interfaces. A model name identifies the enclosure or product family; it does not replace the records for the keyboard, touchpad, radio, graphics function, or storage path. The model is not every component. The guide narrows those subjects rather than blending them.
This matters when one physical system contains several kinds of hardware. Integration has limits. A built-in touchpad can remain present while a dock adds a display, keyboard, and wired network path. Those relationships have different identities and transports, even though a single laptop label appears in each description.
Follow wireless, input, and docking
The Wi-Fi and network pages connect an adapter, radio, firmware, interface, power relationship, link, and host record. Keyboard-identification and keyboard-lifecycle pages do the equivalent for reports, class behavior, selection, replacement, and retained associations. Docks add interfaces. Those paths diverge. Keyboard-touchpad and touchpad-state pages keep two nearby input functions from becoming one generic control device.
Consider a USB-C dock carrying an external screen, keyboard, and wired network connection. The screen follows a visual path; the keyboard sends input reports; the socket exposes another interface. Links change. Removing the dock changes those external relationships but does not remove the integrated touchpad. This concrete contrast is why “laptop state” needs a more specific owner.
Distinguish selection from active state
The selection-lifecycle page describes declarations, matching, ranking, staging, and activation for integrated components. Compatibility and version identity supply evidence about a record, while update-state distinguishes candidate, selected, active, and retained relationships. State needs an owner. These states can coexist in a timeline; none is a recipe for changing the portable system.
Use the computer guide for USB, audio, keyboard, mouse, and network architecture. Use display or audio when the question belongs to a visual or sound path. Identity is narrower. States differ. The laptop hub provides the boundary between those families and the integrated system, so a related link adds context without rewriting another component’s explanation.
- Laptop driver lifecycle reference — How laptop hardware identity, platform components, package records, and runtime interfaces change across a device lifecycle.
- Laptop driver package selection and lifecycle — How laptop package declarations, matching, ranking, staging, and activation relate across integrated components.
- Laptop driver update state reference — A vocabulary for candidate packages, selected components, runtime activation, and retained records on a laptop.
- Laptop Wi-Fi and network driver reference — The adapter, radio, firmware, network interface, and package layers behind laptop wireless connectivity.
- Laptop Wi-Fi package lifecycle — How a laptop wireless package describes adapters, platform integration, radio relationships, and runtime interfaces.
- Laptop network-adapter lifecycle reference — The device, interface, package, power, and link states that describe a laptop network adapter lifecycle.
- Laptop Wi-Fi post-update state reference — How wireless package, interface, radio, firmware, and link records can differ after a package transition.
- Laptop keyboard and touchpad driver reference — How internal input devices, embedded controllers, HID reports, class layers, and platform services meet in a laptop.
- Laptop keyboard-driver identification reference — How to distinguish a laptop keyboard’s physical surface, controller, interface, package, and logical input identity.
- Laptop keyboard package lifecycle — The package, report, class, service, and platform layers that can participate in an internal keyboard lifecycle.
- Laptop keyboard post-update state reference — How keyboard package records, input interfaces, platform services, and logical events can differ after a transition.
- Laptop touchpad driver state reference — A conceptual map of touchpad reports, controller identity, gesture layers, and host-software pointer state.
- Laptop driver state reference — A shared vocabulary for laptop device presence, package selection, runtime activation, power, and interface exposure.
- Laptop device-detection state reference — How laptop buses, firmware, identifiers, package matching, and interface publication define device-detection states.
- Laptop driver version identity reference — How laptop package, file, firmware, service, and platform version fields should be read by owner and scope.
- Laptop driver rollback lifecycle reference — How rollback relates to retained package records, device selection, platform components, and runtime state on a laptop.
- Laptop driver compatibility reference — How laptop platform design, device identifiers, package declarations, firmware, architecture, and interfaces establish compatibility.
- Laptop driver update decision reference — How to describe a laptop driver transition by component scope, platform identity, package declarations, and dependent runtime records.
- Laptop Wi-Fi package replacement lifecycle reference — How a laptop Wi-Fi package replacement relates to adapter identity, retained records, firmware, radio state, and network-interface exposure.