Age | Commit message (Collapse) | Author | Files | Lines |
|
The MACHINE config should not _append but set a default if unset.
Bug-AGL: SPEC-1037
Change-Id: Iaac4901ad2515564f7ebecfb1bd8f160c89fadf9
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
This avoids a conflict between the two following options:
* poky/meta/recipes-graphics/mesa/mesa_17.0.2.bb
* poky/meta/recipes-graphics/mesa/mesa_git.bb
Change-Id: I566ba2f5c3152efe08e9e3e883c79439813ef7ea
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
|
|
Board configs should append to previously set IMAGE_FSTYPES
instead of overriding it.
Change-Id: If5101784f574a96185351e96b7c0cbd120fd90dc
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
Signed-off-by: Thao Nguyen <thao.nguyen.yb@renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
(cherry picked from commit b4c458d529bfad0bd85c282912d3a237c8a3ebfb)
|
|
The SOC_FAMILY is already different between H3ULCB and M3ULCB:
H3ULCB uses SoC r8a7795.
M3ULCB uses SoC r8a7796.
Hence, setting this value in h3ulcb.conf and m3ulcb.conf to allow
images to be built without setting SOC_FAMILY in local.conf.
Signed-off-by: Thao Nguyen <thao.nguyen.yb@renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
H3ULCB will support new board with chip WS2.0.
There will be 2 device trees for H3ULCB corresponding to 2 board types:
- r8a7795-es1-h3ulcb.dtb: for H3ULCB WS1.1
- r8a7795-h3ulcb.dtb: for H3ULCB WS2.0
Change-Id: Ic11ee3f3e734641b020e3332721babd465cce2ae
Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
This commit addes "ulcb" into MACHINEOVERRIDES.
"ulcb" contains h3ulcb and m3ulcb.
It will help the implementation in the future
become easier to maintain for ULCB group.
Change-Id: I3c5d66f1e36e85f07d96a74f566fc1ffd5a76ee6
Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
Signed-off-by: Thao Nguyen <thao.nguyen.yb@rvc.renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|
|
Renesas BSP v3.5.1 (kernel v4.9 stable)
[Environment]
poky: yocto-2.1.2 (cca8dd15c8096626052f6d8d25ff1e9a606104a3)
meta-openembedded: 55c8a76da5dc099a7bc3838495c672140cedb78e
meta-linaro: 2f51d38048599d9878f149d6d15539fb97603f8f
[Information]
- U-boot: Changed load address from H'49000000 to H'50000000
- XDG_RUNTIME_DIR has been changed from "/run/user/root" to "/run/user/0"
- Change location of include directory, which stores common user header
files, to $(INCSHARED)
- In BSP Only, core-image-weston is not supported even though
local-wayland.conf is provided.
- Please set Salvator-x SW7 Pin-1. In after Yocto BSP v2.12.0, it is
necessary to enable BKUP_TRG signal for Suspend to RAM.
- The dtb filename was changed in R-Car H3. Only
"Image-r8a7795-es1-salvator-x.dtb" is supported in this version.
Please use "Image-r8a7795-es1-salvator-x.dtb" It supports R-Car H3
WS1.0 and WS1.1.
- Please update your local.conf and bblayers.conf corresponding to Yocto
v2.16.0 package. You can refer to meta-rcargen3/docs/sample/conf/ for
updated contents.
- You have to re-compile out-of-recipe software like user application by
v2.16.0 SDK toolchains.
- In some boards, the resuming from System Suspend to RAM may cause
unstable operation or failed to resume.
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
|