[Oberon] ALO: ArmLinuxOberon does the job!

[eas lab]

I was wrong again: the special shading of the MenuFrame of the TextFrame,
which does reverse-video for selected text, and has a darker background, to
emphasise the Frame's top boundry, fails to show this special appearance,
in LNO, not because of ETHO code; but because of complex/too-smart
modern hardware.  It's fine with the old CRT. The newDisplayHardware
has a menu-tree with ca. 30 leaves; so that the blame can always be
"you don't know how to operate it".

You won't be happy after spending much effort to tune for your present
favoured hardware, when that effort is lost for future hardware.

I've become curious and want to "look into FrameBuffers".
ARM linux shows the following [but I couldn't find its calculator, so
ALO's Calculator.Panel did the job. And this is all written in ALO.
An acrobatic achievement of ALO, is the remapping of the all importent
"*" char [from the inconvenient <shift 8> to <F12> <insert>] via ETHO's
powerful EditKeys.Tool .  My numKeyPad is dead for ALO.
==============
-> fbset -i ==
mode "960x540"  <-- my /boot/config.txt setting
    geometry 960 540 960 540 16
    timings 0 0 0 0 0 0 0
    rgba 5/11,6/5,5/0,0/16
endmode

Frame buffer device information:
    Name        : BCM2708 FB
    Address     : 0x5d385000
    Size        : 1036800 <- / 960==1080 / 540 == 2
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 1920
    Accelerator : No

===> Can ALO inspect this File ? == YES!!
*alc* = Calculator.Panel == See good calculation results above.
How can ALO see into AbsAdrs-ed memory: 0x5d385000 ?!
Ask on rPi-forum ?
Again: need set of VM instructions, for low-level access, like:
(AbsAdr) -> RegN
RegN  -> (AbsAdr)
...etc.