On Nov 8, 2011, at 5:40 PM, Timur Tabi wrote:
Several macros are used to identify and locate the microcode binary image
that U-boot needs to upload to the QE or Fman. Both the QE and the Fman
use the QE Firmware binary format to package their respective microcode data,
which is why the same
Kumar Gala wrote:
Can your respin against current upstream HEAD. For some reason this doesn't
apply cleanly there.
This patch broke it:
drivers/net/fm/fm.c: Fix GCC 4.6 build warning
I'll post a v2 in just a few minutes.
--
Timur Tabi
Linux kernel developer at Freescale
On Nov 8, 2011, at 5:40 PM, Timur Tabi wrote:
Several macros are used to identify and locate the microcode binary image
that U-boot needs to upload to the QE or Fman. Both the QE and the Fman
use the QE Firmware binary format to package their respective microcode data,
which is why the same
Kumar Gala wrote:
#ifdef CONFIG_QE
/* QE microcode/firmware address */
-#define CONFIG_SYS_QE_FW_ADDR0xefec
-#define CONFIG_SYS_QE_FW_LENGTH 0x1
+#define CONFIG_SYS_QE_FMAN_FW_IN_NOR
+#define CONFIG_SYS_QE_FMAN_FW_ADDR 0xefec
+#define
Several macros are used to identify and locate the microcode binary image
that U-boot needs to upload to the QE or Fman. Both the QE and the Fman
use the QE Firmware binary format to package their respective microcode data,
which is why the same macros are used for both. A given SOC will only
5 matches
Mail list logo