From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org,
linux-fbdev-devel@lists.sourceforge.net,
sparclinux@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
mt1@systella.fr
Subject: Re: [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation
Date: Mon, 02 Jul 2007 20:03:11 +0200 [thread overview]
Message-ID: <46893DDF.1060108@systella.fr> (raw)
In-Reply-To: <20070326.161215.74749546.davem@davemloft.net>
David Miller a écrit :
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Mon, 19 Mar 2007 03:34:25 -0800
>
>> On Mon, 19 Mar 2007 03:19:31 -0700 bugme-daemon@bugzilla.kernel.org wrote:
>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=8232
>>>
>>> Summary: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation
>>> 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 white 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 workstation. On
>>> a U60 (PCI/UPA), I never see it.
>>>
>>> When I launch Xorg, problem goes away.
>
> 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.
>
> Can you test the following patch? Thanks. I'll fire up some of
> my older systems to see if I can reproduce this one.
>
> commit 2c4f1add7dd2747cd79c220c24e1dbc3dc4a315f
> Author: David S. Miller <davem@sunset.davemloft.net>
> Date: Mon Mar 26 16:10:52 2007 -0700
>
> [FFB]: Initialize dac_rev before using it.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> 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) != 0)
> upa_writel(FFB_UCSR_ALL_ERRORS, &fbc->ucsr);
>
> - ffb_switch_from_graph(&all->par);
> -
> + /* Determine the DAC revision, we must do this before calling
> + * ffb_switch_from_graph().
> + */
> dac = all->par.dac;
> upa_writel(0x8000, &dac->type);
> all->par.dac_rev = 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 = 10;
>
> + 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
creator3D UPA freamebuffer...
Regards,
JKB
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-07-02 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703191019.l2JAJVH5018137@fire-2.osdl.org>
2007-03-19 11:34 ` [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation Andrew Morton
2007-03-26 23:12 ` David Miller
2007-03-27 7:54 ` BERTRAND Joël
2007-03-27 8:04 ` David Miller
2007-03-27 8:18 ` BERTRAND Joël
2007-03-27 8:24 ` David Miller
2007-03-27 9:25 ` David Johnson
2007-07-02 18:03 ` BERTRAND Joël [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46893DDF.1060108@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=mt1@systella.fr \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).