public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2-2.1.3 is available
Date: Wed, 16 Jan 2002 20:43:45 -0500	[thread overview]
Message-ID: <20020116204345.A22055@thyrsus.com> (raw)
In-Reply-To: <20020116164758.F12306@thyrsus.com> <esr@thyrsus.com> <200201162156.g0GLukCj017833@tigger.cs.uni-dortmund.de> <20020116164758.F12306@thyrsus.com> <26592.1011230762@redhat.com>
In-Reply-To: <26592.1011230762@redhat.com>; from dwmw2@infradead.org on Thu, Jan 17, 2002 at 01:26:02AM +0000

David Woodhouse <dwmw2@infradead.org>:
> I'm concerned by the 'platform- and bus-type guards' to which you refer. 
> Could you give some examples where the behaviour has changed? Lots of 
> embedded non-x86, non-ISA boxen have ISA network chips glued in somehow, 
> for example. I hope you haven't helpfully stopped that from working.

No, I haven't.

Wha's happened is that I, and others, have merged in a lot of information 
about what cards can be plugged into which platforms.  That information
has been turned into dependency/visibility rules.

The generic hardware that can be used on several platforms has bus guards.
The on-board hardware has platform guards.  Some cards that can only be used
in single-platform buses have platform guards as well.

Here are some examples from the network cards...

Bus guards:

unless MCA suppress dependent ELMC ELMC_II ULTRAMCA SKMC NE2_MCA IBMLANA
unless ISA_CLASSIC suppress EL1 EL2 ELPLUS EL16 WD80x3 APOLLO_ELPLUS unless ISA_PNP suppress CONFIG_3C515 
unless EISA suppress dependent LNE390 NE3210
unless ISA_CLASSIC or EISA suppress AC3200
unless ISA_CLASSIC or ISA_PNP!=n or EISA or MCA suppress EL3	# 3c509 source
unless EISA or PCI or CARDBUS!=n suppress VORTEX	# Vortex help screen
unless ISA_CLASSIC or ISA_PNP!=n or PCI suppress LANCE		# Lance source
unless SPARC or SPARC64 suppress SUNLANCE
unless EISA suppress dependent ULTRA32                      	# SMC-ULTRA32
unless PCI suppress dependent 
	PCNET32 DE2104X TULIP EEPRO100 NE2K_PCI CONFIG_8139TOO CONFIG_8139TOO_8129 
	WINBOND_840 HAPPYMEAL ADAPTEC_STARFIRE FEALNX NATSEMI VIA_RHINE EPIC100
	SUNDANCE
unless ISA_CLASSIC suppress dependent NI52 NI65
unless EISA or PCI suppress DE4X5 DGRS DM9102 TLAN
unless ISA_CLASSIC or EISA or MCA suppress DEPCA	#depca.c
unless ISA_CLASSIC or EISA or MCA suppress HP100
unless ISA_CLASSIC or MCA suppress AT1700               #at1700.c
unless ISA_CLASSIC suppress dependent NI5010			#ni5010.c
unless ISA_CLASSIC suppress dependent E2100 EWRK3 EEXPRESS EEXPRESS_PRO FMV18X 
	HPLAN HPLAN_PLUS ETH16I SEEQ8005 SK_G16 ES3210 APRICOT
unless ISA_CLASSIC or ISA_PNP suppress NE2000 
unless ISA_PNP suppress ULTRA
unless ISA_PNP or CARDBUS suppress I82365

Platform guards:

unless SGI_IP27 or IA64_SGI_SN1 suppress SGI_IOC3_ETH
unless X86 suppress dependent ATP
unless X86 or ALPHA or PPC suppress NET_VENDOR_3COM 
unless X86 or ALPHA suppress LANCE NET_VENDOR_SMC NET_VENDOR_RACAL 
unless SPARC suppress dependent HAPPYMEAL SUNBMAC SUNQE
unless DECSTATION suppress dependent DECLANCE
unless BAGET_MIPS suppress dependent BAGETLANCE
unless (CONFIG_8xx or CONFIG_8260) suppress SCC_ENET FEC_ENET ENET_BIG_BUFFERS
unless AMIGA and PCMCIA!=n suppress dependent APNE
unless APOLLO suppress dependent APOLLO_ELPLUS
unless MAC suppress dependent MAC8390 MACSONIC SMC9194 MAC89x0 MACMACE CS89x0 
unless ATARI suppress dependent ATARILANCE
unless SUN3X or SPARC suppress SUN3LANCE
unless SUN3 suppress dependent SUN3_82586
unless HP300 suppress dependent HPLANCE
unless SUPERH suppress dependent STNIC

