public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Leif Sawyer <lsawyer@gci.com>
Cc: esr@snark.thyrsus.com, linux-kernel@vger.kernel.org
Subject: Re: CML2 1.1.3 release announcement
Date: Tue, 17 Apr 2001 09:53:15 -0400	[thread overview]
Message-ID: <20010417095315.B27468@thyrsus.com> (raw)
In-Reply-To: <BF9651D8732ED311A61D00105A9CA3150446DA08@berkeley.gci.com>
In-Reply-To: <BF9651D8732ED311A61D00105A9CA3150446DA08@berkeley.gci.com>; from lsawyer@gci.com on Mon, Apr 16, 2001 at 03:46:44PM -0800

Leif Sawyer <lsawyer@gci.com>:
> It also appears that upon a re-configuration of 2.4.3 from 2.2.17:
> 
> > cd /usr/src/linux
> > cp ../linux-2.2.17/.config .
> > make oldconfig
> 
> where the old configuration did not include FrameBuffer support,
> then performing an Xconfig to tweak some settings and enable FB,
> no default fonts were allocated.  This is contrary to CML1 behavoir.
> 
> > grep ^CONFIG_FB .config
> CONFIG_FB=y
> CONFIG_FB_VESA=y
> CONFIG_FB_MACH64=y
> 
> 
> however CML1, after only selecting the applicable drivers gives:
> > grep ^CONFIG_FB ~/myotherbox-2.4.3.config
> CONFIG_FB=y
> CONFIG_FB_VESA=y
> CONFIG_FB_VGA16=y
> CONFIG_FBCON_CFB8=y
> CONFIG_FBCON_CFB16=y
> CONFIG_FBCON_CFB24=y
> CONFIG_FBCON_CFB32=y
> CONFIG_FBCON_VGA_PLANES=y

Yes, all those extra symbols are derived from the drivers that you 
didn't select during the CML2 run.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

.. a government and its agents are under no general duty to 
provide public services, such as police protection, to any 
particular individual citizen...
        -- Warren v. District of Columbia, 444 A.2d 1 (D.C. App.181)

  reply	other threads:[~2001-04-17 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 23:46 CML2 1.1.3 release announcement Leif Sawyer
2001-04-17 13:53 ` Eric S. Raymond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-16 22:23 Leif Sawyer

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=20010417095315.B27468@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=esr@snark.thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsawyer@gci.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