From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com, irda-users@lists.sourceforge.net,
jt@hpl.hp.com, the_nihilant@autistici.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Drop ISA dependencies from IRDA drivers
Date: Thu, 15 Jul 2004 12:48:07 -0400 [thread overview]
Message-ID: <40F6B547.7050800@pobox.com> (raw)
In-Reply-To: <m34qo96x8m.fsf@averell.firstfloor.org>
Andi Kleen wrote:
> http://bugme.osdl.org/show_bug.cgi?id=3077
>
> Some IRDA chipsets currently don't work on x86-64, because
> they're dependent on CONFIG_ISA and x86-64 doesn't set this.
> CONFIG_ISA means real ISA slots, and I doubt these chips
> come on real ISA cards, so I just removed the bogus
> dependency.
Honestly, the issue and patch need more thought, IMO.
Regardless of theory, CONFIG_ISA is currently also used to indicate
legacy ISA devices that are today integrated into southbridges.
And with legacy ISA devices still around, I don't see a whole lot of
value in differentiating between "I have ISA slots" and "I have ISA
devices".
Jeff
next prev parent reply other threads:[~2004-07-15 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 16:39 [PATCH] Drop ISA dependencies from IRDA drivers Andi Kleen
2004-07-15 16:48 ` Jeff Garzik [this message]
2004-07-15 20:50 ` Andi Kleen
2004-07-15 21:00 ` Jeff Garzik
2004-07-15 21:55 ` Andi Kleen
[not found] ` <20040715215552.GA46635-h9bWGtP8wOw@public.gmane.org>
2004-07-15 22:32 ` Martin Diehl
2004-07-15 22:42 ` Jean Tourrilhes
[not found] ` <20040715224235.GA5164-yAE0UhLNZJawPNPzzlOzwdBPR1lH4CV8@public.gmane.org>
2004-07-15 22:57 ` Martin Diehl
2004-07-16 5:45 ` Andi Kleen
2004-07-16 6:19 ` Martin Diehl
2004-07-16 6:19 ` Andi Kleen
2004-07-16 6:33 ` Martin Diehl
2004-07-15 22:35 ` Jean Tourrilhes
2004-07-16 5:36 ` Andi Kleen
[not found] ` <m34qo96x8m.fsf-uMLt6ZyWIM1XD82W0jV7G5GkACoKc3Ta@public.gmane.org>
2004-07-15 17:00 ` Jean Tourrilhes
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=40F6B547.7050800@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@muc.de \
--cc=irda-users@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=the_nihilant@autistici.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;
as well as URLs for NNTP newsgroup(s).