linux-mips
[Top] [All Lists]

Re: [PATCH] IP28: fix MC GIOPAR setting

To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH] IP28: fix MC GIOPAR setting
From: peter fuerst <post@pfrst.de>
Date: Fri, 21 Mar 2008 22:07:38 +0100 (CET)
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
In-reply-to: <20080321194737.GA8398@alpha.franken.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.LNX.4.58.0803211535570.423@Indigo2.Peter> <20080321194737.GA8398@alpha.franken.de>
Reply-to: post@pfrst.de
Sender: linux-mips-bounce@linux-mips.org

On Fri, 21 Mar 2008, Thomas Bogendoerfer wrote:

> Date: Fri, 21 Mar 2008 20:47:37 +0100
> From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> To: peter fuerst <post@pfrst.de>
> Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
> Subject: Re: [PATCH] IP28: fix MC GIOPAR setting
>
> On Fri, Mar 21, 2008 at 04:03:16PM +0100, peter fuerst wrote:
> > We must not omit the MASTERGFX setting, unless we want Impact DMA to hang 
> > ;-)
>
> is there a reason to restrict this to IP28 only ?

Would indeed be most surprising, if this isn't appropriate for any Indigo2-
Impact, but don't know for sure.  And can't check, whether it at least doesn't
hurt Non-Impact Indigo2.  Of course, being able to avoid '#ifdef' at all would
be the prettiest alternative.

>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessary a
> good idea.                                                [ RFC1925, 2.3 ]
>
>

<Prev in Thread] Current Thread [Next in Thread>