From: Kyle Moffett <mrmacman_g4@mac.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Herbert Poetzl <herbert@13thfloor.at>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: [Linux-fbdev-devel] Re: funny framebuffer fonts on PowerBook with radeonfb
Date: Mon, 27 Mar 2006 02:24:12 -0500 [thread overview]
Message-ID: <D993BFD8-BB08-4128-93C4-E919817E3C42@mac.com> (raw)
In-Reply-To: <4427900C.7090506@gmail.com>
On Mar 27, 2006, at 02:11:08, Antonino A. Daplas wrote:
> Benjamin Herrenschmidt wrote:
>> On Mon, 2006-03-27 at 05:37 +0200, Herbert Poetzl wrote:
>> Interesting... I suspect there is an endian bug in the new font
>> code that hits odd sized fonts (or non-multiple-of-8 fonts). Can
>> you try enabling 8x8 and 8x16 instead of 6x11 and 7x14 fonts and
>> tell me if those work ?
>>
>> Tony: If my suspition is confirmed, I think that's your call :)
>
> It probably is, a remnant of the console rotation code. If that is
> truly the case, the patch I just sent in another thread should fix it.
I ran into this same bug on my Dual 1GHz Windtunnel G4 with an
upgraded GPU (Radeon 9800) in the 2.6.16-rc4 timeframe. Turning off
the customized console font selection and reverting to the default
list of fonts fixed the problem for me. I think I had the console
rotation config option turned on, but I don't have that config any
more and can't be sure.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2006-03-27 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 0:47 Herbert Poetzl
2006-03-27 1:17 ` Benjamin Herrenschmidt
2006-03-27 3:37 ` Herbert Poetzl
2006-03-27 5:26 ` Benjamin Herrenschmidt
2006-03-27 7:11 ` [Linux-fbdev-devel] " Antonino A. Daplas
2006-03-27 7:24 ` Kyle Moffett [this message]
2006-03-27 11:06 ` Herbert Poetzl
2006-03-27 1:19 ` Antonino A. Daplas
2006-03-27 11:01 ` Herbert Poetzl
2006-03-27 1:24 ` D. Hazelton
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=D993BFD8-BB08-4128-93C4-E919817E3C42@mac.com \
--to=mrmacman_g4@mac.com \
--cc=adaplas@gmail.com \
--cc=adaplas@hotpop.com \
--cc=herbert@13thfloor.at \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®