From mboxrd@z Thu Jan 1 00:00:00 1970 From: Egbert Eich Subject: Re: Who is stomping PCI config space? Date: Fri, 4 Mar 2005 12:25:47 +0100 Message-ID: <16936.17851.290824.371736@xf14.local> References: <9e4733910503031103552514b9@mail.gmail.com> <1109891245.5611.246.camel@gaston> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit In-Reply-To: benh@kernel.crashing.org wrote on Friday, 4 March 2005 at 10:07:25 +1100 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: xorg-bounces@lists.freedesktop.org Errors-To: xorg-bounces@lists.freedesktop.org Content-Type: text/plain; charset="us-ascii" To: Benjamin Herrenschmidt Cc: Xserver development , fbdev Benjamin Herrenschmidt writes: > > I had a report of something similar with X and a mach64 ... I haven't > yet investigated, but basically, X is using "fbdev" (so no specific > driver) and seem to be disabling memory access to the card, thus blowing > up the kernel fbdev. > Benjamin, I faintly remember adding code to the Xserver that it wouldn't do this when you only used fbdev drivers. It may do this for setup (ie. probing) as it has no idea about the drivers it is going to encounter. With the new interface I've added we may actually change this. I'm already doing this to determine if I need to enable PIO. I need to look at this code again, though. Egbert.