DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=R4Dbnb90rHeut7ovxzZZB9kgjAnTZZjeUV/N13g0afy7edoPUSoqd0BotKisbj3oKvU3vIYh6i9Uz4utjPw4HLitY5ImrRqObmI83Banv5AH4kHM5lzM3Iod6IujD/k2fOa63Mif/QcOoO1BAAfzsJq69n9YqEEFZzpFm6jdzOc=
Message-ID: <12c511ca050917233313418638@mail.gmail.com>
Date: Sat, 17 Sep 2005 23:33:57 -0700
From: Tony Luck <tony.luck@gmail.com>
Reply-To: tony.luck@gmail.com
To: "David S. Miller" <davem@davemloft.net>
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Cc: linville@tuxdriver.com, kaos@sgi.com, greg@kroah.com,
       linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
In-Reply-To: <20050917.232304.31192760.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <25288.1126596450@kao2.melbourne.sgi.com>
	 <12c511ca05091708476aa136cd@mail.gmail.com>
	 <20050917155911.GB19854@tuxdriver.com>
	 <20050917.232304.31192760.davem@davemloft.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 746
Lines: 18

> It fixes the problem, but it's a hack, and I, perhaps like Tony,
> personally would like to know why the these IA64 systems break for
> such a simple operation such as writing some base registers with
> values we've probed already.

It does sound odd[1] that you can't rewrite the BARs to the values that
they should already have.  But I'm willing to wait to see what SGI's
solution that fixes this inside arch/ia64/sn/ looks like before making
any judgements.

-Tony

[1] odd == PCI spec violating?
-
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/