All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@sonic.net>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fallback to PCI IRQs for TI bridges
Date: Mon, 3 Mar 2003 12:56:20 -0800	[thread overview]
Message-ID: <20030303125620.A26220@sonic.net> (raw)
In-Reply-To: <Pine.LNX.4.50.0303031203300.17551-100000@marabou.research.att.com>

On Mon, Mar 03, 2003 at 12:26:54PM -0500, Pavel Roskin wrote:
> 
> I'm not aware of the "political" situation around PCMCIA drivers, but I
> think it's sad that the kernel drivers are pushed (e.g. by Red Hat) in the
> hope that they will get more visibility and will be improved, but the
> people who have the best expertize still use pcmcia-cs drivers and work on
> improving them.

I don't think it is a political issue.  I think the kernel drivers
should be promoted and I've encourated other distributions to go that
route as well.  And I hope that this leads to better drivers.  I do
maintenance work on the pcmcia-cs drivers but don't intend to add any
new functionality.

I've tried to update the kernel tree with fixes from individual PCMCIA
client drivers in the pcmcia-cs package.  The divergence of the core
modules is pretty large, though, so it is not a simple "diff", and I
know I've missed things.

I do not have time to be a more active maintainer these days, either
of pcmcia-cs or of the kernel PCMCIA drivers.

> 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.

-- Dave

  parent reply	other threads:[~2003-03-03 20:45 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 [this message]
2003-03-03 21:09       ` 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=20030303125620.A26220@sonic.net \
    --to=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 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.