[RFC] Annotate machines with amount of RAM

[RFC] Annotate machines with amount of RAM

[Paul Sokolovsky]

Hello openembedded-devel,

  Another small RFC from me. We already have ROOT_FLASH_SIZE variable
for machines, which specifies builtin flash size. Distros may use it to
decide what to put into rootfs, check its size, etc.

  I'd like to propose to add setting like RAM_SIZE which would list
available RAM. Generally, that would be in line with more comprehensive
declaritive machine descriptions we move towards with introduction of
MACHINE_FEATURES. Clever distro could use RAM_SIZE to select
alternative packages/settings. For example, if we ever come to
Firefox/Minimo being default browser for distros, RAM_SIZE="32"
machines may still prefer something smaller.


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

Re: [RFC] Annotate machines with amount of RAM

[Michael 'Mickey' Lauer]

Am Montag, den 16.10.2006, 18:00 +0300 schrieb Paul Sokolovsky:
>   I'd like to propose to add setting like RAM_SIZE which would list
> available RAM. Generally, that would be in line with more comprehensive
> declaritive machine descriptions we move towards with introduction of
> MACHINE_FEATURES. Clever distro could use RAM_SIZE to select
> alternative packages/settings. For example, if we ever come to
> Firefox/Minimo being default browser for distros, RAM_SIZE="32"
> machines may still prefer something smaller.

This is a good idea. We definitely need something standardised here in
order to prevent even more growth of hand-selected variables.

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

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).

Last but not least GSM and (A)GPS should make its way into
MACHINE_FEATURES pretty soon as well...

-- 
Regards,

Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de

Re: [RFC] Annotate machines with amount of RAM

[Koen Kooi]

-----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.

> 
> 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 :)

> 
> 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 :)

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFM8aGMkyGM64RGpERAh9TAKCpyAJ33NZ66rfd5rl1qu7aQOZJ2QCeNgN7
OImzQ9bzBfcmsO6cF+v4DRM=
=sxZi
-----END PGP SIGNATURE-----

Re: [RFC] Annotate machines with amount of RAM

[Paul Sokolovsky]

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