mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
synced 2026-11-01 23:04:54 +01:00
Dave Airlie
321eaf317d
A recent snafu where Intel ignored upstream feedback on a firmware change, led to a late rc6 fix being required. In order to avoid this in the future we should document some expectations around linux-firmware. I was originally going to write this for drm, but it seems quite generic advice. v2: rewritten with suggestions from Thorsten Leemhuis v3: rewritten with suggestions from Mauro Acked-by: Luis Chamberlain <[email protected]> Acked-by: Rodrigo Vivi <[email protected]> Acked-by: Daniel Vetter <[email protected]> Acked-by: Harry Wentland <[email protected]> Signed-off-by: Dave Airlie <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
18 lines
336 B
ReStructuredText
18 lines
336 B
ReStructuredText
==========================
|
|
Firmware API core features
|
|
==========================
|
|
|
|
The firmware API has a rich set of core features available. This section
|
|
documents these features.
|
|
|
|
.. toctree::
|
|
|
|
fw_search_path
|
|
built-in-fw
|
|
firmware_cache
|
|
direct-fs-lookup
|
|
fallback-mechanisms
|
|
lookup-order
|
|
firmware-usage-guidelines
|
|
|