From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: fbcon woes with closed source framebuffer kernel module
Date: Mon, 19 Sep 2005 07:03:04 +0800 [thread overview]
Message-ID: <432DF228.8080206@gmail.com> (raw)
In-Reply-To: <196b7d310509160927584f8130@mail.gmail.com>
Lior Balkohen wrote:
> i don't think so:
>
> nm head.ko | grep pfb
> 000125bc t pfb_check_var
> 00003a28 d pfb_default
> 00000000 t pfb_fix
> 00012c50 t pfb_pan_display
> 0001edb0 b pfb_pseudo_palette
> 00012798 t pfb_set_par
> 00012af4 t pfb_setcolreg
That's okay, it's probably using the generic functions, cfb_imageblit,
cfb_copyarea, and cfb_fillrect. Check lsmod, or grep for imageblit,
copyarea and fillrect.
>
>> Check the output of fbset -i and post it here.
>
> /tmp > ./fbset -i
>
> mode "720x576-171"
> # D: 50.000 MHz, H: 54.825 kHz, V: 170.793 Hz
> geometry 720 576 720 576 8
> timings 20000 64 64 32 32 64 2
> laced true
> rgba 8/16,8/8,8/0,8/24
> endmode
>
> Frame buffer device information:
> Name : Pallas FB
> Address : 0xa0901000
> Size : 2093056
> Type : PACKED PIXELS
> Visual : PSEUDOCOLOR
> XPanStep : 1
> YPanStep : 1
> YWrapStep : 1
> LineLength : 720
> Accelerator : No
>
I don't think this is correct. It describes RGBA8888 as
pseudocolor (indexed palette). Try doing an fbset -depth 8
and check the fbset -i output again.
Tony
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-09-18 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 13:24 fbcon woes with closed source framebuffer kernel module Lior Balkohen
2005-09-16 13:59 ` Antonino A. Daplas
2005-09-16 16:27 ` Lior Balkohen
2005-09-18 23:03 ` Antonino A. Daplas [this message]
2005-09-19 6:31 ` Geert Uytterhoeven
2005-09-19 9:55 ` Antonino A. Daplas
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=432DF228.8080206@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.