summaryrefslogtreecommitdiff
path: root/net/core/sock_reuseport.c
diff options
context:
space:
mode:
authorWaldemar Rymarkiewicz <ext.waldemar.rymarkiewicz@tieto.com>2017-01-27 19:52:19 +0200
committerKalle Valo <kvalo@qca.qualcomm.com>2017-01-27 21:28:55 +0200
commitf2593cb1b29185d38db706cbcbe22ed538720ae1 (patch)
tree22436d9a16f7c332a0afac53af743b5d59afd817 /net/core/sock_reuseport.c
parent1ad38fd719da87980480886f21130053c73007ac (diff)
ath10k: Search SMBIOS for OEM board file extension
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@tieto.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'net/core/sock_reuseport.c')
0 files changed, 0 insertions, 0 deletions