From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [Linux-fbdev-devel] Re: 2.6.11-rc5 Date: Sat, 26 Feb 2005 00:30:43 +0100 Message-ID: <20050225233043.GA16187@suse.de> References: <20050224145049.GA21313@suse.de> <1109287708.15026.25.camel@gaston> <20050225070813.GA13735@suse.de> <1109316551.14993.63.camel@gaston> <20050225172945.GA31211@suse.de> <20050225202423.GA24282@suse.de> <20050225212157.GA31227@suse.de> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20050225212157.GA31227@suse.de> Sender: linux-kernel-owner@vger.kernel.org List-Id: , Kernel Mailing List On Fri, Feb 25, Olaf Hering wrote: > On Fri, Feb 25, Olaf Hering wrote: > > > On Fri, Feb 25, James Simmons wrote: > > > > > > > > > cfb_imageblit(320) dst1 fa51a800 base e0b80000 bitstart 1999a800 > > > > fast_imageblit(237) s daea4000 dst1 fa51a800 > > > > fast_imageblit(269) j 1 fa51a800 0 > > > > Unable to handle kernel paging request at virtual address fa51a800 > > > > > > > > is bitstart incorrect or is the thing just not (yet) mapped? > > > > > > Looks like the screen_base is not mapped to. > > > > rc3 worked ok, rc4 does not. testing the -bk snapshots now. > > bk8 works, bk9 breaks, it contains the radeonfb update. > it works ok if the driver is compiled into the kernel. modedb = rinfo->mon1_modedb; passes some shit to fb_find_mode() which kills my screen(1) when DPRINTK is enabled. it dies because bitstart relies on xres_virtual which is 0xcccccc or whatever.