public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Felix von Leitner <felix-kernel@fefe.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb broken
Date: Fri, 16 Apr 2004 12:06:22 -0400	[thread overview]
Message-ID: <4080047E.9050804@techsource.com> (raw)
In-Reply-To: <1082079792.2499.229.camel@gaston>



Benjamin Herrenschmidt wrote:
>>What annoys me most about the Radeon driver is the off-by-one error in 
>>the bmove routine.  Whenever text is copied to the right or down, it 
>>gets positioned incorrectly.  I posted the fix, but no one paid attention.
> 
> 
> Mayb it was just "missed" in the flow of hundreds of mails that go
> through this list. Can you re-sent it to me, and also precise which
> kernel version it applies to ?
> 
> Ben.


BTW, now that we're on the topic of Radeon, could someone tell me how to 
tell the kernel the default resolution to use when initializing the 
console?

When using a CRT, it defaults to 640x480.  When I use my Planar PQ191 
19" 1280x1024 monitor, it defaults to 1024x768.  I want it to default to 
1280x1024.  There's a tool, fbset or something like that, which I can 
use AFTER bootup, but trying to put that into init causes all sorts of 
conflicts.  I need to be able to tell the kernel, either at compile time 
or on the boot command line.


Moving off topic, my cries for help from the XFree86 people also seem to 
have gotten lost in the flow of hundreds of usenet messages.  Try as I 
might, I cannot seem to get XFree86 to talk to my monitor at anything 
other than 60Hz.  Even though LCD monitors have a persistent image, 
increasing the frame rate CAN reduce motion blur slightly.


Thanks.


  parent reply	other threads:[~2004-04-16 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 20:25 radeonfb broken Felix von Leitner
2004-04-15 21:13 ` Timothy Miller
2004-04-16  1:43   ` Benjamin Herrenschmidt
2004-04-16 15:58     ` Timothy Miller
2004-04-17  0:22       ` Benjamin Herrenschmidt
2004-04-19 14:18         ` Timothy Miller
2004-04-19 22:36           ` Benjamin Herrenschmidt
2004-04-16 16:06     ` Timothy Miller [this message]
2004-04-16 16:40       ` Randy.Dunlap
     [not found]   ` <20040415152507.3a0b014d.akpm@osdl.org>
2004-04-16 15:56     ` Timothy Miller
2004-04-16 20:34       ` James Simmons
2004-04-16 21:05         ` Timothy Miller
2004-04-19  2:18   ` David Eger
2004-04-16  1:46 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 21:09 David Eger

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=4080047E.9050804@techsource.com \
    --to=miller@techsource.com \
    --cc=benh@kernel.crashing.org \
    --cc=felix-kernel@fefe.de \
    --cc=linux-kernel@vger.kernel.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