Naming of mfc_fw.bin & s5p-mfc.fw

[gripped]

I realised from reading this post
http://forum.odroid.com/viewtopic.php?f ... 462#p26779
that the firmware on the Arch image I made is an older one.
On checking I found that I had included the newer one at
/lib/firmware/s5p-mfc/s5p-mfc.fw
And the older one was at
/lib/firmware/mfc_fw.bin

Simply linking

Code: Select all

ln -s /lib/firmware/s5p-mfc/s5p-mfc.fw  /lib/firmware/mfc_fw.bin

causes to newer firmware to be loaded at boot

[ 11.012610] MFC v6.5, F/W: 13yy, 10mm, 15dd (D)

Then I realised that the newer firmware was actually being loaded , but only when needed. When running xbmc

I can see /drivers/media/video/exynos/mfc/s5p_mfc_common.h references mfc_fw.bin and
/drivers/media/video/s5p-mfc/s5p_mfc_ctrl.c references s5p-mfc.fw
but in fact both these files are the same firmware ?

Is this correct ? Is there a simple explanation of why ?

[mdrjr]

Hello..

It should be using the drivers/media/video/exynos/mfc as the driver.

[gripped]

Hello..

It should be using the drivers/media/video/exynos/mfc as the driver.

I've done some more testing and I was wrong (and you are of course right), only mfc_fw.bin is ever loaded.

I've never seen it documented that when you download a newer mfc firmware you have to rename it from s5p-mfc.fw to mfc_fw.bin
All the mfc firmwares I've downloaded have been in the s5p-mfc.fw format
Hopefully now this thread is stuffed with keywords this information will be found if any one searches for it

rename s5p-mfc.fw to mfc_fw.bin and place it at /lib/firmware/mfc_fw.bin for the win