On 7/25/11, sandeep kumar wrote:
> Hi vladimir
>>I think this kind of behaviour could be configurable. In case you have
>>described bootloader can protect its code. Actually, kernel does not
>>know itself how much RAM is presented. Bootloader must provide kernel
>>with memory configuration through
Hi vladimir
>I think this kind of behaviour could be configurable. In case you have
>described bootloader can protect its code. Actually, kernel does not
>know itself how much RAM is presented. Bootloader must provide kernel
>with memory configuration through ATAGs (see mem boot option).
>Therefore
Hi sandeep!
On 7/25/11, sandeep kumar wrote:
> Hi all,
> In Android target mobiles there is a facility called "Ramdump", where the
> entire Ram image is copied to a file
> as the kernel goes to panic.
>
> Ramdump is implemented like this
> 1) As the panic() function is called target will be reset
Hi sandeep,
On Sun, Jul 24, 2011 at 9:18 PM, sandeep kumar
wrote:
> Hi all,
> In Android target mobiles there is a facility called "Ramdump", where the
> entire Ram image is copied to a file
> as the kernel goes to panic.
>
> Ramdump is implemented like this
> 1) As the panic() function is called
Hi all,
In Android target mobiles there is a facility called "Ramdump", where the
entire Ram image is copied to a file
as the kernel goes to panic.
Ramdump is implemented like this
1) As the panic() function is called target will be reset.
2) Bootloader boots up in specific mode, where it enables
