From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] IP28 support
Date: Thu, 29 Nov 2007 10:58:44 +0100 [thread overview]
Message-ID: <20071129095844.GA9106@alpha.franken.de> (raw)
In-Reply-To: <20071128143459.GA22943@linux-mips.org>
On Wed, Nov 28, 2007 at 02:34:59PM +0000, Ralf Baechle wrote:
> > diff --git a/include/asm-mips/dma.h b/include/asm-mips/dma.h
> > index 833437d..80caf6b 100644
> > --- a/include/asm-mips/dma.h
> > +++ b/include/asm-mips/dma.h
> > @@ -88,6 +88,9 @@
> > /* Horrible hack to have a correct DMA window on IP22 */
> > #include <asm/sgi/mc.h>
> > #define MAX_DMA_ADDRESS (PAGE_OFFSET + SGIMC_SEG0_BADDR + 0x01000000)
> > +#elif defined(CONFIG_SGI_IP28)
> > +#include <asm/sgi/mc.h>
> > +#define MAX_DMA_ADDRESS (PAGE_OFFSET + SGIMC_SEG1_BADDR + 0x01000000)
> > #else
> > #define MAX_DMA_ADDRESS (PAGE_OFFSET + 0x01000000)
> > #endif
>
> I've always been wondering if the even the IP22 segment was correct at
> all. Afair nobody ever had (E)ISA DMA working on Indigo 2 so that code
> is a shot into the dark. Of course for now it's the sanest thing to
> assume that IP28 is the same as the "classic" Indigo 2.
I've changed that in the updated IP28 patch. I don't see a way to
support ISA busmaster devices, because they will generate a physical
address between 0 and 0x1000000, which will only hit the 512 KB
mirrored RAM. Anything which uses ISA slave DMA is able to address
the full 32bit address space.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2007-11-29 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:40 [PATCH] IP28 support Thomas Bogendoerfer
2007-11-28 1:33 ` peter fuerst
2007-11-29 10:01 ` Thomas Bogendoerfer
2007-11-28 14:34 ` Ralf Baechle
2007-11-29 9:58 ` Thomas Bogendoerfer [this message]
2007-11-29 12:15 ` Ralf Baechle
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=20071129095844.GA9106@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.