All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Handling machines of the same architecture by different	screen resolutions
Date: Wed, 07 Mar 2007 16:39:14 +0000	[thread overview]
Message-ID: <1173285554.5826.19.camel@localhost.localdomain> (raw)
In-Reply-To: <151838550.20070307173136@gmail.com>

On Wed, 2007-03-07 at 17:31 +0200, Paul Sokolovsky wrote:
> Hello openembedded-devel,
> 
>   Continuing discussion of how to handle such important machine
> property like screen size/resolution, here's the issue: there're
> cases, when same "machine" in OE terms actually has submodels which
> differ in screen resolution. One example is recently added aximx50
> machine. That machine covers Axim X50, Axim X50V, Axim X51, Axim X51V
> PDA models. "V" models have VGA screen, others - QVGA. They are served
> by the same kernel port, though defconfigs for "V" models differ, as
> there's no runtime detection.
> 
>   And, again, screen sizes differ, so "V" machines should be
> bigscreen, while "V-less" - smallscreen. Does this warrant adding
> another machine to OE to cover "V" models? (It would be obviously
> done via refactoring common parts to machine/include/ ).

In my view yes, since they need different kernels.

If they used a common kernel, it would be a choice for the machine
maintainer where both large and small icons would be needed in the
image, selected at runtime in the common image case. A separate machine
is probably easier.

Cheers,

Richard







      reply	other threads:[~2007-03-07 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 15:31 Handling machines of the same architecture by different screen resolutions Paul Sokolovsky
2007-03-07 16:39 ` Richard Purdie [this message]

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=1173285554.5826.19.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --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.