Re: command bootu to start kernel

[Belisko Marek <marek.belisko@gmail.com>]

On Fri, Oct 29, 2010 at 11:12 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 10/29/2010 11:04 AM, Belisko Marek wrote:
>> On Fri, Oct 29, 2010 at 10:50 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>>> On 10/29/2010 10:45 AM, Belisko Marek wrote:
>>>> HI Baruch,
>>>>
>>>> On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>>>> Hi Belisko,
>>>>>
>>>>> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>>>>>> I have 2.6.32 kernel but early_printk isn't available and I enable
>>>>>> lowlevel debugging but
>>>>>> don't get nothing else on console. Anyway thanks.
>>>>>
>>>>> Try this patch to see the low level console output:
>>>>>
>>>>> commit 5c31454464ed655401c31c68c895b16eafd2bde5
>>>>> Author: Baruch Siach <baruch@tkos.co.il>
>>>>> Date:   Mon Jan 19 10:41:47 2009 +0200
>>>>>
>>>>>    arm, printk: the famous printascii() hack
>>>>>
>>>>> diff --git a/kernel/printk.c b/kernel/printk.c
>>>>> index 5052b54..d685f8a 100644
>>>>> --- a/kernel/printk.c
>>>>> +++ b/kernel/printk.c
>>>>> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>>>>>        /* Emit the output into the temporary buffer */
>>>>>        printed_len += vscnprintf(printk_buf + printed_len,
>>>>>                                  sizeof(printk_buf) - printed_len, fmt, args);
>>>>> +       {
>>>>> +               extern void printascii(const char *);
>>>>> +               printascii(printk_buf);
>>>>> +       }
>>>>>
>>>>>
>>>>>        /*
>>>>>
>>>>> --
>>>>>                                                     ~. .~   Tk Open Systems
>>>>> =}------------------------------------------------ooO--U--Ooo------------{=
>>>>>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>>>>
>>>> Patch works like charm. Output from my kernel startup:
>>>>
>>>> <5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
>>>> (Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
>>>> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
>>>> CPU: VIVT data cache, VIVT instruction cache
>>>> Machine: MINI2440
>>>> Memory policy: ECC disabled, Data cache writeback
>>>> <7>On node 0 totalpages: 0
>>>> <1>bootmem alloc of 32768 bytes failed!
>>>> <0>Kernel panic - not syncing: Out of memory
>>>
>>> do you have a "MEM=32" on your command line?
>> Well I add it but same result:
>
> BTW: It must be "mem=", in lowercase, but you did this.
>
> What I was meant to ask was, if you forget to add the "M" to "32".
> Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
> your ATAGs are broken, Linux might not see the whole RAM or any if it.
yes it was typo I forgot put M after 32. Kernel now properly boot :).
U-boot somehow
add kernel this parameter? Because for u-boot I don't need to set this
parameter.
>
> Cheers, Marc
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox