From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Voyager GX color mapping
Date: Tue, 14 Dec 2004 18:40:35 +0100 [thread overview]
Message-ID: <41BF2593.7000709@anagramm.de> (raw)
In-Reply-To: <Pine.GSO.4.61.0412141818150.10558@waterleaf.sonytel.be>
Hi, Geert!
> I wrote `fbtest', not `fbset' ;-)
Okay... I will get it... very soon, tomorrow :-)
>>Well, whenever I change the (yet hardcoded) structs in the driver,
>>fbset -fb /dev/fb2 shows me the correct (changed) values.
>>But there is no change in X at all if I play around with the values.
>>Is it possible that X doesn't get my fb_var_screeninfo? Maybe I need
>>to check xorg.cfg again...
>
>
> X may try to change the values again. If you're driver allows that (like it
> seem to do, as per your description above), it may become confusion. Please
> don't allow to change the bitfields in your driver, only allow the values that
> the hardware does support.
Okay... interesting... How does it (try and fail to) change it?
Through IOCTL FBIOPUT_VSCREENINFO? Can I get more debug info out of it?
It's all unread-code-land for me yet. My driver might not implement that
yet... Is there good documentation in addition to RTFC?
Thanks again... I'll keep on learning.
Clemens
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-14 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 16:40 Voyager GX color mapping Clemens Koller
2004-12-14 16:46 ` Geert Uytterhoeven
2004-12-14 17:14 ` Clemens Koller
2004-12-14 17:19 ` Geert Uytterhoeven
2004-12-14 17:40 ` Clemens Koller [this message]
2004-12-14 18:55 ` Geert Uytterhoeven
2004-12-14 16:57 ` Paul Mundt
2004-12-14 17:23 ` Clemens Koller
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=41BF2593.7000709@anagramm.de \
--to=clemens.koller@anagramm.de \
--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.