From: David Johnson <dj@david-web.co.uk>
To: David Miller <davem@davemloft.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation
Date: Tue, 27 Mar 2007 10:25:35 +0100 [thread overview]
Message-ID: <200703271025.35767.dj@david-web.co.uk> (raw)
In-Reply-To: <20070326.161215.74749546.davem@davemloft.net>
On Tuesday 27 March 2007 00:12, David Miller wrote:
>
> 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.
>
I've also been seeing this issue, so I can test your fix. Unfortunately this
is not something that reproduces itself reliably, so it may be a while before
I can be sure if the fix has worked.
Thanks,
David.
--
David Johnson
www.david-web.co.uk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-27 9:25 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 [this message]
2007-07-02 18:03 ` BERTRAND Joël
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=200703271025.35767.dj@david-web.co.uk \
--to=dj@david-web.co.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).