Need to match driver to microcode?
grarpamp at gmail.com
Wed Feb 5 23:34:46 EST 2014
On Wed, Feb 5, 2014 at 8:50 PM, Larry Finger <Larry.Finger at lwfinger.net> wrote:
> If you had one of the newer cores, then you needed newer firmware to get the
> correct file, but the older ones worked. However, I should never trust my
Correct my understanding... 'cores' refers to physical hardware
devices/revisions from Broadcom? So if I 'had newer cores', I'd need
to find newer 'firmware aka: microcode' to support them. Because
'older ones aka: firmware files' would not in fact work for me
since they would not have support for the new physical core
I posess? ie: I see newer files from say Linksys have more
ucodeN.fw N'umbers' available inside them than their older files..
> The TX and RX headers changed with firmware version 598.314.
598.314 is not now in fwcutter, was it at one time present and
> change in the driver was introduced with commit 17030f4 in such a way that
> the older firmware versions still worked.
> The two commits are at the bottom of the page
Looking them over.
> Ah, I know it by a different number.
What number is that?
How does something like '18.104.22.168 (r366174)' on the wrapper
relate to its corresponding internal '784.2'? What are those
strings each describing?
And is there a supposed changelog, perhaps but
not necessarily from Broadcom, for what changed
in the different firmwares that we find?
More information about the b43-dev