From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Roskin <proski@gnu.org>
Cc: David Hinds <dhinds@sonic.net>,
David Hinds <dahinds@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fallback to PCI IRQs for TI bridges
Date: Mon, 3 Mar 2003 15:31:15 -0500 [thread overview]
Message-ID: <20030303203115.GD6615@gtf.org> (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:
> Hi, David!
>
> > > yenta_socket in 2.5.63 knows different models of the bridges and sets IRQ
> > > routing to PCI for certain models. I don't really like this approach.
> >
> > I have not looked at the most recent 2.5.* kernels but if that is true
> > then you're right, it is ill conceived.
>
> 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.
Red Hat "pushes" exactly what the Linux community supports:
This is also called "tracking upstream" and/or "working with the Linux
community, and following the Linux community's decisions." This is
_not_ a political situation at all. We simply ship what the community
supports. Red Hat would not be good "open source citizens" if they did
otherwise.
Taking off my Red hat, and donning my "personal opinion" hat, I think
the kernel cardbus support has been very effectively. It allows drivers
such as tulip and 8139too and epic100 and 3c59x to Just Work(tm),
without any modification besides PCI id table updates. Nothing external
required. That's a huge boon to programmers and maintainers.
Jeff
next prev parent reply other threads:[~2003-03-03 20:21 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 [this message]
2003-03-03 20:56 ` David Hinds
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=20030303203115.GD6615@gtf.org \
--to=jgarzik@pobox.com \
--cc=dahinds@users.sourceforge.net \
--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