From: Christoph Hellwig <hch@infradead.org>
To: Alan Cox <alan@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.orgyy
Subject: Re: PATCH: Further aacraid work
Date: Wed, 16 Jun 2004 22:58:34 +0100 [thread overview]
Message-ID: <20040616215834.GA21072@infradead.org> (raw)
In-Reply-To: <20040616214825.GA29750@devserv.devel.redhat.com>
On Wed, Jun 16, 2004 at 05:48:25PM -0400, Alan Cox wrote:
> On Wed, Jun 16, 2004 at 10:42:57PM +0100, Christoph Hellwig wrote:
> > > Its something I hope to get rid of eventually. In the meantime the GART
> > > define is needed to make it work on AMD64.
> >
> > Well, the code is completely wrong. It must not only go away for AMD64 but
> > for all arches.
>
> The hardware and firmware require knowledge of the host memory layout. They
> also use it. Right now I can't find a portable way to extract this information.
> If you've got any suggestions I'd like to hear them.
>
> Its even worse than it seems too because an IOMMU as in the AMD case changes
> the rules in ways the board simply doesn't expect.
Yikes. This looked like they usual use 32bit dma descriptors if not
enough memory hacks to me. If aacraid is that royally fucked we should
probably add CONFIG_X86 to it.
Never underestimate the braindamage that can happen at Adaptec..
next prev parent reply other threads:[~2004-06-16 21:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 21:04 PATCH: Further aacraid work Alan Cox
2004-06-16 21:33 ` Christoph Hellwig
2004-06-16 21:40 ` Alan Cox
2004-06-16 21:42 ` Christoph Hellwig
2004-06-16 21:48 ` Alan Cox
2004-06-16 21:58 ` Christoph Hellwig [this message]
2004-06-16 22:06 ` Alan Cox
2004-06-29 17:48 ` Byron Stanoszek
2004-06-29 18:27 ` Mark Haverkamp
2004-06-29 18:37 ` Alan Cox
2004-06-30 2:02 ` bm
2004-06-30 16:07 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 12:53 Salyzyn, Mark
2004-06-17 13:07 ` Matthew Wilcox
2004-06-17 13:19 ` Christoph Hellwig
2004-06-17 13:55 ` James Bottomley
2004-06-17 13:32 ` Christoph Hellwig
2004-06-17 14:02 ` Alan Cox
2004-06-17 14:39 Salyzyn, Mark
2004-06-17 14:55 ` James Bottomley
2004-06-17 14:58 ` Alan Cox
2004-06-17 15:15 ` Arjan van de Ven
2004-06-17 19:16 ` James Bottomley
2004-06-17 16:32 ` Clay Haapala
2004-06-17 16:37 ` James Bottomley
2004-06-17 16:46 ` Alan Cox
2004-06-17 15:11 ` Anton Blanchard
2004-06-17 17:54 Salyzyn, Mark
2004-06-17 20:38 ` Alan Cox
2004-06-17 20:48 ` William Lee Irwin III
2004-06-17 20:56 ` James Bottomley
2004-06-18 15:05 ` William Lee Irwin III
2004-06-18 20:32 ` William Lee Irwin III
2004-06-27 17:33 ` James Bottomley
[not found] <286GI-5y3-11@gated-at.bofh.it>
[not found] ` <286Qp-5EU-19@gated-at.bofh.it>
2004-06-17 19:10 ` Andi Kleen
2004-06-17 20:54 ` Alan Cox
2004-06-17 21:13 ` James Bottomley
2004-06-17 21:25 ` Andi Kleen
2004-06-18 15:19 ` Benjamin Herrenschmidt
2004-06-18 5:57 ` Jeff Garzik
2004-06-18 14:07 ` James Bottomley
2004-06-18 15:17 ` Benjamin Herrenschmidt
2004-06-18 20:53 Salyzyn, Mark
2004-06-28 13:17 Salyzyn, Mark
2004-06-29 18:53 Salyzyn, Mark
2004-06-29 19:03 ` Byron Stanoszek
2004-06-29 19:27 Salyzyn, Mark
2004-06-29 20:20 ` Byron Stanoszek
2004-06-29 20:42 ` Alan Cox
2004-06-29 20:55 Salyzyn, Mark
2004-06-29 23:22 ` Byron Stanoszek
2004-06-30 19:52 ` Byron Stanoszek
2004-06-30 19:59 ` Dario
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=20040616215834.GA21072@infradead.org \
--to=hch@infradead.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.orgyy \
/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