From: Ani Joshi <ajoshi@unixbox.com>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Henrik Christian Grove <grove@sslug.dk>, linux-kernel@vger.kernel.org
Subject: Re: Radeon framebuffer problems i 2.6.0-test6
Date: Wed, 1 Oct 2003 15:20:30 -0700 (PDT) [thread overview]
Message-ID: <20031001151529.D57653@shell.unixbox.com> (raw)
In-Reply-To: <16250.4701.976132.141380@wombat.chubb.wattle.id.au>
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
On Wed, 1 Oct 2003, Peter Chubb wrote:
>
>
> 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
>
next prev parent reply other threads:[~2003-10-01 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 20:12 Radeon framebuffer problems i 2.6.0-test6 Henrik Christian Grove
2003-09-30 22:05 ` Peter Osterlund
2003-09-30 23:31 ` Peter Chubb
2003-10-01 8:03 ` Pontus Fuchs
2003-10-01 9:02 ` Henrik Christian Grove
2003-10-01 22:20 ` Ani Joshi [this message]
[not found] <Bz8D.La.11@gated-at.bofh.it>
2003-09-30 21:03 ` Henrik Christian Grove
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=20031001151529.D57653@shell.unixbox.com \
--to=ajoshi@unixbox.com \
--cc=grove@sslug.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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.