summaryrefslogtreecommitdiffstats
path: root/meta-agl-core/recipes-connectivity
diff options
context:
space:
mode:
authorScott Murray <scott.murray@konsulko.com>2021-01-04 11:25:07 -0500
committerJan-Simon Moeller <jsmoeller@linuxfoundation.org>2021-01-12 13:35:51 +0000
commitdd6777dfdacc691402cde0e349e9987a481efe3a (patch)
tree0d7e757655d1d5980bb7b9889ca943a9348e687c /meta-agl-core/recipes-connectivity
parentcf15d1c197b2afdd4641b2415b12c011a8f1a432 (diff)
meta-agl-core: Revise weston-ini-conf mechanism
The recent layer reorganization broke the landscape vs portrait scheme based on bbappend'ing the weston-ini-conf recipe in the previous cluster and html5 demo layers. To fix this and to facilitate being able to easily build the mix of demo platform images, the weston.ini generation mechanism in the weston-ini-conf has been revised to build multiple packages. Instead of relying on SRC_URI to install weston.ini fragments into WORKDIR and grabbing all of them with a *.cfg glob, an explicit list built from new WESTON_FRAGMENTS and WESTON_DISPLAYS variables is used. The fragments listed in WESTON_FRAGMENTS are used to generate both weston-ini-conf and weston-ini-conf-landscape packages containing uniquely named files (weston.ini.default and weston.ini.landscape, respectively), and the OE update-alternatives mechanism is used to have weston.ini point at the appropriate file on installation. For now, the two packages are explicitly marked as incompatible with one another, but this could be tweaked in the future if switching between them on target is desired. Additional notes: - A RPROVIDES of "weston-ini" has been defined for the weston-ini-conf packages and a RDEPENDS on it added to weston-init. This should allow members to drop in a complete alternative solution while still having a dependency chain. - The various meta-agl-bsp bbappends of weston-ini-conf have for the most part been updated to yield the same behavior as before, though with an eye towards using machine overrides to ease multiconfig usage down the road. This includes the currently unused Raspberry Pi touchscreen support, which has been left since it may still see use. - An exception to the above, however, is that the support for the touchscreen on the dra7 EVM has been removed, as upstream dropped the support for the screen on the available test hardware and at present it only seems feasible to support external HDMI monitors. - The unused fbdev fragment used to support meta-freescale in the past has been removed. - The virtual and virtual-landscape fragments have been renamed to virtual-270 and virtual-0 to better indicate the orientation and match the naming used for the other fragments. It is likely that future work will need to split the display enabling and orientation aspects, as the current tying together of the two results in configurations somewhat overly specific to the actual AGL demo systems. Bug-AGL: SPEC-3745 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: I2a968781182a346c1d483cca4fd7337679e58118 Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25860 Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Diffstat (limited to 'meta-agl-core/recipes-connectivity')
0 files changed, 0 insertions, 0 deletions
e.Decorator */ .highlight .ne { color: #bb0066; font-weight: bold } /* Name.Exception */ .highlight .nf { color: #0066bb; font-weight: bold } /* Name.Function */ .highlight .nl { color: #336699; font-style: italic } /* Name.Label */ .highlight .nn { color: #bb0066; font-weight: bold } /* Name.Namespace */ .highlight .py { color: #336699; font-weight: bold } /* Name.Property */ .highlight .nt { color: #bb0066; font-weight: bold } /* Name.Tag */ .highlight .nv { color: #336699 } /* Name.Variable */ .highlight .ow { color: #008800 } /* Operator.Word */ .highlight .w { color: #bbbbbb } /* Text.Whitespace */ .highlight .mb { color: #0000DD; font-weight: bold } /* Literal.Number.Bin */ .highlight .mf { color: #0000DD; font-weight: bold } /* Literal.Number.Float */ .highlight .mh { color: #0000DD; font-weight: bold } /* Literal.Number.Hex */ .highlight .mi { color: #0000DD; font-weight: bold } /* Literal.Number.Integer */ .highlight .mo { color: #0000DD; font-weight: bold } /* Literal.Number.Oct */ .highlight .sa { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Affix */ .highlight .sb { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Backtick */ .highlight .sc { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Char */ .highlight .dl { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Delimiter */ .highlight .sd { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Doc */ .highlight .s2 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Double */ .highlight .se { color: #0044dd; background-color: #fff0f0 } /* Literal.String.Escape */ .highlight .sh { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Heredoc */ .highlight .si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ .highlight .sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ .highlight .sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ .highlight .s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */ }
This README file contains information on the contents of the
hmi-framework layer.

Please see the corresponding sections below for details.


HMI Framework
================
meta-hmi-framework is the layer providing HMI framework. 
HMI framework provides HMI resource(right) management. Resource contains sound, window, input to control.
This is based on the document in https://wiki.automotivelinux.org/hmiframework

Maintainers:
 Takeshi Hoshina<takeshi_hoshina@mail.toyota.co.jp>
 Hiroshi Kojima<Hiroshi_Kojima@mentor.com>
 Kazumasa Mitsunari<knimitz@witz-inc.co.jp>


How to enable the framework
=================
In order to enable the HMI Framework features, the following line has to be enabled in local.conf

IMAGE_INSTALL_append += ""

Reference
=================
https://wiki.automotivelinux.org/hmiframework


I. Adding the hmi-framework layer to your build
=================================================

--- replace with specific instructions for the hmi-framework layer ---

In order to use this layer, you need to make the build system aware of
it.

Assuming the hmi-framework layer exists at the top-level of your
yocto build tree, you can add it to the build system by adding the
location of the hmi-framework layer to bblayers.conf, along with any
other layers needed. e.g.:

  BBLAYERS ?= " \
    /path/to/yocto/meta \
    /path/to/yocto/meta-poky \
    /path/to/yocto/meta-yocto-bsp \
    /path/to/yocto/meta-hmi-framework \
    "


II. Misc
========

--- replace with specific information about the hmi-framework layer ---