From: Adam Radford <aradford@3WARE.com>
To: "'Mark Watts'" <m.watts@eris.qinetiq.com>,
Terje Kvernes <terjekv@math.uio.no>
Cc: Andre Tomt <andre@tomt.net>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: Serial ATA (SATA) status report
Date: Thu, 26 Feb 2004 11:08:15 -0800 [thread overview]
Message-ID: <A1964EDB64C8094DA12D2271C04B8126F8C95C@tabby> (raw)
The only 'issue' running in 64-bit mode on AMD-64 I know of was where there
was data corruption when the IOMMU flushing scheme changed. I think Andi
sent out an email
where this was reverted. If it wasn't, all you need to do is run with
iommu=fullflush
and you shouldn't have any other trouble.
What other issues are there?
-Adam
-----Original Message-----
From: Mark Watts [mailto:m.watts@eris.qinetiq.com]
Sent: Thursday, February 26, 2004 7:56 AM
To: Terje Kvernes
Cc: Andre Tomt; Linux Kernel
Subject: Re: Serial ATA (SATA) status report
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> the 3w-xxxx-module works well enough in 32bit mode on AMD64. sadly
> enough, we have had some other issues with 64bit mode, but the
> _driver_ seems to load there as well.
Do these 'issues' prevent the cards from being used at all in 64bit mode on
AMD-64?
We'd really like to use the 4-port SATA 3Ware card on a Tyan Thunder K8W
(S2885) but it'd be a bit of a waste if we can only use it in 32bit mode. (I
assume 32bit mode means you compile for i686 instead of AMD-64 ?)
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAPhcCBn4EFUVUIO0RAgYlAKCIdWX36mkFko8kdlyhCtzTcpAgsQCeOCc4
hZYOYnuFKuZLa5v4KJ7XGjI=
=M/Ej
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
DISCLAIMER: The information contained in this electronic mail transmission
is intended by 3ware for the use of the named individual or entity to which
it is directed and may contain information that is confidential or
privileged and should not be disseminated without prior approval from 3ware
next reply other threads:[~2004-02-26 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 19:08 Adam Radford [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-26 6:28 Kyle Wong
2004-02-26 2:34 Jeff Garzik
2004-02-26 2:54 ` Mike Fedyk
2004-02-26 3:09 ` Jeff Garzik
2004-02-26 9:13 ` Mark Watts
2004-02-26 13:19 ` Andre Tomt
2004-02-26 14:23 ` Mark Watts
2004-02-26 15:33 ` Terje Kvernes
2004-02-26 15:55 ` Mark Watts
2004-02-26 20:11 ` Terje Kvernes
2004-02-27 18:56 ` Mark
2004-02-26 16:00 ` Jeff Garzik
2004-02-28 14:49 ` Justin Cormack
2004-03-01 8:05 ` Michael Knigge
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=A1964EDB64C8094DA12D2271C04B8126F8C95C@tabby \
--to=aradford@3ware.com \
--cc=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.watts@eris.qinetiq.com \
--cc=terjekv@math.uio.no \
/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®