From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Jon Smirl <jonsmirl@gmail.com>
Subject: Re: Patch to add mode setting to sysfs
Date: Thu, 17 Feb 2005 21:50:16 +0800 [thread overview]
Message-ID: <200502172150.16256.adaplas@hotpop.com> (raw)
In-Reply-To: <9e4733910502161430ff1dad1@mail.gmail.com>
On Thursday 17 February 2005 06:30, Jon Smirl wrote:
> This is a first pass at adding two new sysfs attributes to
> /sys/class/graphics/fb0 for setting modes. There are two attributes:
> modes which contains a list of valid modes, and mode which is the
> current mode. To switch modes echo one of the entries from the modes
> list to the mode attribute.
> The D,V,S on the modes represents Detailed, Vesa, Standard from the DDC
> info.
>
> modes is root writable. It can also be used to set the list of modes.
> For example a /etc file could add modes that are not in the monitor's
> DDC.
>
> mode is user writable. PAM would set ownership of mode at user login
> time. This provides a safe way for a user to set the mode without
> being root. You can only set the mode to one of the modes on the list.
>
> If this code looks good I'll do another pass that adds some more
> features and makes it more robust.
Looks very interesting, and I will try it soon. A few comments:
+ fb_videomode_to_var(&var, mode);
+ var.activate |= FB_ACTIVATE_FORCE;
+ var.bits_per_pixel = 32;
Instead of hardcoding some of the fields in var, why not
copy it from the current var? Ie:
var = info->var;
fb_videomode_to_var(&var, mode);
Tony
-------------------------------------------------------
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 prev parent reply other threads:[~2005-02-17 13:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 22:30 Patch to add mode setting to sysfs Jon Smirl
2005-02-16 22:47 ` James Simmons
2005-02-17 1:28 ` Jon Smirl
2005-02-17 13:50 ` Antonino A. Daplas [this message]
2005-02-17 20:49 ` Jon Smirl
2005-02-17 22:13 ` James Simmons
2005-02-18 0:04 ` Antonino A. Daplas
2005-02-18 0:39 ` Jon Smirl
2005-02-21 18:37 ` James Simmons
2005-02-21 19:11 ` Jon Smirl
2005-02-21 21:16 ` James Simmons
2005-02-18 2:59 ` Jon Smirl
2005-02-18 7:31 ` Antonino A. Daplas
2005-02-18 9:42 ` Geert Uytterhoeven
2005-02-18 7:27 ` Jon Smirl
2005-02-18 7:41 ` Antonino A. Daplas
2005-02-18 7:42 ` Antonino A. Daplas
2005-02-18 16:46 ` Jon Smirl
2005-02-18 21:59 ` Antonino A. Daplas
2005-02-21 18:55 ` James Simmons
2005-02-21 19:13 ` Jon Smirl
2005-02-21 23:13 ` Antonino A. Daplas
2005-02-21 23:15 ` Antonino A. Daplas
2005-02-25 0:04 ` 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=200502172150.16256.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=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 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.