From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= Subject: Re: [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation Date: Mon, 02 Jul 2007 20:03:11 +0200 Message-ID: <46893DDF.1060108@systella.fr> References: <200703191019.l2JAJVH5018137@fire-2.osdl.org> <20070319033425.b0be2d95.akpm@linux-foundation.org> <20070326.161215.74749546.davem@davemloft.net> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20070326.161215.74749546.davem@davemloft.net> Sender: sparclinux-owner@vger.kernel.org List-Id: Cc: akpm@linux-foundation.org, linux-fbdev-devel@lists.sourceforge.net, sparclinux@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, mt1@systella.fr David Miller a =E9crit : > From: Andrew Morton > Date: Mon, 19 Mar 2007 03:34:25 -0800 >=20 >> On Mon, 19 Mar 2007 03:19:31 -0700 bugme-daemon@bugzilla.kernel.org = wrote: >> >>> http://bugzilla.kernel.org/show_bug.cgi?id=3D8232 >>> >>> Summary: Creator3D Framebuffer (sparc64) on Sbus/UPA wor= kstation >>> Kernel Version: ALL 2.6 >>> Status: NEW >>> Severity: normal >>> Owner: jsimmons@infradead.org >>> Submitter: mt1@systella.fr >>> >>> >>> Most recent kernel where this bug did *NOT* occur: 2.4.34.1 >>> Distribution: Debian/testing >>> Hardware Environment: U1E/170 with Creator3D (UPA), U2 with creator= 3D >>> Software Environment: debian without X on U1E, debian with Xorg on = U2 >>> Problem Description: Console is white foreground and blanck backgro= und by >>> default. Sometimes, the screen is cut like this : >>> >>> N | N | N | N >>> --+---+---+--- >>> N | G | G | G >>> --+---+---+--- >>> N | W | W | W >>> --+---+---+--- >>> N | G | G | G >>> >>> >>> where N is a 'normal' console, 'G' a 'like grey' console (black and= white pixels >>> like snow), and 'W' a white console (many white pixels). I have tes= ted some >>> differents Creator3D fb and this trouble only occurs on Sbus/UPA wo= rkstation. On >>> a U60 (PCI/UPA), I never see it. >>> >>> When I launch Xorg, problem goes away. >=20 > A quick audit found that we're using the ->dac_rev value before > setting it properly. One difference between the older creator > cards and the newer ones is the DAC, so perhaps this was the > bug. >=20 > Can you test the following patch? Thanks. I'll fire up some of > my older systems to see if I can reproduce this one. >=20 > commit 2c4f1add7dd2747cd79c220c24e1dbc3dc4a315f > Author: David S. Miller > Date: Mon Mar 26 16:10:52 2007 -0700 >=20 > [FFB]: Initialize dac_rev before using it. > =20 > Signed-off-by: David S. Miller >=20 > diff --git a/drivers/video/ffb.c b/drivers/video/ffb.c > index 15854ae..3c01f45 100644 > --- a/drivers/video/ffb.c > +++ b/drivers/video/ffb.c > @@ -948,8 +948,9 @@ static int ffb_init_one(struct of_device *op) > if ((upa_readl(&fbc->ucsr) & FFB_UCSR_ALL_ERRORS) !=3D 0) > upa_writel(FFB_UCSR_ALL_ERRORS, &fbc->ucsr); > =20 > - ffb_switch_from_graph(&all->par); > - > + /* Determine the DAC revision, we must do this before calling > + * ffb_switch_from_graph(). > + */ > dac =3D all->par.dac; > upa_writel(0x8000, &dac->type); > all->par.dac_rev =3D upa_readl(&dac->value) >> 0x1c; > @@ -960,6 +961,8 @@ static int ffb_init_one(struct of_device *op) > if (all->par.flags & FFB_FLAG_AFB) > all->par.dac_rev =3D 10; > =20 > + ffb_switch_from_graph(&all->par); > + > /* Unblank it just to be sure. When there are multiple > * FFB/AFB cards in the system, or it is not the OBP > * chosen console, it will have video outputs off in Hello, Bad news... This patch doesn't work for 2.6.21.3 and my U2 with=20 creator3D UPA freamebuffer... Regards, JKB - To unsubscribe from this list: send the line "unsubscribe sparclinux" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= Date: Mon, 02 Jul 2007 18:03:11 +0000 Subject: Re: [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Message-Id: <46893DDF.1060108@systella.fr> List-Id: References: <200703191019.l2JAJVH5018137@fire-2.osdl.org> <20070319033425.b0be2d95.akpm@linux-foundation.org> <20070326.161215.74749546.davem@davemloft.net> In-Reply-To: <20070326.161215.74749546.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: David Miller Cc: akpm@linux-foundation.org, linux-fbdev-devel@lists.sourceforge.net, sparclinux@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, mt1@systella.fr David Miller a =E9crit : > From: Andrew Morton > Date: Mon, 19 Mar 2007 03:34:25 -0800 >=20 >> On Mon, 19 Mar 2007 03:19:31 -0700 bugme-daemon@bugzilla.kernel.org wrot= e: >> >>> http://bugzilla.kernel.org/show_bug.cgi?id=8232 >>> >>> Summary: Creator3D Framebuffer (sparc64) on Sbus/UPA worksta= tion >>> Kernel Version: ALL 2.6 >>> Status: NEW >>> Severity: normal >>> Owner: jsimmons@infradead.org >>> Submitter: mt1@systella.fr >>> >>> >>> Most recent kernel where this bug did *NOT* occur: 2.4.34.1 >>> Distribution: Debian/testing >>> Hardware Environment: U1E/170 with Creator3D (UPA), U2 with creator3D >>> Software Environment: debian without X on U1E, debian with Xorg on U2 >>> Problem Description: Console is white foreground and blanck background = by >>> default. Sometimes, the screen is cut like this : >>> >>> N | N | N | N >>> --+---+---+--- >>> N | G | G | G >>> --+---+---+--- >>> N | W | W | W >>> --+---+---+--- >>> N | G | G | G >>> >>> >>> where N is a 'normal' console, 'G' a 'like grey' console (black and whi= te pixels >>> like snow), and 'W' a white console (many white pixels). I have tested = some >>> differents Creator3D fb and this trouble only occurs on Sbus/UPA workst= ation. On >>> a U60 (PCI/UPA), I never see it. >>> >>> When I launch Xorg, problem goes away. >=20 > A quick audit found that we're using the ->dac_rev value before > setting it properly. One difference between the older creator > cards and the newer ones is the DAC, so perhaps this was the > bug. >=20 > Can you test the following patch? Thanks. I'll fire up some of > my older systems to see if I can reproduce this one. >=20 > commit 2c4f1add7dd2747cd79c220c24e1dbc3dc4a315f > Author: David S. Miller > Date: Mon Mar 26 16:10:52 2007 -0700 >=20 > [FFB]: Initialize dac_rev before using it. > =20 > Signed-off-by: David S. Miller >=20 > diff --git a/drivers/video/ffb.c b/drivers/video/ffb.c > index 15854ae..3c01f45 100644 > --- a/drivers/video/ffb.c > +++ b/drivers/video/ffb.c > @@ -948,8 +948,9 @@ static int ffb_init_one(struct of_device *op) > if ((upa_readl(&fbc->ucsr) & FFB_UCSR_ALL_ERRORS) !=3D 0) > upa_writel(FFB_UCSR_ALL_ERRORS, &fbc->ucsr); > =20 > - ffb_switch_from_graph(&all->par); > - > + /* Determine the DAC revision, we must do this before calling > + * ffb_switch_from_graph(). > + */ > dac =3D all->par.dac; > upa_writel(0x8000, &dac->type); > all->par.dac_rev =3D upa_readl(&dac->value) >> 0x1c; > @@ -960,6 +961,8 @@ static int ffb_init_one(struct of_device *op) > if (all->par.flags & FFB_FLAG_AFB) > all->par.dac_rev =3D 10; > =20 > + ffb_switch_from_graph(&all->par); > + > /* Unblank it just to be sure. When there are multiple > * FFB/AFB cards in the system, or it is not the OBP > * chosen console, it will have video outputs off in Hello, Bad news... This patch doesn't work for 2.6.21.3 and my U2 with=20 creator3D UPA freamebuffer... Regards, JKB