mlockall on Embedded Linux: Budget Future Heap and Stack Growth Before Enabling MCL_FUTURE
Why can adding MCL_FUTURE make later allocations fail or stack growth fault while the device still has free RAM?
-
-
Linux UIO Mapping Offsets: Select the Region Before Adding the Device Byte Offset
Why can using a physical register address as mmap offset select the wrong UIO map or fail even when the advertised device region exists?
-
ALSA PCM Recovery on Embedded Linux: Distinguish an XRUN from a Suspended Stream
Why does snd_pcm_recover take a different path for EPIPE and ESTRPIPE, and what must an audio service still decide after it returns success?
-
udev Device Events: Start Long-Running Acquisition in a Service, Not a RUN Child
Why does a background acquisition helper launched by a udev RUN rule disappear after the device event finishes, and when is SYSTEMD_WANTS actually acted on?
-
systemd Socket Activation: Preserve the Listener Across an Embedded Service Restart
Why can a device daemon break later activations by calling shutdown on the listening socket it inherited from systemd?
-
Linux Type-B Multitouch: Track Contact Identity Separately from the Slot Number
Why can a two-finger evdev reader move the wrong contact when it treats ABS_MT_SLOT as a permanent finger identifier or clears unchanged coordinates every frame?
-
V4L2 Multi-Planar Capture: Separate Memory Planes from YUV Color Planes
Why does an NV12 frame contain luma and chroma planes while its V4L2 buffer description can still use one contiguous memory allocation?
-
RISC-V OpenSBI Ports: Map Device-Tree Hart IDs to Dense Runtime Indices
Trace OpenSBI v1.9 CPU identity from enabled device-tree nodes through dense scratch indices and independently ordered PLIC contexts during a platform migration.
-
RISC-V OpenSBI FW_DYNAMIC: Pass Next-Stage Information Through the Correct Handoff ABI
Diagnose OpenSBI FW_DYNAMIC handoff failures through a2, target-width information layout, early assembly checks and preferred-boot-hart relocation policy.
-
RISC-V Secondary-Hart Startup: Treat SBI HSM Success as an Asynchronous Transition
Integrate SBI secondary-hart startup through asynchronous HSM states, physical entry and unspecified-register handling, with a separate runtime-ready handshake.
