linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: probing the supported resolution list
Date: Thu, 01 Oct 2009 00:41:41 -0700	[thread overview]
Message-ID: <4AC45D35.3020600@manoweb.com> (raw)

Hi, is there a standard way for a userspace program to "probe" the 
supported display sizes/refresh rates/bit depths? The display I'm 
writing a driver for only supports a few specific resolutions, and I'm 
wondering how a userspace program can discover those.

Thank you
Alessio



------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf

             reply	other threads:[~2009-10-01  7:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  7:41 Alessio Sangalli [this message]
2009-10-03  5:04 ` probing the supported resolution list Krzysztof Helt

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=4AC45D35.3020600@manoweb.com \
    --to=alesan@manoweb.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).