linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-fbdev@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] cyber2000fb: fix machine hang on module load
Date: Sat, 31 Jul 2010 21:21:33 +0000	[thread overview]
Message-ID: <4C5493DD.7010402@garzik.org> (raw)
In-Reply-To: <201007312255.30729.linux@rainbow-software.org>

On 07/31/2010 04:55 PM, Ondrej Zary wrote:
> I was testing two CyberPro 2000 based PCI cards on x86 and the machine always
> hanged completely when the cyber2000fb module was loaded. It seems that the
> card hangs when some registers are accessed too quickly after writing RAMDAC
> control register. With this patch, both card work.
>
> Add delay after RAMDAC control register write to prevent hangs on module load.
>
> Signed-off-by: Ondrej Zary<linux@rainbow-software.org>
>
> --- linux-2.6.35-rc2-orig/drivers/video/cyber2000fb.c	2010-06-06 05:43:24.000000000 +0200
> +++ linux-2.6.35-rc3/drivers/video/cyber2000fb.c	2010-07-27 23:12:37.000000000 +0200
> @@ -436,6 +436,8 @@ static void cyber2000fb_write_ramdac_ctr
>   	cyber2000fb_writeb(i | 4, 0x3cf, cfb);
>   	cyber2000fb_writeb(val, 0x3c6, cfb);
>   	cyber2000fb_writeb(i, 0x3cf, cfb);
> +	/* prevent card lock-up observed on x86 with CyberPro 2000 */
> +	cyber2000fb_readb(0x3cf, cfb);
>   }

IIRC, cyber2000 is basically an S3 graphics chip.  When working on s3fb, 
over a decade ago, ISTR needing a lot of MMIO register flushes -- dummy 
register reads -- to flush out just-written register writes.



  reply	other threads:[~2010-07-31 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31 20:55 [PATCH 1/3] cyber2000fb: fix machine hang on module load Ondrej Zary
2010-07-31 21:21 ` Jeff Garzik [this message]
2010-07-31 21:25   ` Russell King - ARM Linux
2010-07-31 22:37     ` Jeff Garzik
2010-07-31 22:51       ` Russell King - ARM Linux

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=4C5493DD.7010402@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linux@rainbow-software.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).