thunderbolt: Do not fail if DROM data CRC32 is invalid
There are devices out there where CRC32 of the DROM is not correct. One reason for this is that the ICM firmware does not validate it and it seems that neither does the Apple driver. To be able to support such devices we continue parsing the DROM contents regardless of whether CRC32 failed or not. We still keep the warning there. Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Reviewed-by: Yehezkel Bernat <yehezkel.bernat@intel.com> Reviewed-by: Michael Jamet <michael.jamet@intel.com> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Andreas Noever <andreas.noever@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
f53e767604
commit
3902294555
|
@ -485,9 +485,8 @@ parse:
|
||||||
crc = tb_crc32(sw->drom + TB_DROM_DATA_START, header->data_len);
|
crc = tb_crc32(sw->drom + TB_DROM_DATA_START, header->data_len);
|
||||||
if (crc != header->data_crc32) {
|
if (crc != header->data_crc32) {
|
||||||
tb_sw_warn(sw,
|
tb_sw_warn(sw,
|
||||||
"drom data crc32 mismatch (expected: %#x, got: %#x), aborting\n",
|
"drom data crc32 mismatch (expected: %#x, got: %#x), continuing\n",
|
||||||
header->data_crc32, crc);
|
header->data_crc32, crc);
|
||||||
goto err;
|
|
||||||
}
|
}
|
||||||
|
|
||||||
if (header->device_rom_revision > 2)
|
if (header->device_rom_revision > 2)
|
||||||
|
|
Loading…
Reference in New Issue