From: Andi Kleen <ak@muc.de>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Matthew Wilcox <willy@debian.org>, Andi Kleen <ak@muc.de>,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.6 + Adaptec I2O
Date: 1 Jun 2004 21:25:52 +0200
Date: Tue, 1 Jun 2004 21:25:52 +0200 [thread overview]
Message-ID: <20040601191853.GA63663@colin2.muc.de> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189FAD5143@otce2k03.adaptec.com>
> The management tools could (but doesn't for linux, this is for sake of
> argument) report the driver was built for an i386 processor, yet we
> could be running on an i686 kernel. Other drivers from DPT/Adaptec for
> other operating systems have the same ioctl call populated with the same
> information.
Sounds useless to me. At least for linux you would need to report
a lot more than what you currently do to figure out if the driver
is compatible to a given kernel.
e.g. how the kernel was built (with SMP, without, with PREEMPT etc.,
with what compiler etc.) See what the linux module loader checks.
In addition the distribution vendor may be needed.
Also PROC_SEXIUM is definitely wrong then since an x86-64 driver
is completely different from a i686 driver.
-Andi
next prev parent reply other threads:[~2004-06-01 19:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 18:39 2.6.6 + Adaptec I2O Salyzyn, Mark
2004-06-01 19:25 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-01 19:52 Salyzyn, Mark
2004-06-01 20:29 ` Andi Kleen
2004-06-01 18:27 Salyzyn, Mark
2004-06-01 18:29 ` Matthew Wilcox
2004-06-01 17:25 Salyzyn, Mark
2004-06-01 18:20 ` Andi Kleen
2004-06-01 16:09 Salyzyn, Mark
2004-06-01 15:38 Salyzyn, Mark
2004-06-01 15:54 ` Christoph Hellwig
2004-06-01 15:11 Salyzyn, Mark
2004-06-01 15:20 ` Christoph Hellwig
2004-06-01 15:23 ` Christoph Hellwig
2004-06-02 8:11 ` Leon Toh
2004-06-02 8:16 ` Christoph Hellwig
2004-06-01 17:08 ` Andi Kleen
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=20040601191853.GA63663@colin2.muc.de \
--to=ak@muc.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=willy@debian.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