From: Timothy Miller <miller@techsource.com>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: radeonfb broken
Date: Thu, 15 Apr 2004 17:13:44 -0400 [thread overview]
Message-ID: <407EFB08.6050307@techsource.com> (raw)
In-Reply-To: <20040415202523.GA17316@codeblau.de>
Felix von Leitner wrote:
> I am using the radeonfb on a Radeon 9600 Pro with a TFT display, and
> radeonfb very recently started to give me a picture at all, so I am
> quite happy about that.
>
> However, running mplayer does not work at all on radeonfb. mplayer
> inquires about the color depth, I am using 32 bit color depth for this,
> but radeonfb says it's DirectColor instead of TrueColor, so mplayer
> tries to initialize the palette and fails.
>
> Also, using fbset to set the mode to 1600x1200 fails. The mode is
> changed, but the text console resolution stays the same. Worse, a
> "setfont" changes back to 1024x768.
>
> Also, I cannot view images on console with fbi or fbv.
>
> Felix
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.
next prev parent reply other threads:[~2004-04-15 21:14 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 [this message]
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
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=407EFB08.6050307@techsource.com \
--to=miller@techsource.com \
--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