Tero Kristo <[EMAIL PROTECTED]> writes:
> Without this, causes some random crashes related to memory management.
>
> Signed-off-by: Tero Kristo <[EMAIL PROTECTED]>
Looks like this is against pm-20081106. Pulling into next PM branch.
Kevin
> ---
> arch/arm/mach-omap2/pm34xx.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 0df3245..58d0479 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -883,7 +883,7 @@ int __init omap3_pm_init(void)
>
> if (omap_type() != OMAP2_DEVICE_TYPE_GP) {
> omap3_secure_ram_storage =
> - kmalloc(0x8000, GFP_KERNEL);
> + kmalloc(0x803F, GFP_KERNEL);
> if (!omap3_secure_ram_storage)
> printk(KERN_ERR "Memory allocation failed when"
> "allocating for secure sram context\n");
> --
> 1.5.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
