On Thu, Feb 12, 2015 at 6:27 PM, Larry Finger <Larry.Finger@xxxxxxxxxxxx> wrote:
>> +#define RTL_EPATCH_SIGNATURE "Realtech"
>
>
> Typo here. It should be Realtek.
If it is a typo, it is a typo from Realtek :)
The firmware includes this signature and it is what the vendor code checks for.
const uint8_t RTK_EPATCH_SIGNATURE[8] = {0x52, 0x65, 0x61, 0x6C, 0x74,
0x65, 0x63, 0x68};
>> +#define RTL_ROM_LMP_3499 0x3499
>> +#define RTL_ROM_LMP_8723A 0x1200
>> +#define RTL_ROM_LMP_8723B 0x8723
>> +#define RTL_ROM_LMP_8821A 0x8821
>> +#define RTL_ROM_LMP_8761A 0x8761
>
>
> I just got a report for an lmp_subversion of 0x4ce1 on an RTL8723BE. The
> above list and the table below may need expanding. We are still testing.
Keep in mind, it is normal for the lmp_subversion to change once the
firmware has been uploaded.
That list is only a list of firmware versions that must be replaced.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
