Skip to content

Commit 5b8f85d

Browse files
jlawrynoJonathan Corbet
authored andcommitted
docs: driver-api: firmware: clarify userspace requirements
The guidelines mention that firmware updates can't break the kernel, but it doesn't state directly that they can't break userspace programs. Make it explicit that firmware updates cannot break UAPI. Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com> Acked-by: Dave Airlie <airlied@redhat.com> [jc: fixed "no trailing newline"] Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250314100137.2972355-1-jacek.lawrynowicz@linux.intel.com
1 parent 4e6b714 commit 5b8f85d

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

Documentation/driver-api/firmware/firmware-usage-guidelines.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,8 @@ then of course these rules will not apply strictly.)
4242
deprecating old major versions, then this should only be done as a
4343
last option, and be stated clearly in all communications.
4444

45+
* Firmware files that affect the User API (UAPI) shall not introduce
46+
changes that break existing userspace programs. Updates to such firmware
47+
must ensure backward compatibility with existing userspace applications.
48+
This includes maintaining consistent interfaces and behaviors that
49+
userspace programs rely on.

0 commit comments

Comments
 (0)