Hello Peter,
2015-04-08 17:32 GMT+06:00 Peter Hurley :
>> +
>> +void setup_early_serial_console() {
>
> If you put this function in kernel/early_printk.c, then
> setup_early_printk() can remain file scope.
>
Yes, right. will fix it.
>
> The WARN is still required here because the
Hello Peter,
2015-04-08 17:32 GMT+06:00 Peter Hurley pe...@hurleysoftware.com:
+
+void setup_early_serial_console() {
If you put this function in kernel/early_printk.c, then
setup_early_printk() can remain file scope.
Yes, right. will fix it.
The WARN is still required here because the
Hi Alexander,
On 04/08/2015 05:31 AM, Alexander Kuleshov wrote:
> As setup_early_printk passed to the early_param, it will be usable only after
> 'parse_early_param' function will be called from the 'setup_arch'. So we have
> earlyprintk during early boot and decompression. Next point after
>
As setup_early_printk passed to the early_param, it will be usable only after
'parse_early_param' function will be called from the 'setup_arch'. So we have
earlyprintk during early boot and decompression. Next point after decompression
of the kernel where we can use early_printk is after call of
Hi Alexander,
On 04/08/2015 05:31 AM, Alexander Kuleshov wrote:
As setup_early_printk passed to the early_param, it will be usable only after
'parse_early_param' function will be called from the 'setup_arch'. So we have
earlyprintk during early boot and decompression. Next point after
As setup_early_printk passed to the early_param, it will be usable only after
'parse_early_param' function will be called from the 'setup_arch'. So we have
earlyprintk during early boot and decompression. Next point after decompression
of the kernel where we can use early_printk is after call of
6 matches
Mail list logo
