public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>,
	Nicolas Pitre <nico@cam.org>,
	morton@nortelnetworks.com, linux-kernel@vger.kernel.org
Subject: Re: Fwd: [Fwd: [PATCH] cs89x0 is not only an ISA card]
Date: Thu, 14 Dec 2000 12:00:13 -0500	[thread overview]
Message-ID: <3A38FC9D.7B2F2B7D@mandrakesoft.com> (raw)
In-Reply-To: <200012141525.PAA00867@raistlin.arm.linux.org.uk>

Russell King wrote:
> 
> Erik Mouw writes:
> > The Crystal CS89x0 ethernet chip is also used in quite some embedded
> > systems that don't have an ISA bus at all, so the CONFIG_ISA option in
> > drivers/net/Config.in is inapropriate. Here is a patch against
> > 2.4.0-test12 to fix that. Please consider applying.
> 
> I don't think this is the right way to fix the problem.  Take for instance
> an EBSA285 platform which has only PCI sockets.  It is possible to plug in
> a card with an ISA bridge on, with a ESS SB clone on board (I have one here).
> 
> Maybe the right thing to do is to define CONFIG_ISA on these architectures/
> machine types where the device itself is actually an ISA device, instead of
> going through special-casing the driver configuration entries?

Agreed.  We -don't- want to remove CONFIG_ISA or other dependencies. 
The idea for drivers/net/Config.in at least is that all architectures
can source the file, and be presented with a proper list of devices for
that platform.

For an embedded board that supports cs89x0, as you suggest, defining
CONFIG_ISA is a much better option.  Or, making cs89x0 dependent on
CONFIG_EMBEDDED_PLATFORM -and- CONFIG_ISA.

	Jeff


-- 
Jeff Garzik         |
Building 1024       | These are not the J's you're lookin' for.
MandrakeSoft        | It's an old Jedi mind trick.
-
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-12-14 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001214011415.E15157@arthur.ubicom.tudelft.nl>
2000-12-14 15:25 ` Fwd: [Fwd: [PATCH] cs89x0 is not only an ISA card] Russell King
2000-12-14 17:00   ` Jeff Garzik [this message]
2000-12-14 18:29     ` Alan Cox
2000-12-14 18:42     ` Erik Mouw
2000-12-14 19:15       ` Russell King

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=3A38FC9D.7B2F2B7D@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=J.A.K.Mouw@ITS.TUDelft.NL \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morton@nortelnetworks.com \
    --cc=nico@cam.org \
    --cc=rmk@arm.linux.org.uk \
    /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