public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: David Hinds <dhinds@sonic.net>
Cc: Pavel Roskin <proski@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fallback to PCI IRQs for TI bridges
Date: Mon, 3 Mar 2003 21:09:21 +0000	[thread overview]
Message-ID: <20030303210921.D17997@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030303125620.A26220@sonic.net>; from dhinds@sonic.net on Mon, Mar 03, 2003 at 12:56:20PM -0800

On Mon, Mar 03, 2003 at 12:56:20PM -0800, David Hinds wrote:
> > I think it CONFIG_ISA is meant to be that.  The "ISA support" is so
> > trivial from the kernel perspective, that the line between systems with
> > and without ISA is somewhat blurred.
> 
> I don't really know what the scope of CONFIG_ISA should be.  I think
> now it is mainly used to show or hide drivers for ISA cards, rather
> than describing a system capability.

In my bunch of PCMCIA/Cardbus/PCI changes, I have one patch which
decouples CONFIG_ISA from the PCMCIA subsystem, replacing it with
CONFIG_PCMCIA_PROBE - on statically mapped PCMCIA systems (eg, SA1110)
all the region probing, resource handling, and interrupt stuff is
rather heavy weight.  However, decoupling it from CONFIG_ISA would
allow all that supporting code to remain when required for some socket
drivers.

I'm working through getting stuff tested and in to Linus in a reasonable
way.  Of course, this won't help for 2.4 based kernels, although the
CONFIG_PCMCIA_PROBE has existed in the ARM tree for a fair while and
could, given someone with enough motivation, the relevant changes could
be dug out and submitted to Marcello.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-03-03 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01  1:30 [PATCH] Fallback to PCI IRQs for TI bridges Pavel Roskin
2003-03-01  1:36 ` Jeff Garzik
2003-03-01  3:00 ` Alan Cox
2003-03-01  5:05   ` Pavel Roskin
2003-03-01 17:38 ` David Hinds
2003-03-01 18:05   ` Jeff Garzik
2003-03-03 17:26   ` Pavel Roskin
2003-03-03 20:31     ` Jeff Garzik
2003-03-03 20:56     ` David Hinds
2003-03-03 21:09       ` Russell King [this message]

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=20030303210921.D17997@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dhinds@sonic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.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