Hi Juergen,
Le 07/03/2013 15:10, Juergen Beisert a écrit :
> Maxime Ripard wrote:
>>> []
>>>
>>> Unfortunately I had to drop this one. It breaks compilation on some
>>> architectures which do not have _text and __bss_stop (namely blackfin
>>> and another one I forgot about).
>>>
>>> Anyway, I
Hi Maxime,
Maxime Ripard wrote:
> > []
> >
> > Unfortunately I had to drop this one. It breaks compilation on some
> > architectures which do not have _text and __bss_stop (namely blackfin
> > and another one I forgot about).
> >
> > Anyway, I realized that we now can start the MMU during earl
Hi Sascha,
Le 04/03/2013 09:02, Sascha Hauer a écrit :
> On Tue, Feb 26, 2013 at 05:55:41PM +0100, Maxime Ripard wrote:
>> get_ram_size cannot be used when running from RAM at the moment, even
>> though it backs up the memory cells it modifies, since it can also
>> modify the get_ram_size function
On Tue, Feb 26, 2013 at 05:55:41PM +0100, Maxime Ripard wrote:
> get_ram_size cannot be used when running from RAM at the moment, even
> though it backs up the memory cells it modifies, since it can also
> modify the get_ram_size function itself.
>
> Avoid testing the memory area where barebox is
get_ram_size cannot be used when running from RAM at the moment, even
though it backs up the memory cells it modifies, since it can also
modify the get_ram_size function itself.
Avoid testing the memory area where barebox is loaded at to prevent this
problem. If the memory supposed to host barebox
