From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Felix von Leitner <felix-kernel@fefe.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb broken
Date: Fri, 16 Apr 2004 11:46:51 +1000 [thread overview]
Message-ID: <1082080010.5657.234.camel@gaston> (raw)
In-Reply-To: <20040415202523.GA17316@codeblau.de>
> 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.
It is DirectColor and setting the palette should work. If it doesn't
then we indeed have a bug, but so far, I didn't have any problems
with MacOnLinux which does fbdev and sets the palette properly not
with XFree which does also set the palette. In DirectColor, the
palette is actually a gamma table.
> 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.
Yes, that's not a radeonfb problem. The current 2.6 fbcon driver is
completely broken in this regard imho. It tries to adapt the display
mode on stty and setfont, which usually doesn't work properly since it
can't calculate supported modes properly (well... radeonfb sort of can
but it's the only one who can and there are still issues). On the
other hand, it doesn't adapt properly to changes done via fbset.
I have done some workarounds for this but they triggered other bugs
in the fbcon driver at that time, some of them causing memory
corruption, so I didn't commit my changes upstream.
A bunch of this should have been fixed by now, I need to re-sync with
James Simmons and see if I can make that to work now.
> Also, I cannot view images on console with fbi or fbv.
>
> Felix
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2004-04-16 1:55 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
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 [this message]
-- 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=1082080010.5657.234.camel@gaston \
--to=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