The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Travis <travis@sgi.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Add config option to setup early serial console
Date: Thu, 12 Jun 2008 15:46:00 -0700	[thread overview]
Message-ID: <20080612154600.fac8cc6b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080612223802.673729000@polaris-admin.engr.sgi.com>

On Thu, 12 Jun 2008 15:38:03 -0700
Mike Travis <travis@sgi.com> wrote:

>  * Add config option EARLY_SERIAL_CONSOLE to enable early
>    printk's to be directed to the serial console.
> 
> Based on linux-next
> 
> Signed-off-by: Mike Travis <travis@sgi.com>
> ---
> 
> ---
>  arch/x86/Kconfig.debug         |    9 +++++++++
>  arch/x86/kernel/early_printk.c |    4 ++++
>  2 files changed, 13 insertions(+)
> 
> --- linux-2.6-next.orig/arch/x86/Kconfig.debug
> +++ linux-2.6-next/arch/x86/Kconfig.debug
> @@ -29,6 +29,15 @@ config EARLY_PRINTK
>  	  with klogd/syslogd or the X server. You should normally N here,
>  	  unless you want to debug such a crash.
>  
> +config EARLY_SERIAL_CONSOLE
> +	bool "Early Serial Console"
> +	default m
> +	help
> +	  Initializes the early console to be the serial port.  The default
> +	  is to use the VGA console.
> +
> +	  This is useful for server systems that do not have a VGA console.
> +
>  config DEBUG_STACKOVERFLOW
>  	bool "Check for stack overflows"
>  	depends on DEBUG_KERNEL
> --- linux-2.6-next.orig/arch/x86/kernel/early_printk.c
> +++ linux-2.6-next/arch/x86/kernel/early_printk.c
> @@ -193,7 +193,11 @@ static struct console simnow_console = {
>  };
>  
>  /* Direct interface for emergencies */
> +#ifdef CONFIG_EARLY_SERIAL_CONSOLE
> +static struct console *early_console = &early_serial_console;
> +#else
>  static struct console *early_console = &early_vga_console;
> +#endif
>  static int early_console_initialized;
>  
>  void early_printk(const char *fmt, ...)
> 

Confused.  What's wrong with console=uart,...?



  parent reply	other threads:[~2008-06-12 22:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080612223802.528617000@polaris-admin.engr.sgi.com>
2008-06-12 22:38 ` [PATCH 1/1] x86: Add config option to setup early serial console Mike Travis
2008-06-12 22:42   ` H. Peter Anvin
2008-06-12 22:54     ` Mike Travis
2008-06-12 22:59       ` H. Peter Anvin
2008-06-12 22:42   ` Mike Travis
2008-06-12 22:46   ` Andrew Morton [this message]
2008-06-12 22:58     ` Mike Travis
2008-06-12 23:10       ` Andrew Morton
2008-06-12 23:18         ` Yinghai Lu
2008-06-12 23:19         ` Yinghai Lu
     [not found] <20080612224247.486614000@polaris-admin.engr.sgi.com>
2008-06-12 22:42 ` Mike Travis
2008-06-12 22:48   ` Yinghai Lu
2008-06-12 23:01     ` Mike Travis
2008-06-18 12:13       ` Ingo Molnar
     [not found] <20080612223343.257409000@polaris-admin.engr.sgi.com>
2008-06-12 22:33 ` Mike Travis
2008-06-12 22:37   ` Mike Travis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080612154600.fac8cc6b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox