From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: sysfs support for framebuffer
Date: Fri, 18 Feb 2005 17:35:25 -0500 [thread overview]
Message-ID: <9e4733910502181435f60371c@mail.gmail.com> (raw)
What are the attributes needed for framebuffers in sysfs?
This is the list I came up with, are there more?
bits_per_pixel - r/w color depth
blank - w set the vesa blank state
color_map - r/w control the color map
console - r/w? map of console number to fb device
cursor - r/w x/y position of the cursor
mode - r/w set the display mode
modes - list of valid modes
pan - r/w x/y of the pan offset
virtual_size - r/w x/y of the virtual size
modes is designed to let a user space root app set the list of valid
modes into the driver
ownership of all other attributes are assigned by pam to the display user
mode must be an entry from the list of modes, this prevents a user
from setting in a damaging mode
The list is based on the current fbdev IOCTLs. All attributes appear
in /sys/class/graphics/fb0/xxxx
Current patch is in the "Patch to add mode setting to sysfs" thread.
fbdev also needs to generate events to let the xserver know if things
have been changed. These can come up through hotplug to dbus.
bits_per_pixel, mode, virtual_size - mode event
blank - blank event
modes - modes event
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-18 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 22:35 Jon Smirl [this message]
2005-02-21 18:50 ` sysfs support for framebuffer James Simmons
2005-02-21 19:33 ` Jon Smirl
2005-02-21 21:36 ` James Simmons
2005-02-21 22:15 ` Jon Smirl
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=9e4733910502181435f60371c@mail.gmail.com \
--to=jonsmirl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).