From: Andi Kleen <ak@suse.de>
To: Jeffrey Baker <jwbaker@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ia32 kernel on amd64 box?
Date: 28 Apr 2003 19:00:35 +0200 [thread overview]
Message-ID: <p73znma36bw.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20030428164248.GA25416@heat.suse.lists.linux.kernel>
Jeffrey Baker <jwbaker@acm.org> writes:
> I was wondering the same thing about peripherals. The
> README in aic79xx driver from adaptec states that the driver
> is supported on x86 only. So I was wary to spec model 39320
> HBAs in x86-64 machines. I'm sure Adaptec is using the term
> "support" in the most corporate sense possible, but what if
> it really does scribble the disk under SuSE 64-bit kernel?
The AIC 7xxx driver works fine. It should work on the same hardware as
79xx.
The biggest AMD64 issue with drivers is normally IOMMU support, but
that only needs to concern you when you have more than 4GB of memory
and the hardware does not support 64bit Addresses. The Adaptec
hardware supports 64bit addresses.
What's a problem is the "Adaptec RAID" - which uses the dpt_i2o driver.
That driver is not 64bit safe and doesn't work and is disabled.
-Andi
next parent reply other threads:[~2003-04-28 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030428164248.GA25416@heat.suse.lists.linux.kernel>
2003-04-28 17:00 ` Andi Kleen [this message]
2003-04-28 16:42 ia32 kernel on amd64 box? Jeffrey Baker
[not found] <20030425214500.GA20221@ncsu.edu.suse.lists.linux.kernel>
[not found] ` <hoof2rghbs.fsf@byrd.suse.de.suse.lists.linux.kernel>
2003-04-28 12:29 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 21:45 jlnance
2003-04-25 21:49 ` Bill Nottingham
2003-04-25 21:56 ` Jamie Lokier
2003-04-25 22:07 ` Timothy Miller
2003-04-25 22:56 ` Bill Nottingham
2003-04-28 8:24 ` Andreas Jaeger
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=p73znma36bw.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=jwbaker@acm.org \
--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;
as well as URLs for NNTP newsgroup(s).