[PATCH] tile: allow disabling CONFIG_EARLY_PRINTK

2016-06-07 Thread Chris Metcalf
*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

[PATCH RFC] x86/boot, earlyprintk: do not compile early_setup_console if !CONFIG_EARLY_PRINTK

2015-04-06 Thread Alexander Kuleshov
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:

[PATCH 3/3] x86, boot: Don't compile early_serial_console.c when !CONFIG_EARLY_PRINTK

2014-03-10 Thread 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

[041/141] m68k/mac: Fix unexpected interrupt with CONFIG_EARLY_PRINTK

2013-07-03 Thread Steven Rostedt
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

[PATCH 19/93] m68k/mac: Fix unexpected interrupt with CONFIG_EARLY_PRINTK

2013-06-18 Thread Luis Henriques
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

[ 078/127] m68k/mac: Fix unexpected interrupt with CONFIG_EARLY_PRINTK

2013-06-05 Thread Greg Kroah-Hartman
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 g

[ 36/44] m68k/mac: Fix unexpected interrupt with CONFIG_EARLY_PRINTK

2013-06-05 Thread Greg Kroah-Hartman
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 g

[PATCH 72/75] m68k/mac: Fix unexpected interrupt with CONFIG_EARLY_PRINTK

2013-06-04 Thread Kamal Mostafa
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

Re: CONFIG_EARLY_PRINTK

2013-03-25 Thread Randy Dunlap
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, t

Re: CONFIG_EARLY_PRINTK

2013-03-22 Thread Thomas Meyer
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. > A

Re: CONFIG_EARLY_PRINTK

2013-03-16 Thread Geert Uytterhoeven
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. >

Re: CONFIG_EARLY_PRINTK

2013-03-16 Thread Randy Dunlap
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: EXPER

Re: CONFIG_EARLY_PRINTK

2013-03-16 Thread Thomas Meyer
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

Re: CONFIG_EARLY_PRINTK

2013-03-13 Thread 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 enable CONFIG_EXPERT and then you can disable EARLY_PRINTK. You

CONFIG_EARLY_PRINTK

2013-03-13 Thread Thomas Meyer
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 majord...@vg