All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andries Brouwer <aeb@veritas.com>
Cc: Steven Cole <elenstev@mesatop.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_EISA note in Documentation/Configure.help
Date: Tue, 14 Nov 2000 15:23:05 -0500	[thread overview]
Message-ID: <3A119F29.2BD8E7C@mandrakesoft.com> (raw)
In-Reply-To: <00111317072200.00727@localhost.localdomain> <20001114205950.A25349@veritas.com>

Andries Brouwer wrote:
> However, CONFIG_EISA is almost completely superfluous, is not
> required at compile time, can easily be tested at run time,
> in other words adding such an option is a very stupid thing to do.

Each driver's entry in Config.in should be dependent on its
CONFIG_{ISA,EISA,PCI,SBUS,...} defines that indicate what buses are
defined on this particular architecture.  Eventually, DaveM and other
Sparc users will be able to directly source drivers/net/Config.in, and
be presented with the correct list of net drivers given their selected
bus(es).  Ditto for ARM.  Ditto for x86.  Etc.

Disabling code by making global var 'EISA_bus' unconditionally zero was
just an added bonus.  Helps a tiny bit with embedded platforms.


> [Steven, you understand that I would have written under CONFIG_EISA:
> say Y here - there is never any reason to say N, unless there exists
> hardware where the canonical probing hangs the machine.]

Agreed, for the most part.  If you know for sure you don't have an EISA
machine, you can now disable CONFIG_EISA.  IMHO ideally one should be
able to eliminate code that is useless on all but a small subset of
working machines.

	Jeff


-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-14 20:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14  0:07 [PATCH] CONFIG_EISA note in Documentation/Configure.help Steven Cole
2000-11-14 19:59 ` Andries Brouwer
2000-11-14 20:23   ` Jeff Garzik [this message]
2000-11-14 21:00     ` Andries Brouwer
     [not found]   ` <3A127070.7DEE2527@yahoo.com>
2000-11-17 22:01     ` Andries Brouwer
2000-11-17 23:24       ` Alan Cox
2000-11-18 11:26       ` Christer Weinigel
  -- strict thread matches above, loose matches on Subject: below --
2000-11-14 20:48 Steven Cole
2000-11-14 21:06 ` Jeff Garzik
2000-11-14 21:22 Steven Cole
2000-11-14 23:37 Andrzej Krzysztofowicz
2000-11-17 23:47 Andries.Brouwer

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=3A119F29.2BD8E7C@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=aeb@veritas.com \
    --cc=elenstev@mesatop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.