On Nov 19, 2010, at 4:23 AM, DUNDA Matthias wrote:
>>>
Well, it's actually 2 Gig, just like u-boot recognizes above...
>>>
>>> There's something wrong with the parameter you're passing to print_size().
>
>> I'm guessing its -1 or something like that.
>
> I used the board specific code of
>>
>>> Well, it's actually 2 Gig, just like u-boot recognizes above...
>>
>> There's something wrong with the parameter you're passing to print_size().
>I'm guessing its -1 or something like that.
I used the board specific code of the MPC8568MDS and adapted it to our
configuration.
The code reg
On Nov 18, 2010, at 1:04 PM, Timur Tabi wrote:
> On Thu, Nov 18, 2010 at 9:02 AM, DUNDA Matthias
> wrote:
>
>> Well, it's actually 2 Gig, just like u-boot recognizes above...
>
> There's something wrong with the parameter you're passing to print_size().
I'm guessing its -1 or something like t
On Thu, Nov 18, 2010 at 9:02 AM, DUNDA Matthias
wrote:
> Well, it's actually 2 Gig, just like u-boot recognizes above...
There's something wrong with the parameter you're passing to print_size().
--
Timur Tabi
Linux kernel developer at Freescale
___
> > CPU: 8568E, Version: 1.1, (0x807d0011)
> > Core: E500, Version: 2.2, (0x80210022)
> > ...
> > DRAM: Initializing
> > 4 PiB left unmapped
> >DDR: 2 GiB (DDR2, 64-bit, CL=4, ECC off)
> > FLASH: 256 MiB
> > L2:512 KB enabled
>
> Pretty cool, how much memory do you actually have in the
On Nov 18, 2010, at 8:41 AM, DUNDA Matthias wrote:
> Hi again,
>
> my current binary of U-Boot claims, that 4 petabyte of memory are unmapped:
>
>
> U-Boot 2010.09-svn314 (Nov 18 2010 - 15:09:16)
>
> CPU: 8568E, Version: 1.1, (0x807d0011)
> Core: E500, Version: 2.2, (0x80210022)
> ...
> DR
Hi again,
my current binary of U-Boot claims, that 4 petabyte of memory are unmapped:
U-Boot 2010.09-svn314 (Nov 18 2010 - 15:09:16)
CPU: 8568E, Version: 1.1, (0x807d0011)
Core: E500, Version: 2.2, (0x80210022)
...
DRAM: Initializing
4 PiB left unmapped
DDR: 2 GiB (DDR2, 64-bit, CL=4, E
7 matches
Mail list logo