summaryrefslogtreecommitdiff
path: root/drivers/net/wimax/i2400m/sdio.c
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-09-09 17:11:57 -0700
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-10-19 15:55:58 +0900
commit10607c86e163e3da8bdf58a934da7dd3a68dcb7c (patch)
treeae12d72aec61824697dee9d0b509ef37d02f49e3 /drivers/net/wimax/i2400m/sdio.c
parentbfc44187bbaeabf597be6566a24e8fa7d689b984 (diff)
wimax/i2400m: on firmware upload, select BCF header that matches device's request
Devices based on the i2400m emit a "barker" (32 bit unsigned) when they boot. This barker is used to select, in the firmware file image, which header should be used to process the rest of the file. This commit implements said support, completing the series started by previous commits. We modify the i2400m_fw_dnload() firmware loading path by adding a call to i2400m_bcf_hdr_find() [new function], in which the right BCF header [as listed in i2400m->fw_hdrs by i2400m_fw_check()] is located. Then this header is fed to i2400m_dnload_init() and i2400m_dnload_finalize(). The changes to i2400m_dnload_finalize() are smaller than they look; they add the bcf_hdr argument and use that instead of bcf. Likewise in i2400m_dnload_init(). Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'drivers/net/wimax/i2400m/sdio.c')
0 files changed, 0 insertions, 0 deletions