_write(const char *buf, int count);
+
+#ifdef CONFIG_EARLY_PRINTK
void early_panic(const char *fmt, ...);
+#else
+#define early_panic panic
+#endif
/* Init-time routine to do tile-specific per-cpu setup. */
void setup_cpu(int boot);
--
2.7.2
);
+
+#ifdef CONFIG_EARLY_PRINTK
void early_panic(const char *fmt, ...);
+#else
+#define early_panic panic
+#endif
/* Init-time routine to do tile-specific per-cpu setup. */
void setup_cpu(int boot);
--
2.7.2
There is the call of the console_init() function in the arch/x86/boot/main.c
which tries to find 'earlyprintk' option in the kernel command line. This
function called every time regardless of the CONFIG_EARLY_PRINTK, but we
no need in it if CONFIG_EARLY_PRINTK is not set.
Signed-off-by: Alexander
There is the call of the console_init() function in the arch/x86/boot/main.c
which tries to find 'earlyprintk' option in the kernel command line. This
function called every time regardless of the CONFIG_EARLY_PRINTK, but we
no need in it if CONFIG_EARLY_PRINTK is not set.
Signed-off-by: Alexander
All the code in early_serial_console.c gets compiled out if
!CONFIG_EARLY_PRINTK, but early_serial_console.o itself still gets
compiled in. Eliminate it from the compile entirely in that case.
This does not change the generated code at all, in either case.
Signed-off-by: Josh Triplett
All the code in early_serial_console.c gets compiled out if
!CONFIG_EARLY_PRINTK, but early_serial_console.o itself still gets
compiled in. Eliminate it from the compile entirely in that case.
This does not change the generated code at all, in either case.
Signed-off-by: Josh Triplett j
. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel A setup, the SCC
to initialise the device. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset
. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel A setup, the SCC
to initialise the device. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset
is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel A setup, the SCC then gets
is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel A setup, the SCC then gets
the device. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel
the device. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel
. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset for channel A setup, the SCC
to initialise the device. The result is that the SCC
interrupt sources become enabled (if they weren't already). This leads to
an early boot crash (unexpected interrupt) given CONFIG_EARLY_PRINTK. Fix
this by adding a delay. A successful reset disables the interrupt sources.
Also, after the reset
On 03/22/13 07:07, Thomas Meyer wrote:
> Am Samstag, den 16.03.2013, 10:38 -0700 schrieb Randy Dunlap:
>> On 03/16/13 08:08, Thomas Meyer wrote:
>>> Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
>>> Yes,
>>>
>>> so why not do this? As the text to EARLY_PRINTK explains?
>>
>> Yes,
On 03/22/13 07:07, Thomas Meyer wrote:
Am Samstag, den 16.03.2013, 10:38 -0700 schrieb Randy Dunlap:
On 03/16/13 08:08, Thomas Meyer wrote:
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
Yes,
so why not do this? As the text to EARLY_PRINTK explains?
Yes, the default should
Am Samstag, den 16.03.2013, 10:38 -0700 schrieb Randy Dunlap:
> On 03/16/13 08:08, Thomas Meyer wrote:
> > Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
> > Yes,
> >
> > so why not do this? As the text to EARLY_PRINTK explains?
>
> Yes, the default should match the help text.
>
Am Samstag, den 16.03.2013, 10:38 -0700 schrieb Randy Dunlap:
On 03/16/13 08:08, Thomas Meyer wrote:
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
Yes,
so why not do this? As the text to EARLY_PRINTK explains?
Yes, the default should match the help text.
Acked-by:
On Sat, Mar 16, 2013 at 6:38 PM, Randy Dunlap wrote:
> On 03/16/13 08:08, Thomas Meyer wrote:
>> Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
>>> On 03/13/13 10:15, Thomas Meyer wrote:
help text says:
"You should normally N here, unless you want to debug such a crash.
On 03/16/13 08:08, Thomas Meyer wrote:
> Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
>> On 03/13/13 10:15, Thomas Meyer wrote:
>>> Hi,
>>>
>>> -*- Early printk
>>>
>>> help text says:
>>> "You should normally N here, unless you want to debug such a crash.
>>> (Depends on:
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
> On 03/13/13 10:15, Thomas Meyer wrote:
> > Hi,
> >
> > -*- Early printk
> >
> > help text says:
> > "You should normally N here, unless you want to debug such a crash.
> > (Depends on: EXPERT [=n])"
> >
> > How to normally N
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
On 03/13/13 10:15, Thomas Meyer wrote:
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to normally N here?
You'll have to
On 03/16/13 08:08, Thomas Meyer wrote:
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
On 03/13/13 10:15, Thomas Meyer wrote:
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to
On Sat, Mar 16, 2013 at 6:38 PM, Randy Dunlap rdun...@infradead.org wrote:
On 03/16/13 08:08, Thomas Meyer wrote:
Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
On 03/13/13 10:15, Thomas Meyer wrote:
help text says:
You should normally N here, unless you want to debug such a
On 03/13/13 10:15, Thomas Meyer wrote:
> Hi,
>
> -*- Early printk
>
> help text says:
> "You should normally N here, unless you want to debug such a crash.
> (Depends on: EXPERT [=n])"
>
> How to normally N here?
You'll have to enable CONFIG_EXPERT and then you can disable EARLY_PRINTK.
You
Hi,
-*- Early printk
help text says:
"You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])"
How to normally N here?
kind regards
thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to normally N here?
kind regards
thomas
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On 03/13/13 10:15, Thomas Meyer wrote:
Hi,
-*- Early printk
help text says:
You should normally N here, unless you want to debug such a crash.
(Depends on: EXPERT [=n])
How to normally N here?
You'll have to enable CONFIG_EXPERT and then you can disable EARLY_PRINTK.
You may even
30 matches
Mail list logo