From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by ozlabs.org (Postfix) with ESMTP id 4AE322BF0E for ; Tue, 11 Jan 2005 05:16:23 +1100 (EST) Received: by wproxy.gmail.com with SMTP id 37so318348wra for ; Mon, 10 Jan 2005 10:16:22 -0800 (PST) Message-ID: <4240b916050110101647cfb8f9@mail.gmail.com> Date: Mon, 10 Jan 2005 19:16:22 +0100 From: Jerome Glisse To: benh@kernel.crashing.org In-Reply-To: <4240b91605010912414a5b1b67@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII References: <4240b916050109072621440269@mail.gmail.com> <20050109160614.GA22839@lst.de> <4240b91605010909463e44bba8@mail.gmail.com> <4240b91605010912414a5b1b67@mail.gmail.com> Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org Subject: Re: U3 G5 AGP support patch (v4) Reply-To: Jerome Glisse List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > It seems there is bug somewhere in my agp patch. I was playing with > r300 radeon and > i get a hard lockup (quite used to that while playing with r300 thought :() > > But after a bit of investigation it seems to be related to agp. Right now i am > porting an old tools from dri that test agpgart & thus agp. I finally may really > need to totaly split the u3 driver from the old uninorth. > > I will give a deeper look to track down the issue. In the mean time if some > one could test agp & radeon r200 on a g5. You will certainly lockup your g5 > but it should not burn, at least here i just got some smoke ;) > Finally this was because i was doing some nasty stuff elsewhere :) Thus AGP seems to work well, at least over here with some r300 test program using agp :) best, Jerome Glisse