Radeon framebuffer problems i 2.6.0-test6

[Henrik Christian Grove]

Henrik Christian Grove <gr...@sslug.dk> writes:

> Searching through the archives I have found some reports of problems
> with the radeon framebuffer, but done that seems to fully match my
> experiences.

So I forgor the question: Am I doing something totally wrong? Is there
something I can do to make the Radeon framebuffer work?

.Henrik

--
... applications which need to address vast amounts of memory
(e.g., big scientific crankers, large databases, emacs) ...
-- fra en artikel i LWN

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

[Peter Osterlund]

Henrik Christian Grove <gr...@sslug.dk> writes:

> I have an Asus L3800C laptop with a Radeon Mobility 7500 graphics
> chip.
>
> I have made three slightly different 2.6.0-test6 kernels, called
> test6-1, test6-2 and test6-3. The only differences are what framebuffer
> drivers are included. Test6-1 includes both the vga16 driver and the
> radeon driver, test6-2 only includes the radeon driver, and test6-3 only
> includes the vga16 driver.
>
> With test6-2 I get a framebuffer that looks like it has a sync
> problem. Horizontal lines are horizontal, but vertical lines are
> displayed as individual dots, for each horizontal line of pixels 8
> pixels further right.

See http://www.ussg.iu.edu/hypermail/linux/kernel/0308.3/0637.html
That patch fixed the same problem for me.

--
Peter Osterlund - pet...@telia.com
http://w1.894.telia.com/~u89404340

[Peter Chubb]

Try this patch that's been floating around for a while.

Ani, can you please push this patch to Linus? It fixes the Radeon
problems for a lot of people.

===== drivers/video/radeonfb.c 1.30 vs edited =====
--- 1.30/drivers/video/radeonfb.c Fri Aug 1 01:58:45 2003
+++ edited/drivers/video/radeonfb.c Tue Sep 9 13:18:36 2003
@@ -2090,7 +2090,7 @@

}
/* Update fix */
- info->fix.line_length = rinfo->pitch*64;
+ info->fix.line_length = mode->xres_virtual*(mode->bits_per_pixel/8);
info->fix.visual = rinfo->depth == 8 ? FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_DIRECTCOLOR;

#ifdef CONFIG_BOOTX_TEXT

[Pontus Fuchs]

Hi,

Quoting Peter Chubb <pe...@chubb.wattle.id.au>:
> Try this patch that's been floating around for a while.
>
> Ani, can you please push this patch to Linus? It fixes the Radeon
> problems for a lot of people.

In addition I need the following patch for radeonfb to work on my Asus L5.
See http://bugs.xfree86.org/show_bug.cgi?id=561 for more info.

--- radeonfb.c.orig 2003-09-20 11:47:53.000000000 +0200
+++ radeonfb.c 2003-10-01 09:38:23.000000000 +0200
@@ -1099,7 +1099,7 @@
printk("radeonfb: detected DFP panel size from BIOS: %dx%d\n",
rinfo->panel_xres, rinfo->panel_yres);

- for(i=0; i<20; i++) {
+ for(i=0; i<21; i++) {
tmp0 = rinfo->bios_seg + readw(tmp+64+i*2);
if (tmp0 == 0)
break;

Pontus Fuchs

[Henrik Christian Grove]

Peter Chubb <pe...@chubb.wattle.id.au> writes:

> Try this patch that's been floating around for a while.

That solved the problem for me.

> Ani, can you please push this patch to Linus?

Please do that.

.Henrik

--
"Done. For future reference - don't anybody else try to send patches as
vi scripts, please. Yes, it's manly, but let's face it, so is
bungee-jumping with the cord tied to your testicles."
-- Linus Torvalds

[Ani Joshi]

My recent experience in patch submission makes me believe that sending
patches to the kernel maintainers is like sending the patch into a vacuum.
I don't care to maintain any of the drivers with my name on them anymore
partly because of such problems. I imagine if you keep posting the patch
to the list it will someday reach kernel.org, since apparently being the
author of a driver doesn't mean your patches will be applied nowdays.

good luck! :)

ani