From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965367AbXG1AwU (ORCPT ); Fri, 27 Jul 2007 20:52:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S938237AbXG1AwM (ORCPT ); Fri, 27 Jul 2007 20:52:12 -0400 Received: from wa-out-1112.google.com ([209.85.146.177]:25609 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932985AbXG1AwL (ORCPT ); Fri, 27 Jul 2007 20:52:11 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=uRN1Y5rHHwzKW5ygBnDbwJoXWdR+JsoJ5WnXAeu25SoAnu1oGgqqql86zVtR0sNrMvfBRHLgrMTAA/qm+XYX/nmfjVwNedfhe8e9Br/BCRb0D3X1spIb0jW7BtMpvrW+pRfhiPgzsAyHMeSQqx3c31eqHwrRL2ClgOvghU88+xc= Subject: Re: Problems with framebuffer in 2.6.22-git17 From: "Antonino A. Daplas" To: Adrian McMenamin Cc: Adrian McMenamin , linux-kernel@vger.kernel.org, lethal@users.sourceforge.net In-Reply-To: <92a12cdb0707271732l1d61f0aajfbd72c62d7ded3b6@mail.gmail.com> References: <92a12cdb0707221141i4398d6fdxa7994c5f1f809b0a@mail.gmail.com> <1185146563.6370.8.camel@daplas> <8b67d60707241445l2764d9f1odb72848342135048@mail.gmail.com> <1185406433.5046.23.camel@daplas> <92a12cdb0707271247s727993b8i33999a9652b2ca20@mail.gmail.com> <92a12cdb0707271318t141ee32bs69cb9dab22eabba2@mail.gmail.com> <1185571890.26603.7.camel@daplas> <92a12cdb0707271525i46970157ke1b2b2e6575682d6@mail.gmail.com> <1185578576.26603.16.camel@daplas> <92a12cdb0707271732l1d61f0aajfbd72c62d7ded3b6@mail.gmail.com> Content-Type: text/plain Date: Sat, 28 Jul 2007 08:52:04 +0800 Message-Id: <1185583925.26603.24.camel@daplas> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2007-07-28 at 01:32 +0100, Adrian McMenamin wrote: > On 28/07/07, Antonino A. Daplas wrote: > > On Fri, 2007-07-27 at 23:25 +0100, Adrian McMenamin wrote: > > > On 27/07/07, Antonino A. Daplas wrote: > > > > On Fri, 2007-07-27 at 21:18 +0100, Adrian McMenamin wrote: > > > > > On 27/07/07, Adrian McMenamin wrote: > > > > > > > > > > > With the patch reverted and 24bpp, it oopses before freezing (with two > > > > > > odd looking boot logos on the screen): > > > > > > > > > > > Tested this further and it fails on: > > > > > > > > > > rev = fb_readl(par->mmio_base + 0x04); > > > > > > > > Doubtful if this line is the point of failure, this line is executed > > > > only once, on initialization. > > > > > > > > > par->mmio_base is corrupted in some way during the call to > > > register_framebuffer - still investigating how/why. > > > > Possible, par->mmio_base is the last field in struct pvr2fb_par, > > after that is the pseudo_palette. The oops did not manifest when the > > pseudo_palette was written as u16, but oops'ed when written as u32. > > Memory alignment problems? > > > > Try the patch I posted before, might help. > > > Apologies, missed the patch before. > > With the patch applied the Dreamcast no longer crashes or locks with > either 16, 24 or 32 bpp, so that's good. > > With 24bpp everything is doubled up (eg two boot logos on screen) and > about twice (?) the size it should be - though with a black screen. > > With 32 bpp everything is about 4 (?) times the size it should be and > all on a yellow background. > > With 16bpp then everything is on a blue background as before, but is > also the correct size (as before). Is this with commit a66ad56eb2c9644717da4d7f05f971d6786145e3 reverted? Reapply this commit again, it might (fingers crossed) correct the color problem. As to your display doubling/quadrupling with bpp 24/32, I don't have any answers (no hardware) though it seems to be a framebuffer pitch/display width mismatch. Tony