U-Boot PCI BAR Mapping: The Helper Checks Host Windows, Not the BAR’s Own Size
A PCI register mapping returns a pointer, yet the requested register displacement is outside the endpoint’s BAR.
-
-
U-Boot EFI Measured Boot: A Full Event Log Can Leave PCR State Ahead of the Record
An EFI measurement operation reports that the event log is full.
-
U-Boot VirtIO Negotiation: Device Features Are Not the Driver’s Accepted Feature Set
A virtual machine advertises a storage feature, but U-Boot does not use it.
-
U-Boot Regulator Startup: A Voltage Range Does Not Select an Operating Point
A board description allows several output voltages, and the boot log says its regulator was enabled.
-
Linux Hardware Receive Timestamps: Qualify Packet Coverage Before Calculating Acquisition Latency
Qualify ordinary sensor-packet timestamp coverage, receive metadata and hardware-clock provenance before reporting acquisition latency on an embedded Linux gateway.
-
Yocto 5.0.8 Test Exports for Hardware Labs: Keep Runner, Image and Metadata Together
Qualify a standalone Yocto test-export bundle against its actual runner, image metadata and target identity before using hardware-lab results for release acceptance.
-
Yocto Customer eSDK Delivery: Qualify Updates and Add-On Artifacts Beyond the Installer
Design the standalone customer eSDK handover around a versioned installer, a usable update tree, matching prebuilt add-ons and a recovery acceptance path.
-
Yocto IDE Remote Debugging: Trace the Launcher That Sets the Target Program Arguments
Why does changing args in a devtool-generated VSCode launch.json leave the target program arguments unchanged, and why can starting the debug session also replace the target executable?
-
Yocto Upstream Version Checks: Distinguish an Undiscovered Release from an Up-to-Date Recipe
Why does devtool fail to identify a known upstream release, or report UNKNOWN rather than a usable upgrade, while the existing recipe still fetches and builds successfully?
-
Yocto devtool deploy-target: Supply Runtime Dependencies Even When the Recipe Declares Them Correctly
Why does an application deployed with devtool fail to find a shared library that its Yocto recipe correctly declares and packages?
