All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Graeme Gregory <dp@xora.org.uk>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Mon, 9 Jul 2007 16:41:28 +0300	[thread overview]
Message-ID: <1211634359.20070709164128@gmail.com> (raw)
In-Reply-To: <20070709131744.GC2336@p3n3tr4t0r.internal>

Hello Graeme,

Monday, July 9, 2007, 4:17:44 PM, you wrote:

> On Mon, Jul 09, 2007 at 03:43:03PM +0300, Paul Sokolovsky wrote:
>>   As was pointed out, interpretation of those vars should depend on
>> presence of "screen" in machine features. And yes, then we need to set
>> their bitbake.conf default to 0, so only screen'ed machines specify
>> them.
>> 
>>   Also a note of exact semantics of those vars - they provide *some
>> default* screen resolution and orientation. Actually not some, but the
>> most appropriate after-install default. So, in particular,
>> notebook-style keyboarded devices would have:
>> 
>> MACHINE_DISPLAY_WIDTH_PIXELS=640
>> MACHINE_DISPLAY_HEIGHT_PIXELS=480
>> 
>> A device with vertical PDA layout would have
>> 
>> MACHINE_DISPLAY_WIDTH_PIXELS=480
>> MACHINE_DISPLAY_HEIGHT_PIXELS=640
>> 

> The problem with this interpretation is that although spitz boots and looks
> like it is 640x480 it is in fact 480x640 with rotation. So it may just
> be a mistake in your example that spitz happens to show up. Or it may be
> something that has not been considered.

That's just low-level details, which would be handled on another
level. I have specific usecase for this on which I model this initial
usage: background images for OPIE. So, what would you prefer for
spitz: having a landscape or portrait background by default? That's
what should go into those vars. Of course, for other uses we may need
another interpretation, for example, add function which will
"normalize" resolution (w >= h for example), or just return largest of
them, etc.

And rotation may need special support, and then DPI too. Just let's
start with specific itches first and elaborate on that. Actual pixel
dimension is the objective parameter, so we're not on the wrong track.

> Graeme


> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  parent reply	other threads:[~2007-07-09 13:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08  1:11 [RFC] Adding screen dimensions to machine configs Paul Sokolovsky
2007-07-08  7:16 ` Koen Kooi
2007-07-08  8:39   ` Dr. Michael Lauer
2007-07-08  9:26   ` Richard Purdie
2007-07-08 12:00     ` Stanislav Brabec
2007-07-08 14:27       ` Richard Purdie
2007-07-09  0:53   ` Rod Whitby
2007-07-09  5:31     ` Stelios Koroneos
2007-07-09 12:43   ` Paul Sokolovsky
2007-07-09 13:17     ` Graeme Gregory
2007-07-09 13:35       ` Dr. Michael Lauer
2007-07-09 13:42         ` Graeme Gregory
2007-07-09 13:52           ` Dr. Michael Lauer
2007-07-09 14:03             ` Graeme Gregory
2007-07-09 14:19               ` Dr. Michael Lauer
2007-07-09 14:25                 ` Graeme Gregory
2007-07-09 14:40                   ` Paul Sokolovsky
2007-07-09 15:15                   ` Marcin Juszkiewicz
2007-07-09 20:30                     ` Koen Kooi
2007-07-09 22:03                       ` Richard Purdie
2007-07-09 15:44                 ` Florian Boor
2007-07-09 14:23               ` Marcin Juszkiewicz
2007-07-09 14:25               ` Paul Sokolovsky
2007-07-09 15:11                 ` Marcin Juszkiewicz
2007-07-09 13:57         ` Paul Sokolovsky
2007-07-09 13:41       ` Paul Sokolovsky [this message]
2007-07-09 15:55     ` Richard Purdie
2007-07-09 20:01       ` Dr. Michael Lauer
2007-07-09 20:19         ` Graeme Gregory
2007-07-09 20:44           ` Richard Purdie
2007-07-09 20:21         ` Koen Kooi
2007-07-09 21:36           ` Paul Sokolovsky
2007-07-09 21:21         ` Paul Sokolovsky
2007-07-10 10:33           ` Dr. Michael Lauer
2007-07-12 12:36             ` Paul Sokolovsky
2007-07-08 11:36 ` Michael Krelin

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=1211634359.20070709164128@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=dp@xora.org.uk \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.