From: James Bottomley <James.Bottomley@steeleye.com>
To: Andries.Brouwer@cwi.nl
Cc: James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org
Subject: Re: 3c509.c
Date: Wed, 22 Jan 2003 11:44:50 -0500 [thread overview]
Message-ID: <200301221644.h0MGion18794@localhost.localdomain> (raw)
In-Reply-To: Message from Andries.Brouwer@cwi.nl of "Wed, 22 Jan 2003 02:11:26 +0100." <UTC200301220111.h0M1BQg03940.aeb@smtp.cwi.nl>
Andries.Brouwer@cwi.nl said:
> Yes, you are right. But. (I do not have an MCA machine myself, this
> was just from source inspection. Let me grep a bit more.)
> Suppose CONFIG_MCA_LEGACY is not set, and CONFIG_MCA is set. Then, as
> you say, <linux/mca-legacy.h> is not included.
Yes, and unfortunately it does this by default. The idea of CONFIG_MCA_LEGACY
was to have legacy drivers unable to compile like this. However, it seems
that most people who will be trying this don't get the CONFIG_MCA_LEGACY set.
When the option was added, I couldn't come up with a useful scheme to make the
legacy (which is almost all MCA drivers) require CONFIG_MCA_LEGACY (there's a
kernel bug about this too).
However, looking through the source, the 3c509 driver is broken anyway for MCA
(done by the eisa sysfs patches), so I think I can probably just add the extra
pieces to convert it to the new sysfs MCA API.
James
next prev parent reply other threads:[~2003-01-22 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 1:11 3c509.c Andries.Brouwer
2003-01-22 16:44 ` James Bottomley [this message]
2003-01-22 16:57 ` 3c509.c Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-01-22 11:10 3c509.c Andries.Brouwer
2003-01-22 12:13 ` 3c509.c Marc Zyngier
2003-01-21 23:34 3c509.c James Bottomley
2003-01-21 20:45 3c509.c Andries.Brouwer
2003-01-22 9:29 ` 3c509.c Marc Zyngier
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=200301221644.h0MGion18794@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®