~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/firmware/lookup-order.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/driver-api/firmware/lookup-order.rst (Architecture m68k) and /Documentation/driver-api/firmware/lookup-order.rst (Architecture alpha)


  1 =====================                               1 =====================
  2 Firmware lookup order                               2 Firmware lookup order
  3 =====================                               3 =====================
  4                                                     4 
  5 Different functionality is available to enable      5 Different functionality is available to enable firmware to be found.
  6 Below is chronological order of how firmware w      6 Below is chronological order of how firmware will be looked for once
  7 a driver issues a firmware API call.                7 a driver issues a firmware API call.
  8                                                     8 
  9 * The ''Built-in firmware'' is checked first,       9 * The ''Built-in firmware'' is checked first, if the firmware is present we
 10   return it immediately                            10   return it immediately
 11 * The ''Firmware cache'' is looked at next. If     11 * The ''Firmware cache'' is looked at next. If the firmware is found we
 12   return it immediately                            12   return it immediately
 13 * The ''Direct filesystem lookup'' is performe     13 * The ''Direct filesystem lookup'' is performed next, if found we
 14   return it immediately                            14   return it immediately
 15 * The ''Platform firmware fallback'' is perfor     15 * The ''Platform firmware fallback'' is performed next, but only when
 16   firmware_request_platform() is used, if foun     16   firmware_request_platform() is used, if found we return it immediately
 17 * If no firmware has been found and the fallba     17 * If no firmware has been found and the fallback mechanism was enabled
 18   the sysfs interface is created. After this e     18   the sysfs interface is created. After this either a kobject uevent
 19   is issued or the custom firmware loading is      19   is issued or the custom firmware loading is relied upon for firmware
 20   loading up to the timeout value.                 20   loading up to the timeout value.
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php