From: "Antonino A. Daplas" <adaplas@gmail.com>
To: DervishD <lkml@dervishd.net>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: tdfx framebuffer garbles display in 2.6.19.5
Date: Wed, 28 Feb 2007 07:09:15 +0800 [thread overview]
Message-ID: <1172617755.13422.0.camel@daplas> (raw)
In-Reply-To: <20070226203223.GA161@DervishD>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Mon, 2007-02-26 at 21:32 +0100, DervishD wrote:
> Hi Antonino :)
>
> * Antonino A. Daplas <adaplas@gmail.com> dixit:
> > On Mon, 2007-02-26 at 18:13 +0100, DervishD wrote:
> > That's why tdfxb limits the vyres to a maximum of 4096. As to why the
> > problem disappeared just by changing this parameter, that I too don't
> > know.
>
> Probably setting it back to 4096 will make the problem reappear.
> Right now I cannot test, but I'll make some experiments.
>
Can you try this patch? It might help with the screen corruption.
Tony
[-- Attachment #2: tdfxfb_delay.diff --]
[-- Type: text/x-patch, Size: 699 bytes --]
diff --git a/drivers/video/tdfxfb.c b/drivers/video/tdfxfb.c
index 689ce02..bb3ca71 100644
--- a/drivers/video/tdfxfb.c
+++ b/drivers/video/tdfxfb.c
@@ -284,7 +284,8 @@ static inline void banshee_make_room(str
{
/* Note: The Voodoo3's onboard FIFO has 32 slots. This loop
* won't quit if you ask for more. */
- while((tdfx_inl(par, STATUS) & 0x1f) < size-1);
+ while((tdfx_inl(par, STATUS) & 0x1f) < size-1)
+ mdelay(5);
}
static int banshee_wait_idle(struct fb_info *info)
@@ -297,7 +298,9 @@ static int banshee_wait_idle(struct fb_i
while(1) {
i = (tdfx_inl(par, STATUS) & STATUS_BUSY) ? 0 : i + 1;
- if(i == 3) break;
+ if(i == 3)
+ break;
+ mdelay(5);
}
return 0;
}
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: DervishD <lkml@dervishd.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: tdfx framebuffer garbles display in 2.6.19.5
Date: Wed, 28 Feb 2007 07:09:15 +0800 [thread overview]
Message-ID: <1172617755.13422.0.camel@daplas> (raw)
In-Reply-To: <20070226203223.GA161@DervishD>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Mon, 2007-02-26 at 21:32 +0100, DervishD wrote:
> Hi Antonino :)
>
> * Antonino A. Daplas <adaplas@gmail.com> dixit:
> > On Mon, 2007-02-26 at 18:13 +0100, DervishD wrote:
> > That's why tdfxb limits the vyres to a maximum of 4096. As to why the
> > problem disappeared just by changing this parameter, that I too don't
> > know.
>
> Probably setting it back to 4096 will make the problem reappear.
> Right now I cannot test, but I'll make some experiments.
>
Can you try this patch? It might help with the screen corruption.
Tony
[-- Attachment #2: tdfxfb_delay.diff --]
[-- Type: text/x-patch, Size: 699 bytes --]
diff --git a/drivers/video/tdfxfb.c b/drivers/video/tdfxfb.c
index 689ce02..bb3ca71 100644
--- a/drivers/video/tdfxfb.c
+++ b/drivers/video/tdfxfb.c
@@ -284,7 +284,8 @@ static inline void banshee_make_room(str
{
/* Note: The Voodoo3's onboard FIFO has 32 slots. This loop
* won't quit if you ask for more. */
- while((tdfx_inl(par, STATUS) & 0x1f) < size-1);
+ while((tdfx_inl(par, STATUS) & 0x1f) < size-1)
+ mdelay(5);
}
static int banshee_wait_idle(struct fb_info *info)
@@ -297,7 +298,9 @@ static int banshee_wait_idle(struct fb_i
while(1) {
i = (tdfx_inl(par, STATUS) & STATUS_BUSY) ? 0 : i + 1;
- if(i == 3) break;
+ if(i == 3)
+ break;
+ mdelay(5);
}
return 0;
}
next prev parent reply other threads:[~2007-02-27 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 14:47 tdfx framebuffer garbles display in 2.6.19.5 DervishD
2007-02-26 15:24 ` Antonino A. Daplas
2007-02-26 15:24 ` Antonino A. Daplas
2007-02-26 17:13 ` DervishD
2007-02-26 17:24 ` Antonino A. Daplas
2007-02-26 20:32 ` DervishD
2007-02-27 23:09 ` Antonino A. Daplas [this message]
2007-02-27 23:09 ` Antonino A. Daplas
2007-02-28 10:49 ` DervishD
2007-03-01 16:01 ` DervishD
2007-03-06 1:33 ` Antonino A. Daplas
2007-03-06 1:33 ` Antonino A. Daplas
2007-03-06 6:25 ` DervishD
2007-03-06 6:53 ` Antonino A. Daplas
2007-03-06 11:17 ` DervishD
2007-03-07 10:02 ` DervishD
2007-03-14 9:06 ` [TESTED] " DervishD
2007-03-14 9:06 ` DervishD
2007-02-26 15:24 ` James Simmons
2007-02-26 15:24 ` James Simmons
2007-02-26 17:04 ` DervishD
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=1172617755.13422.0.camel@daplas \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.