Compound bus *and* platform guard:

unless (X86 or ALPHA) and PARPORT!=n suppress dependent NET_POCKET

In a typical situation, you're going to enable platform and bus
symbols early.  All these guards will drastically filter the questions
you have to answer later.  The overall objective is to reduce the
questions a human user asks to those strictly relevant to his or her
configuration.

Now we're closing in on the second-stage objective, which is to automatically
discover (via an *optional* program...kids, remember that word *optional*)
so much about the configuration that the user need only answer questions 
that are genuinely about policy and capabilities.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The conclusion is thus inescapable that the history, concept, and 
wording of the second amendment to the Constitution of the United 
States, as well as its interpretation by every major commentator and 
court in the first half-century after its ratification, indicates 
that what is protected is an individual right of a private citizen 
to own and carry firearms in a peaceful manner.
         -- Report of the Subcommittee On The Constitution of the Committee On 
            The Judiciary, United States Senate, 97th Congress, second session 
            (February, 1982), SuDoc# Y4.J 89/2: Ar 5/5

  reply	other threads:[~2002-01-17  2:00 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 19:53 CML2-2.1.3 is available Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18   ` Eric S. Raymond
2002-01-15 20:41     ` Nicolas Pitre
2002-01-15 19:19       ` Rob Landley
2002-01-16  3:48         ` Eric S. Raymond
2002-01-16  6:29           ` Peter Samuelson
2002-01-16  6:32             ` Eric S. Raymond
2002-01-16  7:13               ` Peter Samuelson
2002-01-16  6:36             ` Alexander Viro
2002-01-16  0:15     ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24   ` Eric S. Raymond
2002-01-15 19:30     ` Rob Landley
2002-01-16  3:58       ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37   ` Rob Landley
2002-01-17  1:18     ` Val Henson
2002-01-21 16:22     ` Daniel Phillips
2002-01-21 17:05       ` [kbuild-devel] " Giacomo Catenazzi
2002-01-21 23:11         ` Daniel Phillips
2002-01-22  6:29           ` Kai Henningsen
2002-01-23 21:45         ` Daniel Phillips
2002-01-16  0:38   ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16  4:02   ` Eric S. Raymond
2002-01-16 16:38     ` Ross Vandegrift
2002-01-16 16:59       ` Ross Vandegrift
2002-01-16 18:29       ` Rob Landley
2002-01-18 18:32     ` Ross Vandegrift
2002-01-22  5:31       ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31   ` Eric S. Raymond
2002-01-16 21:56     ` Horst von Brand
2002-01-16 21:47       ` Eric S. Raymond
2002-01-17  1:26       ` David Woodhouse
2002-01-17  1:43         ` Eric S. Raymond [this message]
2002-01-17  8:53         ` David Woodhouse
2002-01-17 13:37           ` Eric S. Raymond
2002-01-17 14:09           ` David Woodhouse
2002-01-17 14:29             ` Eric S. Raymond
2002-01-16 23:36     ` David Lang
2002-01-18  6:48       ` Kai Henningsen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-22  9:11 [kbuild-devel] " Giacomo Catenazzi
2002-01-22  9:20 ` Keith Owens
     [not found] <fa.d4sn1fv.b78io8@ifi.uio.no>
     [not found] ` <fa.i3p6mlv.1mg2frl@ifi.uio.no>
2002-01-22 10:09   ` Giacomo Catenazzi
2002-01-22 10:25     ` Keith Owens
2002-01-22 10:48       ` Giacomo Catenazzi
2002-01-22 10:53         ` Keith Owens

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=20020116204345.A22055@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --cc=dwmw2@infradead.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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