linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Antonino Daplas <adaplas@pol.net>,
	James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Small API change
Date: 01 Apr 2003 20:30:58 +0200	[thread overview]
Message-ID: <1049221857.589.138.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <1049214320.1174.68.camel@localhost.localdomain>

I want to add a flag passed by userland in fb_var_screeninfo
that say, for an LCD using a scaled mode, to either use a full
scaling or to keep aspect ratio (when possible).

This is quite useful for things like titanium powerbooks with their
wide LCDs. Currently, if I set a 1024x768 mode on my 'native' 1152x768,
I get a horizontal scaling and no vertical scaling, thus a bad
aspect ratio. It can be ok for some things, not for others, I'd like
to let userland the choice. MacOS does provide both set of modes
as well. In the "keep aspect ratio" mode, the driver would scale
both H and V the same (based on the smaller of H and V ratios)
and add margins to center the display. On some radeons, I think I
even have optional HW automatic centering.

We can either define a "flags" field using on of the reserved ones
and stuff that (along with 31 remaining bits for whatever other
flags we may have, I'm thinking about 6 vs. 8 bits DACs or such
other options that are common to enough HW to be worth defining
there).

We can define a "hw_specific_flags" field. Same as above, but we
define the meaning of this field as depending on the driver. That
is, we add a way for userland to pass mode attributes (we are really
talking about mode attributes here, that should be passed along with
setting the mode) that are specific to a given driver, though the
problem of identifying the driver type may not be that simple (using
the accel type constant ?)

Or we can eventually just define a new bit in the "sync" field, that
seem to be the most economic way, since we have 32 bits available
and only 6 used so far




-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

  parent reply	other threads:[~2003-04-01 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31  9:53 [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01  0:07 ` Jon Smirl
2003-04-01  0:27   ` Kendall Bennett
2003-04-01  1:27     ` Antonino Daplas
2003-04-01  8:29       ` Benjamin Herrenschmidt
2003-04-01  9:41         ` Antonino Daplas
2003-04-01 11:34           ` Benjamin Herrenschmidt
2003-04-01 13:38             ` Antonino Daplas
2003-04-01 13:53               ` Benjamin Herrenschmidt
2003-04-01 15:32                 ` Antonino Daplas
2003-04-01 15:22               ` Jon Smirl
2003-04-01 16:25                 ` Antonino Daplas
2003-04-01 16:44                   ` Benjamin Herrenschmidt
2003-04-01 18:30                   ` Benjamin Herrenschmidt [this message]
2003-04-01 20:10                     ` Small API change Geert Uytterhoeven
2003-04-01 22:03                       ` Benjamin Herrenschmidt
2003-04-02 22:01                         ` James Simmons
2003-04-02 22:11                           ` Benjamin Herrenschmidt
2003-04-01  1:04   ` [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01  4:01     ` Jon Smirl
2003-04-01  9:41       ` Antonino Daplas
     [not found]         ` <20030401120835.GA30421@skunk.convergence.de>
2003-04-01 13:38           ` [directfb-dev] " Antonino Daplas

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=1049221857.589.138.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --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).