checking atags for boot parameters

[Christopher Harvey]

 On Wed, 22 Jun 2011 00:14:50 +0700, Mulyadi Santosa 
 <mulyadi.santosa at gmail.com> wrote:
> Hi Christ... :)
 It's Chris.
>
> On Tue, Jun 21, 2011 at 21:20, Christopher Harvey
> <chris at basementcode.com> wrote:
>>  I'm suspicious that the bootloader I'm using isn't passing atags to 
>> the
>>  kernel properly.
>
> which bootloader?
 uboot
>
>>  I'm getting a prefetch exception right after the "uncompressing
>>  linux....done" message, does it make sense that this could happen
>>  because mem=128M isn't getting passed properly?
>
> uhm, fairly unlikely for me.... must be something else... could you
> tell us which arch it is and which kernel version (along with patches
> from certain tree, if any) that yield that error message?
 It's not an error message, but with difficulty I was able to trace some 
 of the code and it ends up in a prefetch exception handler. I am not 
 able to find out from where however, and the line stepping is a bit 
 sketchy. No major patches to the kernel, and it runs in QEMU without 
 error. Adding uboot to QEMU then booting the same kernel yields the 
 problems.

 It would be nice to find out what physical address the kernel is 
 uncompressed to as well, I'm as of yet unable to properly trace after 
 decompression.

 -C