1*4882a593Smuzhiyun===================== 2*4882a593SmuzhiyunFirmware search paths 3*4882a593Smuzhiyun===================== 4*4882a593Smuzhiyun 5*4882a593SmuzhiyunThe following search paths are used to look for firmware on your 6*4882a593Smuzhiyunroot filesystem. 7*4882a593Smuzhiyun 8*4882a593Smuzhiyun* fw_path_para - module parameter - default is empty so this is ignored 9*4882a593Smuzhiyun* /lib/firmware/updates/UTS_RELEASE/ 10*4882a593Smuzhiyun* /lib/firmware/updates/ 11*4882a593Smuzhiyun* /lib/firmware/UTS_RELEASE/ 12*4882a593Smuzhiyun* /lib/firmware/ 13*4882a593Smuzhiyun 14*4882a593SmuzhiyunThe module parameter ''path'' can be passed to the firmware_class module 15*4882a593Smuzhiyunto activate the first optional custom fw_path_para. The custom path can 16*4882a593Smuzhiyunonly be up to 256 characters long. The kernel parameter passed would be: 17*4882a593Smuzhiyun 18*4882a593Smuzhiyun* 'firmware_class.path=$CUSTOMIZED_PATH' 19*4882a593Smuzhiyun 20*4882a593SmuzhiyunThere is an alternative to customize the path at run time after bootup, you 21*4882a593Smuzhiyuncan use the file: 22*4882a593Smuzhiyun 23*4882a593Smuzhiyun* /sys/module/firmware_class/parameters/path 24*4882a593Smuzhiyun 25*4882a593SmuzhiyunYou would echo into it your custom path and firmware requested will be 26*4882a593Smuzhiyunsearched for there first. 27