From: Ondrej Zajicek <santiago@mail.cz>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Framebuffer questions
Date: Wed, 15 Mar 2006 22:10:22 +0100 [thread overview]
Message-ID: <20060315211022.GA4474@localhost.localdomain> (raw)
Hello
I have several questions about fbdev. I already read FB-FAQ, most docs
in Documentation/fb/*, linux/fb.h and some messages in archive of this
mailing list.
- I understood that if i want to change videomode then i should set
all items in struct fb_var_screeninfo, call ioctl FBIOPUT_VSCREENINFO,
driver considers wanted parameters and if exactly this mode or mode
with more bits_per_pixel or greater some bitfield.length is supported,
then mode is changed, otherwise change is rejected. If change is
successfull, then i should call ioctl FBIOGET_VSCREENINFO and
FBIOGET_FSCREENINFO to get information about real framebuffer
structure. Is this correct?
- Should i really set all fields? For example offset and msb_right
parts of red, green, blue and transp. I usually don't care of this
so i want to set some DONT_CARE value. Or are these items always
ignored so i needn't set anything?
- If i have to supply complete mode timings for videomode change
why there is modedb.c and mode lines stored inside drivers?
- I see there is FB_TYPE_TEXT mode (assume for standard text mode).
what should i set in struct fb_var_screeninfo to get this mode?
If i grep drivers/video for it, i get it occurs only in vga16fb.
Is there some deep reason for this or just programmers of other
fb drivers don't care about text mode?
- Is there some possibility to get list of possible framebuffer
videomodes? Or just list of possible 'structural' framebuffer
configurations (type,visual,bpp,r/g/b)? (i hope that usually this is
ortogonal to resolution and timings setting - suppose have enough ram).
I know about FB_ACTIVATE_TEST but use iterative binary search to
find all video modes isn't sane idea :-)
- Is there description of fb sysfs interface anywhere?
- Is there description of specific framebuffer formats for
various FB_TYPE_* and FB_AUX_* anywhere?
- I found that with vga16fb i can access just first plane.
Is it possible to switch planes from userspace and without
interaction with VGA registers?
- What exactly is supposed to do FB_SYNC_BROADCAST ?
- In include/fb.h there is:
#define FB_VISUAL_PSEUDOCOLOR 3 /* Pseudo color (like atari) */
Is there some deep sense in remark '(like atari)' or is this well-known
basic palette visual mode?
I hope i can get some answers or hints.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@mail.cz, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-15 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 21:10 Ondrej Zajicek [this message]
2006-03-16 1:20 ` Framebuffer questions Antonino A. Daplas
2006-03-16 10:17 ` Ondrej Zajicek
2006-03-16 21:26 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2008-02-09 21:12 framebuffer questions Scott D. Davilla
2008-02-10 11:11 ` Geert Uytterhoeven
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=20060315211022.GA4474@localhost.localdomain \
--to=santiago@mail.cz \
--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.