qiang.z...@freescale.com wrote:
Other boards have either Fman or QE, So CONFIG_SYS_QE_FMAN_FW_ADDR can
be used either Fman or QE.
But T1040QDS have both Fman and QE.
Does the T1040QDS have microcode for both Fman and QE? Normally, QE
microcode is not needed.
qiang.z...@freescale.com wrote:
CONFIG_SYS_QE_FMAN_FW_ADDR is used for Fman microcode while
CONFIG_SYS_QE_UCODE_FW_ADDR used
For QE microcode.
No, CONFIG_SYS_QE_FMAN_FW_ADDR is used for both QE and Fman microcode.
That's why it says "QE_FMAN" in it. This is documented in the README.
___
On 14-01-25 11:46 AM, bhupesh.sha...@freescale.com [via U-Boot] wrote:
>
>
>>
>> However, if we set up u-boot so that it can wake up at any security
>> level and migrate to non-secure EL1, that might be a nice compromise.
>> But having specific EL3 startup assumptions and code that is always
>>
Enable required clocks for GPIO to fix a boot issue introduced by commit
f33b9bd3984fb11e1d8566a866adc5957b1e1c9d (arm: omap3: Enable clocks for
peripherals only if they are used).
Without this patch the u-boot freezes after the following messages
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Ma
I have fixed the problem. The imx6 pads accessing the SD needed some better
calibration in my board file
Thank you
A
On Sat, Jan 25, 2014 at 2:39 PM, Andy Ng wrote:
> Dear colleagues,
>
> The u-boot freezes when I try to read mmc for second time. u-boot 2013-10,
> imx6 Solo CPU
>
> One the fir
> -Original Message-
> From: Darwin Rambo [mailto:dra...@broadcom.com]
> Sent: Thursday, January 23, 2014 10:35 PM
> To: Detlev Zundel; Sharma Bhupesh-B45370
> Cc: 'u-boot@lists.denx.de'; 'Tom Rini'
> Subject: Re: [U-Boot] how to get u-boot code with arm64: core support
>
>
>
> On 14-01-
On 01/25/2014 07:46 AM, Timur Tabi wrote:
> On Fri, Jan 24, 2014 at 7:45 AM, Wolfgang Denk wrote:
>>
>> For the "test"
>> part, it is probably much easier to add a customized memory test (or
>> fix just the existing memory test such that it can be built for a 64
>> bit mode) and use this, then try
From: Fabio Estevam
There is no need to print an error message when cpu_eth_init() fails because
net/eth.c already prints it.
In order to simplify the code, just return the value from cpu_eth_init(bis)
directly.
Signed-off-by: Fabio Estevam
---
board/solidrun/hummingboard/hummingboard.c |
On Fri, Jan 24, 2014 at 3:05 AM, Zhao Qiang wrote:
> +#ifdef CONFIG_PPC_T1040
> + qe_upload_firmware((const void *)CONFIG_SYS_QE_UCODE_FW_ADDR);
> +#else
> qe_upload_firmware((const void *)CONFIG_SYS_QE_FMAN_FW_ADDR);
> +#endif
>
It's been a while since I looked at the QE code in U
On Fri, Jan 24, 2014 at 7:45 AM, Wolfgang Denk wrote:
>
> For the "test"
> part, it is probably much easier to add a customized memory test (or
> fix just the existing memory test such that it can be built for a 64
> bit mode) and use this, then trying to run all of U-Boot in 64 bit
> mode.
There
Dear colleagues,
The u-boot freezes when I try to read mmc for second time. u-boot 2013-10,
imx6 Solo CPU
One the first read I do have also an error:
mx6s > run bootmmc
reading uImage
Error reading cluster
** Unable to read file uImage **
## Booting kernel from Legacy Image at 1200 ...
Im
On Fri, Dec 13, 2013 at 02:42:58PM +0530, Pekon Gupta wrote:
> @@ -1851,7 +1854,13 @@ static int omap_nand_probe(struct platform_device
> *pdev)
> ecclayout->eccbytes = nand_chip->ecc.bytes *
> (mtd->writesize /
>
On Fri, Dec 13, 2013 at 02:42:57PM +0530, Pekon Gupta wrote:
> This patch updates starting offset for free bytes in OOB which can be used by
> file-systems to store their metadata (like clean-marker in case of JFFS2).
This should be describing a regression fix, right? We don't just
arbitrarily cha
Hi Pekon,
Sorry, I'm revisiting your patch series a bit late. There are a few
factors that contributed to this, though.
1. This patch series talks extensively about U-Boot. U-Boot is not my
interest, nor should it be the focus of kernel (driver) development.
Any work done here should be fra
-Add usb2 node entry in "hwconfig string"
-Remove controller interleaving from hwconfig string as T1040
has only one DDR conroller
-SPI related macros which were earlier under #ifdef CONFIG_SPIFLASH
are move outside so that they are defined for all cases as these
macros are also used by other
15 matches
Mail list logo
