32742e6158
The i2400m based devices can boot two main types of firmware images: signed and non-signed. Signed images have signature data included that must match that of a certificate stored in the device. Currently the code is making the decission on what type of firmware load (signed vs non-signed) is going to be loaded based on a hardcoded decission in __i2400m_ack_verify(), based on the barker the device sent upon boot. This is not flexible enough as future hardware will emit more barkers; thus the bit has to be set in a place where there is better knowledge of what is going on. This will be done in follow-up commits -- however this patch paves the way for it. So the querying of the mode is packed into i2400m_boot_is_signed(); the main changes are just using i2400m_boot_is_signed() to determine the method to follow and setting i2400m->sboot in i2400m_is_boot_barker(). The modifications in i2400m_dnload_init() and i2400m_dnload_finalize() are just reorganizing the order of the if blocks and thus look larger than they really are. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| control.c | ||
| debug-levels.h | ||
| debugfs.c | ||
| driver.c | ||
| fw.c | ||
| i2400m-sdio.h | ||
| i2400m-usb.h | ||
| i2400m.h | ||
| netdev.c | ||
| op-rfkill.c | ||
| rx.c | ||
| sdio-debug-levels.h | ||
| sdio-fw.c | ||
| sdio-rx.c | ||
| sdio-tx.c | ||
| sdio.c | ||
| sysfs.c | ||
| tx.c | ||
| usb-debug-levels.h | ||
| usb-fw.c | ||
| usb-notif.c | ||
| usb-rx.c | ||
| usb-tx.c | ||
| usb.c | ||