mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: James C Georgas <jgeorgas@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vga text console
Date: Tue, 15 Aug 2006 09:54:09 +0800	[thread overview]
Message-ID: <1155606849.3948.17.camel@daplas.org> (raw)
In-Reply-To: <1155606109.8131.13.camel@Rainsong>

On Mon, 2006-08-14 at 21:41 -0400, James C Georgas wrote:
> On Tue, 2006-15-08 at 09:26 +0800, Antonino A. Daplas wrote:
> > On Tue, 2006-08-15 at 09:22 +0800, Antonino A. Daplas wrote:
> > > On Mon, 2006-08-14 at 21:11 -0400, James C Georgas wrote:
> > > > I can't seem to remove the VGA text console from my kernel
> > > > configuration. Can someone please enlighten me?
> > > 
> > > You can't. It is always part of the kernel (for X86 at least). What's
> > > your intention?
> 
> I want to write my own VGA text console driver.
> 
> > And correcting myself, you can configure out vgacon, but you have to
> > define CONFIG_EMBEDDED, and undefine CONFIG_VT.
> > 
> If I define CONFIG_EMBEDDED, is that going to change the behaviour of
> other subsystems, or does it just enable more options?
> 

It basically opens up a lot of config options. It may also disable a few
incompatible options (ie, CONFIG_DEBUG_VERBOSE), and enable a few.  It
will require that you know exactly what options need to be turned on or
off.

Tony


  reply	other threads:[~2006-08-15  1:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  1:11 James C Georgas
2006-08-15  1:22 ` Antonino A. Daplas
2006-08-15  1:26   ` Antonino A. Daplas
2006-08-15  1:41     ` James C Georgas
2006-08-15  1:54       ` Antonino A. Daplas [this message]
2006-08-15  2:09         ` James C Georgas
2006-08-15  6:11           ` Antonino A. Daplas
2006-08-15  6:52             ` Jan Engelhardt

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=1155606849.3948.17.camel@daplas.org \
    --to=adaplas@gmail.com \
    --cc=jgeorgas@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®