Waldemar Rymarkiewicz <ext.waldemar.rymarkiewicz@xxxxxxxxx> wrote: > Board Data File (BDF) is loaded upon driver boot-up procedure. The right > board data file is identified, among others, by device and sybsystem ids. > > The problem, however, can occur when the (default) board data file cannot > fulfill with the vendor requirements and it is necessary to use a different > board data file. > > To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name > Extension to specify the extension/variant name. The driver will take the > extension suffix into consideration and will load the right (non-default) > board data file if necessary. > > If it is unnecessary to use extension board data file, please leave the > SMBIOS field blank and default configuration will be used. > > Example: > If a default board data file for a specific board is identified by a string > "bus=pci,vendor=168c,device=003e,subsystem-vendor=1028, > subsystem-device=0310" > then the OEM specific data file, if used, could be identified by variant > suffix: > "bus=pci,vendor=168c,device=003e,subsystem-vendor=1028, > subsystem-device=0310,variant=DE_1AB" > > Signed-off-by: Waldemar Rymarkiewicz <ext.waldemar.rymarkiewicz@xxxxxxxxx> Patch applied to ath-next branch of ath.git, thanks. f2593cb1b291 ath10k: Search SMBIOS for OEM board file extension -- https://patchwork.kernel.org/patch/9521307/ Documentation about submitting wireless patches and checking status from patchwork: https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
