From: Ondrej Zary <linux@rainbow-software.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [resend] cyber2000fb: fix machine hang on module load
Date: Tue, 27 Jul 2010 21:18:55 +0000 [thread overview]
Message-ID: <201007272318.57975.linux@rainbow-software.org> (raw)
In-Reply-To: <20100727162510.GB17099@n2100.arm.linux.org.uk>
On Tuesday 27 July 2010 18:25:11 Russell King - ARM Linux wrote:
> On Tue, Jul 27, 2010 at 03:29:20PM +0200, Ondrej Zary wrote:
> > Hello,
> > 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.
>
> This one on the other hand I think is rather too heavy.
>
> What might be better is to re-code the last register write to use
> the x86 outb_p() stuff to slow it down, rather than using udelay().
> Could you try something along those lines please?
Is this better?
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);
}
static void cyber2000fb_set_timing(struct cfb_info *cfb, struct par_info *hw)
--
Ondrej Zary
prev parent reply other threads:[~2010-07-27 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 13:29 [PATCH] [resend] cyber2000fb: fix machine hang on module load Ondrej Zary
2010-07-27 16:25 ` Russell King - ARM Linux
2010-07-27 21:18 ` Ondrej Zary [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=201007272318.57975.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).