[oe] [RFC] Adding screen dimensions to machine configs

[Paul Sokolovsky]

Hello Koen,

Monday, July 9, 2007, 11:21:14 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Dr. Michael Lauer schreef:
>> 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.

> and how about linux kernel 2.4 and 2.6 (or even 2.6.ancient and 2.6.recent) having
> different opinions on rotation, or maybe worse, having rotation specified via CMDLINE?

> I think OE should specify the hardware (since it's in the MACHINE namespace anyway) and
> have userspace deal with rotation and stuff.

> The main question remains: what are people going to (ab)use this for? If it's just for
> opie backgrounds I don't see why adding 3 or more lines to each and every machine is less
> work than adding one machine override to the background .

  Hopefully not just for OPIE. And it is still paradigmatic question -
where is the proper place for such information. With this change, we
move towards having machine-specific information in ... well, machine
config itself, not spread around the codebase, and that's apparently the
right direction of changes.

>> This is Poky version of that part XServer script - no machine related code
>> at all. Of course it support only machines with formfactor defines.
> 
> So you have the exact same problem, but in a different place. And as a side-effect, the
> image can't be shared between machines anymore, since only one config is present in
> formfactor.

  As if we had too good multi-machine shareability before... And it's
still about doing the right abstraction in the right place. It's only
one step from current formfactor implementation which uses build-time
file override to one which keeps DB of machine configs and dispatches
on them. And both these implementations can be used as needed,
transparently to the rest of system. And in general, it removes adhoc
case dispatches from different places, putting them in one clean
place.

> regards,

> Koen


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