From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] Annotate machines with amount of RAM
Date: Tue, 17 Oct 2006 00:23:11 +0300 [thread overview]
Message-ID: <299122878.20061017002311@gmail.com> (raw)
In-Reply-To: <4533C686.8020600@dominion.kabel.utwente.nl>
Hello Koen,
Monday, October 16, 2006, 8:51:02 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Michael 'Mickey' Lauer schreef:
>> Which features do we need to describe? At first glance, I could think
>> about
>>
>> VOLATILE_STORAGE_SIZE (RAM)
>> NON_VOLATILE_STORAGE_SIZE (Flash, HD, etc.)
>> DISPLAY_TYPE (Touchscreen or not)
>> DISPLAY_RESOLUTION
> and please let us not fall in to the same trap over and over again by ignoring DPI. My
> a780 and h2200 are both qvga, but it's 100dpi versus 160dpi, which makes a huge difference.
Still, exact pixel resolution is primary thing from the software
point fo view ;-). But I guess, current GUI_MACHINE_CLASS indeed may
survive some more time.
>>
>> We shouldn't stop here. With several groups working on device daemon
>> standards towards interoperable platforms, it could make sense to
>> describe
>>
>> INPUT_METHODS
>>
>> as well (buttons, keyboard, touchscreen, microphone).
> MACHINE_FEATURES = "keyboard" exists :)
touchscreen, too. But "buttons" and "microphone" would be nice
additions.
>>
>> Last but not least GSM and (A)GPS should make its way into
>> MACHINE_FEATURES pretty soon as well...
> Right, I nuked smartphone-common.conf today and I was thinking how to funnel it into
> task-base :)
Well, I'd say, the benefits of task-base are now pretty visible!
> regards,
> Koen
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2006-10-16 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 15:00 [RFC] Annotate machines with amount of RAM Paul Sokolovsky
2006-10-16 17:35 ` Michael 'Mickey' Lauer
2006-10-16 17:51 ` Koen Kooi
2006-10-16 21:23 ` Paul Sokolovsky [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=299122878.20061017002311@gmail.com \
--to=pmiscml@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox