Hi Reinhard,
Le 22/01/2011 12:00, Reinhard Meyer a écrit :
> Dear Albert ARIBAUD,
>
> this is not an ARM local issue.
Well, there *is* an ARM specific side of it (use of gd variables during
relocation), and that is what prompted me to start the RFC, but
generalization to U-boot is welcome if it
Dear Albert ARIBAUD,
this is not an ARM local issue.
The timeouts are used in generic drivers all around u-boot.
Have a grep for get_timer, reset_timer...
The most ugly use is with reset_timer involved, where the internal
pseudo-tick is reset to zero, so all calls to get_timer are
relative to t
Dne Ne 2. května 2010 13:07:13 Kyungmin Park napsal(a):
> On Sun, May 2, 2010 at 3:39 PM, Marek Vasut wrote:
> > Dne Ne 2. května 2010 05:54:41 Kyungmin Park napsal(a):
> >> Hi,
> >>
> >> Which CPU do you use? In most ARM cpu, CPU load the IPL into its
> >> internal SRAM, and runs at here.
> >
>
On Sun, May 2, 2010 at 3:39 PM, Marek Vasut wrote:
> Dne Ne 2. května 2010 05:54:41 Kyungmin Park napsal(a):
>> Hi,
>>
>> Which CPU do you use? In most ARM cpu, CPU load the IPL into its
>> internal SRAM, and runs at here.
> PXA270 ... the BootRAM is mapped to 0x0 and the code runs from there.
>>
Dne Ne 2. května 2010 05:54:41 Kyungmin Park napsal(a):
> Hi,
>
> Which CPU do you use? In most ARM cpu, CPU load the IPL into its
> internal SRAM, and runs at here.
PXA270 ... the BootRAM is mapped to 0x0 and the code runs from there.
> But in your case it's not. So you maybe redefine IPL address
Hi,
Which CPU do you use? In most ARM cpu, CPU load the IPL into its
internal SRAM, and runs at here.
But in your case it's not. So you maybe redefine IPL address.
Instead of modifying the config.mk, how about to define IPL_TEXT_BASE.
e.g.,
In OneNAND IPL code,
#ifndef BOARD_IPL_TEXT_BASE
#def
6 matches
Mail list logo
