From: Richard Purdie <rpurdie@rpsys.net>
To: Graeme Gregory <dp@xora.org.uk>
Cc: openembedded-devel@openembedded.org,
"Dr. Michael Lauer" <mickey@vanille-media.de>
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Mon, 09 Jul 2007 21:44:35 +0100 [thread overview]
Message-ID: <1184013875.5757.71.camel@localhost.localdomain> (raw)
In-Reply-To: <200707092119.03823.dp@xora.org.uk>
On Mon, 2007-07-09 at 21:19 +0100, Graeme Gregory wrote:
> On Monday 09 July 2007 21:01:36 Dr. Michael Lauer wrote:
> > To summarize:
> >
> > It looks like we can agree to adding information to the
> > MACHINE_DISPLAY_ namespace.
> >
> > However, we're undecided regarding the semantics. Some of think the
> > physical hardware information need to be there, some of us want the
> > logical (including kernel-level gfx hardware rotation), some of us
> > want a high-level meaning.
> >
> > How do we proceed now? Collect more arguments in favour or against or
> > shall we vote? Who is having a voice?
> >
> I would vote for using the version that gives the most information and
> therefore the other information can be derived.
>
> WIDTH=480
> HEIGHT=640
> ROTATION=270
>
> You can infer that inside your opie/x11/other system you have a 640x480
> landscape.
>
> But from
>
> WIDTH=640
> HEIGHT=480
>
> You cannot infer the rotation.
>
> So I think having the physical parameters including rotation is essential.
Well said :). If you give the physical information you can derive the
rest. If you give "logical" information you can't get back to the
physical which is why formfactor gives physical parameters.
Cheers,
Richard
next prev parent reply other threads:[~2007-07-09 20:50 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
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 [this message]
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=1184013875.5757.71.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=dp@xora.org.uk \
--cc=mickey@vanille-media.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.