* Alexander Kuleshov <[email protected]> wrote:
> 2015-04-07 17:35 GMT+06:00 Ingo Molnar <[email protected]>:
> >
> >
> > So if you set up earlyprintk via CONFIG_CMDLINE_OVERRIDE it just
> > works?
> >
>
> Look, how i did it. I set:
>
> CONFIG_CMDLINE_BOOL =y
> CONFIG_CMDLINE_OVERRIDE =y
>
> and passed following string:
>
> [=root=/dev/sdb earlyprintk=ttyS0 loglevel=7 debug rdinit=/sbin/init
> root=/dev/ram memblock=debug]
>
> to the CONFIG_CMDLINE.
>
> Now i put two early_printk calls before and after earlyprintk initialization:
>
> early_printk("before setup_early_printk \n");
> setup_early_printk(boot_command_line);
> early_printk("after setup_early_printk \n");
>
> And i don't see first string, but see last.
>
> Did i make something wrong?
Yes, you need to check how and where in the arch init code
boot_command_line is set up in the CONFIG_CMDLINE_OVERRIDE=y case.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
