From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding screen dimensions to machine configs
Date: Mon, 09 Jul 2007 17:44:07 +0200 [thread overview]
Message-ID: <469257C7.2040104@kernelconcepts.de> (raw)
In-Reply-To: <4310707680.20070709161925@vanille-media.de>
Hi,
Dr. Michael Lauer schrieb:
>> I just worry what happens to machines without screens but that can have
>> gfx cards added.
>
> Which is almost all equipment with USB host.
I think it is fine to assume that these devices that do not have a built-in
screen but support one by adding a graphics device can have a more or less
arbitrary resolution. That means that you assume a common resolution like
1024x768 and if you really have a special need you would override these values
anyway. For most devices which usually have no screen or a built-in one you
would be quite safe with one setting. For the others just choose a big default
which should bee correct in most cases and for things like background images it
is usually better to ship a big one and scale it down instead of shipping a too
small one.
>> By the current level of thought behind these variables
>> a divide by zero is inevitable.
>
> Ok, how about VGA being the default?
That's fine as long you do not have this set if you do not have the screen
feature enabled, otherwise you might pull in big backgrounds and similar stuff
for no reason.
> I don't think so. What applications care about is if portrait or
> landscape is the common default and this is already encoded in HEIGHT
> and WIDTH.
Exactly... and on rotatable displays you need some support from the applications
anyway.
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
1D78 2D4D 6C53 1CA4 5588 D07B A8E7 940C 25B7 9A76
next prev parent reply other threads:[~2007-07-09 15:49 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 [this message]
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
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=469257C7.2040104@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--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.