From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Kurt Garloff <garloff@suse.de>,
Jochen Friedrich <jochen@scram.de>,
linux-kernel@vger.kernel.org,
Jay Estabrook <Jay.Estabrook@compaq.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: Busmaster DMA broken in 2.4.18 on Alpha
Date: Mon, 11 Mar 2002 17:10:58 +0300 [thread overview]
Message-ID: <20020311171058.A9038@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.NEB.4.33.0203111049580.1675-100000@www2.scram.de> <20020311124511.J2346@nbkurt.etpnet.phys.tue.nl>
In-Reply-To: <20020311124511.J2346@nbkurt.etpnet.phys.tue.nl>; from garloff@suse.de on Mon, Mar 11, 2002 at 12:45:11PM +0100
On Mon, Mar 11, 2002 at 12:45:11PM +0100, Kurt Garloff wrote:
> Unfortunately, your ISA card does not seem to be able to address 32 bits.
> (I guess no non-on-chip ISA adapter will.)
No, the ability to address 32 bits is property of an ISA bridge, not
of any particular ISA card or device. Most alphas do have 32-bit ISA DMA.
For that particular driver the following hack should work.
However, ideally we should have ISA_DMA_MASK in asm/dma.h defined
for all architectures...
Ivan.
--- linux/drivers/net/tokenring/tms380tr.h.orig Fri May 25 20:58:07 2001
+++ linux/drivers/net/tokenring/tms380tr.h Mon Mar 11 15:52:06 2002
@@ -462,7 +462,12 @@ typedef struct {
*/
/* XXX is there some better way to do this? */
+#if defined(__alpha__)
+#define ISA_MAX_ADDRESS (MAX_DMA_ADDRESS - IDENT_ADDR - 1 < 0xffffffff ? \
+ MAX_DMA_ADDRESS - IDENT_ADDR - 1 : 0xffffffff)
+#else
#define ISA_MAX_ADDRESS 0x00ffffff
+#endif
#define PCI_MAX_ADDRESS 0xffffffff
#pragma pack(1)
next prev parent reply other threads:[~2002-03-11 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 9:57 Jochen Friedrich
2002-03-11 11:45 ` Kurt Garloff
2002-03-11 13:53 ` Jochen Friedrich
2002-03-11 14:10 ` Ivan Kokshaysky [this message]
2002-03-11 14:32 ` Jochen Friedrich
2002-03-11 15:02 ` Jay Estabrook
2002-03-11 15:45 ` Alan Cox
2002-03-11 16:04 ` Ivan Kokshaysky
2002-03-11 15:16 ` David S. Miller
2002-03-11 15:44 ` Jay Estabrook
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=20020311171058.A9038@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=Jay.Estabrook@compaq.com \
--cc=garloff@suse.de \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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®