date:20200917

[yocto] Yocto recipe for Tailscale #yocto #golang

2020-09-17 Thread Mike Thompson via lists.yoctoproject.org

Does anyone know if there is an existing bitbake recipe for building the 
Tailscale client daemon and CLI tool from the following source?  A search on 
Google yielded no obvious links.

https://github.com/tailscale/tailscale

The Tailscale client for Linux looks to be built using the Go language which is 
a complete unknown to me. I've built very simple recipes before for basic 
Makefile and Automake built software, but I suppose Go brings a new set of 
challenges.

If an existing recipe is not available, any words of wisdom before I get 
started on this?

Thanks,

Mike Thompson

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50721): https://lists.yoctoproject.org/g/yocto/message/50721
Mute This Topic: https://lists.yoctoproject.org/mt/76925556/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #golang:https://lists.yoctoproject.org/g/yocto/mutehashtag/golang
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH] zephyr-kernel: add Zephyr RTOS version 2.3.0 support

2020-09-17 Thread yock . gen . mah

From: yockgenm 

Signed-off-by: yockgenm 
---
 classes/zephyr-kernel-src.bbclass  | 12 
 .../{qemu_4.2.%.bbappend => qemu_5.1.%.bbappend}   |  0
 .../zephyr-kernel/zephyr-kernel-common.inc |  1 +
 .../zephyr-kernel/zephyr-kernel-src_2.2.bb | 33 --
 .../zephyr-kernel/zephyr-kernel-src_2.3.bb | 24 
 .../zephyr-kernel/zephyr-kernel-test.inc   |  7 ++---
 6 files changed, 35 insertions(+), 42 deletions(-)
 rename recipes-devtools/qemu/{qemu_4.2.%.bbappend => qemu_5.1.%.bbappend} 
(100%)
 delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
 create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb

diff --git a/classes/zephyr-kernel-src.bbclass 
b/classes/zephyr-kernel-src.bbclass
index 653cb9b..d202293 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -1,13 +1,15 @@
 #Set relevant variables based on Zephyr kernel version
 
-PREFERRED_VERSION_zephyr-kernel ??= "2.2.0"
+PREFERRED_VERSION_zephyr-kernel ??= "2.3.0"
 
-SRCREV = "d39cb42d0920d5658fad358ad5b91de75d747a20"
+SRCREV = "b8c78e254ff875680e99c9f131fbe285c4575927"
+SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
 
-SRC_URI = 
"git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch
 \
+SRC_URI = 
"git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.3-branch
 \
+   
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis
 \
   file://0001-cmake-add-yocto-toolchain.patch \
 "
-PV = "2.2.0"
+PV = "2.3.0"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"
 
@@ -15,7 +17,7 @@ ZEPHYR_TEST_SRCDIR = "tests/legacy/kernel/"
 
 python () {
 src_pn = d.getVar('PREFERRED_VERSION_zephyr-kernel', True)
-if src_pn == '2.2.0':
+if src_pn == '2.3.0':
 return
 else:
 bb.error("Unsupported Zephyr kernel version requested")
diff --git a/recipes-devtools/qemu/qemu_4.2.%.bbappend 
b/recipes-devtools/qemu/qemu_5.1.%.bbappend
similarity index 100%
rename from recipes-devtools/qemu/qemu_4.2.%.bbappend
rename to recipes-devtools/qemu/qemu_5.1.%.bbappend
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index d7147d5..aaf71a8 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -14,6 +14,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf"
 
 
 EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto 
-DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} 
-DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto"
+EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
 export ZEPHYR_BASE="${S}"
 
 
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
deleted file mode 100644
index a3e1c28..000
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb
+++ /dev/null
@@ -1,33 +0,0 @@
-
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"
-
-# tag v2.2
-SRCREV="d39cb42d0920d5658fad358ad5b91de75d747a20"
-SRC_URI = 
"git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch
 \
-  file://0001-cmake-add-yocto-toolchain.patch \
-"
-inherit cmake 
-PV = "2.2.0"
-S = "${WORKDIR}/git"
-
-IMAGE_NO_MANIFEST = "1"
-INHIBIT_DEFAULT_DEPS = "1"
-
-do_configure[noexec] = "1"
-do_compile[noexec] = "1"
-
-do_compile () {
-}
-
-do_install () {
-kerneldir=${D}/usr/src/zephyr
-install -d $kerneldir
-cp -r ${S}/* $kerneldir
-}
-
-PACKAGES = "${PN}"
-FILES_${PN} = "/usr/src/zephyr"
-
-SYSROOT_DIRS += "/usr/src/zephyr"
-
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb
new file mode 100644
index 000..8e8b5b8
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb
@@ -0,0 +1,24 @@
+
+inherit zephyr-kernel-src
+inherit cmake
+
+S = "${WORKDIR}/git"
+
+IMAGE_NO_MANIFEST = "1"
+INHIBIT_DEFAULT_DEPS = "1"
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+
+
+do_install () {
+kerneldir=${D}/usr/src/zephyr
+install -d $kerneldir
+cp -r ${S}/* $kerneldir
+}
+
+PACKAGES = "${PN}"
+FILES_${PN} = "/usr/src/zephyr"
+
+SYSROOT_DIRS += "/usr/src/zephyr"
+
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
index 65da7e8..7ab9bd4 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc
@@ -1,4 +1,4 @@
-ZEPHYRTESTS_remove = "fifo fp_sharing lifo mbox mem_heap mem_pool \
+ZEPHYRTESTS_remove = "fifo fpu_sharing lifo mbox mem_heap mem_pool \
 mem_protect mem_slab msgq mutex

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

2020-09-17 Thread Sangeeta Jain

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.2_M3.rc1.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Wednesday, September 23.

Thanks,
Sangeeta

> -Original Message-
> From: Pokybuild User 
> Sent: Friday, 18 September, 2020 12:18 AM
> To: yocto@lists.yoctoproject.org
> Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
> ; Yeoh, Ee Peng ;
> Chan, Aaron Chun Yew ;
> richard.pur...@linuxfoundation.org; akuster...@gmail.com;
> sjolley.yp...@gmail.com; Jain, Sangeeta 
> Subject: QA notification for completed autobuilder build (yocto-3.2_M3.rc1)
> 
> 
> A build flagged for QA (yocto-3.2_M3.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc1
> 
> 
> Build hash information:
> 
> bitbake: 29081375659e3dcf1c578cd98ab2c8a2e9f07ca8
> meta-arm: 1f3cf5812c91cdc15f63737bf9b30cce665b2999
> meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537
> meta-intel: f7580d72763653893c06e1d9ece7a77c4adb8485
> meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4
> meta-mingw: 30a051401c0a73dfff486ca4d0303b434816200f
> oecore: 4e7506882cabf3936f0269c2a98f61c7d595d613
> poky: c6bc20857cd1bdfd25dfc50e413be84d1d12b189
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50719): https://lists.yoctoproject.org/g/yocto/message/50719
Mute This Topic: https://lists.yoctoproject.org/mt/76912804/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] do_unpack() ISO Image

2020-09-17 Thread Chuck Wolber

Hi all,

I have a need to unpack an ISO image during do_unpack. This does not appear
to be one of the extensions that is handled by default, so I am working out
a way to use xorriso to do this for me.

I can get this to work in the following way, but it involves calling an
executable running on the build host, which only works by luck since the
host executable is the same architecture as what I am currently building. I
would like to do this in a portable way that does not break when I try to
build for a different architecture.

DEPENDS += "xorriso"

do_unpack_append() {
bb.build.exec_func('unpack_iso', d)
}

unpack_iso() {
   /usr/bin/xorriso -osirrox on -indev ${WORKDIR}/${PN}_${PV}.iso -extract
/ ${S}
}


>From looking at base.bbclass, it _seems_ as if my solution involves
something like this:

d.appendVarFlag('do_unpack', 'depends', ' xorriso:do_populate_sysroot')

But it is unclear exactly where that would go within my recipe. Any
thoughts?

Thank you,

..Ch:W..

-- 
*"Perfection must be reached by degrees; she requires the slow hand of
time." - Voltaire*

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50718): https://lists.yoctoproject.org/g/yocto/message/50718
Mute This Topic: https://lists.yoctoproject.org/mt/76924178/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 0/2] Delete mainline content

2020-09-17 Thread quanyang.wang

From: Quanyang Wang 

Hi Bruce,

This 2 patches are to delete the redundant content which is introduced
by mainline. Would you please help merge them to standard/xlnx-soc ?

Thanks,
Quanyang

Quanyang Wang (2):
  drm: xlnx: delete mainline Kconfig content
  arm64: zynqmp: delete mainline dts content

 arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 21 -
 drivers/gpu/drm/xlnx/Kconfig   |  9 -
 2 files changed, 30 deletions(-)

-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9070): 
https://lists.yoctoproject.org/g/linux-yocto/message/9070
Mute This Topic: https://lists.yoctoproject.org/mt/76922356/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][PATCH 2/2] arm64: zynqmp: delete mainline dts content

2020-09-17 Thread quanyang.wang

From: Quanyang Wang 

This is to delete the unnecessary content which is introduced from
mainline.

Signed-off-by: Quanyang Wang 
---
 arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 21 -
 1 file changed, 21 deletions(-)

diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi 
b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index f09d4e2e412e..59d393aa9bb3 100644
--- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
+++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
@@ -799,14 +799,6 @@
};
};
 
-   psgtr: phy@fd40 {
-   compatible = "xlnx,zynqmp-psgtr-v1.1";
-   status = "disabled";
-   reg = <0x0 0xfd40 0x0 0x4>,
- <0x0 0xfd3d 0x0 0x1000>;
-   reg-names = "serdes", "siou";
-   #phy-cells = <4>;
-   };
qspi: spi@ff0f {
u-boot,dm-pre-reloc;
compatible = "xlnx,zynqmp-qspi-1.0";
@@ -921,19 +913,6 @@
power-domains = <_firmware PD_SD_1>;
};
 
-   smmu: iommu@fd80 {
-   compatible = "arm,mmu-500";
-   reg = <0x0 0xfd80 0x0 0x2>;
-   status = "disabled";
-   #global-interrupts = <1>;
-   interrupt-parent = <>;
-   interrupts = <0 155 4>,
-   <0 155 4>, <0 155 4>, <0 155 4>, <0 155 4>,
-   <0 155 4>, <0 155 4>, <0 155 4>, <0 155 4>,
-   <0 155 4>, <0 155 4>, <0 155 4>, <0 155 4>,
-   <0 155 4>, <0 155 4>, <0 155 4>, <0 155 4>;
-   };
-
spi0: spi@ff04 {
compatible = "cdns,spi-r1p6";
status = "disabled";
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9069): 
https://lists.yoctoproject.org/g/linux-yocto/message/9069
Mute This Topic: https://lists.yoctoproject.org/mt/76922353/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] v5.2.x - stable updates comprising v5.2.60

2020-09-17 Thread Paul Gortmaker

Bruce, Yocto kernel folks:

Here it is.  The *final* 5.2.x stable update extension from me.

A quick overview - this maintenance extension - in just under a year,
contained 39 releases (v5.2.22 --> v5.2.60) and about 7800 backports.
So - roughly two hundred backports per release (on average).  I wish
the number was smaller, but as it turns out, that was the work done.

Hopefully nobody is surprised by this ending, with several months of
warning in these release notes being broadcast already.

The 5.2.60 content here is from an audit of what went into the v5.4.60
release plus any additional commits listed as "Fixes:" of the chosen
commits (and past backported commits) resulting in about 130 commits.

There was also a couple specific CVEs that I was aware of and made sure
we had the mainline commits for those present as well.  I hope that the
transparency of what was used, and the evolution repo below will help
anyone else who wants to continue v5.2 maintenance have an easier job.

There will always be one more commit/CVE, but as per the v4.8 and 4.12
and 4.18 extensions from the past, one has to draw a line in the sand.

I've put this release through my normal testing, with build tests
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and
finally some sanity runtime tests on x86-64 (raw + qemu/KVM).

Please find tag v5.2.60 (3ab42df9927f8a1dd5f49107242f0d6f61eeab3c) as
the current head of linux-5.2.y branch in the repo in the kernel.org
directory here:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git/?h=linux-5.2.y
  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git

for merge to standard/base in linux-yocto-5.2 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

  https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-5.2.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 5.2.x release.

Thanks to all the users and people who provided feedback.
Paul.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9067): 
https://lists.yoctoproject.org/g/linux-yocto/message/9067
Mute This Topic: https://lists.yoctoproject.org/mt/76920949/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Emulator tool for imx8m #linux #devtool #yocto

2020-09-17 Thread Khem Raj

On Thu, Sep 17, 2020 at 6:43 AM Amrun Nisha.R  wrote:
>
> Hi,
>
> Actually I'm working on the DART-IMX8M board. I can able to build the image 
> in linux machine and run it on the board. But for every build, i have to run 
> the image on board. I have checked on the qemu but it is not supported for 
> the machine imx8mq-var-dart.
> Is there any emulator can be used for imx8mq-var-dart?

closed you can get is qemuarm64, you can also use package management
in image and install/update/remove individual packages. something like
https://imxdev.gitlab.io/tutorial/How_to_apt-get_to_the_Yocto_Project_image/

> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50717): https://lists.yoctoproject.org/g/yocto/message/50717
Mute This Topic: https://lists.yoctoproject.org/mt/76909115/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

2020-09-17 Thread Pokybuild User


A build flagged for QA (yocto-3.2_M3.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.2_M3.rc1


Build hash information: 

bitbake: 29081375659e3dcf1c578cd98ab2c8a2e9f07ca8
meta-arm: 1f3cf5812c91cdc15f63737bf9b30cce665b2999
meta-gplv2: a8da8eb127a56561bf633ab53bec57fb5dbba537
meta-intel: f7580d72763653893c06e1d9ece7a77c4adb8485
meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4
meta-mingw: 30a051401c0a73dfff486ca4d0303b434816200f
oecore: 4e7506882cabf3936f0269c2a98f61c7d595d613
poky: c6bc20857cd1bdfd25dfc50e413be84d1d12b189



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50716): https://lists.yoctoproject.org/g/yocto/message/50716
Mute This Topic: https://lists.yoctoproject.org/mt/76912804/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [yocto-builds] relocate_sdk.py is failing when installing yocto3.1.2 SDK

2020-09-17 Thread Randy MacLeod


Hi Vijay,

I have redirected this thread to the main yocto list.
The yocto-builds list is for automated build outputs
rather than discussions.


What distro are you using?
What version of python3 is provided by that distro?
On Ubu-20.04, fyi:
$ grep python3 /.../oe-core.git/scripts/relocate_sdk.py
#!/usr/bin/env python3
$ python3 --version
Python 3.8.2

../Randy

On 2020-09-17 9:49 a.m., Ansurivijay Ramana wrote:


Classification: *HCL Internal*

Hi ,

I have added my layer and builded the SDK in yocto 3.1.2 but 
relocate_sdk.py is failing when installing.


Please help me in fixing this.

./poky-glibc-x86_64-core-image-sato-sdk-core2-32-qemux86-toolchain-3.1.2.sh

Poky (Yocto Project Reference Distro) SDK installer version 3.1.2

=

Enter target directory for SDK (default: /opt/poky/3.1.2): 
/home/vijay/build/test3


You are about to install the SDK to "/home/vijay/build/test3". Proceed 
[Y/n]? Y


Extracting 
SDK.done


Setting it up...Traceback (most recent call last):

  File "/home/vijay/build/test3/relocate_sdk.py", line 244, in 

    change_dl_sysdirs(e)

  File "/home/vijay/build/test3/relocate_sdk.py", line 118, in 
change_dl_sysdirs


    sh_offset, sh_size = struct.unpack("<24xQQ24x", sh_hdr)

struct.error: unpack requires a string argument of length 64

SDK could not be set up. Relocate script failed. Abort!

Thanks & Regards,

Vijay

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and 
intended for the named recipient(s) only. E-mail transmission is not 
guaranteed to be secure or error-free as information could be 
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
may contain viruses in transmission. The e mail and its contents (with 
or without referred errors) shall therefore not attach any liability 
on the originator or HCL or its affiliates. Views or opinions, if any, 
presented in this email are solely those of the author and may not 
necessarily reflect the views or opinions of HCL or its affiliates. 
Any form of reproduction, dissemination, copying, disclosure, 
modification, distribution and / or publication of this message 
without the prior written consent of authorized representative of HCL 
is strictly prohibited. If you have received this email in error 
please delete it and notify the sender immediately. Before opening any 
email and/or attachments, please check them for viruses and other defects.







--
# Randy MacLeod
# Wind River Linux


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50715): https://lists.yoctoproject.org/g/yocto/message/50715
Mute This Topic: https://lists.yoctoproject.org/mt/76912603/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Emulator tool for imx8m #linux #devtool #yocto

2020-09-17 Thread Andy Pont


Hello!

Actually I'm working on the DART-IMX8M board. I can able to build the 
image in linux machine and run it on the board. But for every build, i 
have to run the image on board. I have checked on the qemu but it is 
not supported for the machine imx8mq-var-dart.

Is there any emulator can be used for imx8mq-var-dart?
Generally speaking, at the point when we get to working with boards we 
are needing to interact with the outside world so we have to run on the 
target hardware.  Once U-Boot (or equivalent) is up and running then we 
speed the development process up using TFTP/NFS to boot the Linux kernel 
and mount the root file system.


It saves all the messing around programming on-board flash devices or SD 
cards whilst the image is in flux.  It also means that all the 
application developers are using the same and the latest configuration 
rather than having flash devices with old versions potentially causing 
problems.


It might help a little!

-Andy.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50714): https://lists.yoctoproject.org/g/yocto/message/50714
Mute This Topic: https://lists.yoctoproject.org/mt/76909115/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][linux-yocto v5.4/standard/base][PATCH] kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE

2020-09-17 Thread Bruce Ashfield

In message: [linux-yocto][linux-yocto v5.4/standard/base][PATCH] kprobes: Fix 
compiler warning for !CONFIG_KPROBES_ON_FTRACE
on 17/09/2020 Xulin Sun wrote:

> From: Muchun Song 
> 
> commit 10de795a5addd1962406796a6e13ba6cc0fc6bee upstream
> 
> Fix compiler warning(as show below) for !CONFIG_KPROBES_ON_FTRACE.
> 
> kernel/kprobes.c: In function 'kill_kprobe':
> kernel/kprobes.c:1116:33: warning: statement with no effect
> [-Wunused-value]
>  1116 | #define disarm_kprobe_ftrace(p) (-ENODEV)
>   | ^
> kernel/kprobes.c:2154:3: note: in expansion of macro
> 'disarm_kprobe_ftrace'
>  2154 |   disarm_kprobe_ftrace(p);
> 
> Link: https://lore.kernel.org/r/20200805142136.0331f...@canb.auug.org.au
> Link: 
> https://lkml.kernel.org/r/20200805172046.19066-1-songmuc...@bytedance.com

Looks like this should have also gone to -stable, but I've merged it
while it loops around.

Bruce

> 
> Reported-by: Stephen Rothwell 
> Fixes: 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at 
> kprobe_ftrace_handler")
> Acked-by: Masami Hiramatsu 
> Acked-by: John Fastabend 
> Signed-off-by: Muchun Song 
> Signed-off-by: Steven Rostedt (VMware) 
> Signed-off-by: Xulin Sun 
> ---
>  kernel/kprobes.c | 17 ++---
>  1 file changed, 14 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index bbff4bccb885..6cc1d961f56a 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -1076,9 +1076,20 @@ static int disarm_kprobe_ftrace(struct kprobe *p)
>   ipmodify ? _ipmodify_enabled : _ftrace_enabled);
>  }
>  #else/* !CONFIG_KPROBES_ON_FTRACE */
> -#define prepare_kprobe(p)arch_prepare_kprobe(p)
> -#define arm_kprobe_ftrace(p) (-ENODEV)
> -#define disarm_kprobe_ftrace(p)  (-ENODEV)
> +static inline int prepare_kprobe(struct kprobe *p)
> +{
> + return arch_prepare_kprobe(p);
> +}
> +
> +static inline int arm_kprobe_ftrace(struct kprobe *p)
> +{
> + return -ENODEV;
> +}
> +
> +static inline int disarm_kprobe_ftrace(struct kprobe *p)
> +{
> + return -ENODEV;
> +}
>  #endif
>  
>  /* Arm a kprobe with text_mutex */
> -- 
> 2.17.1
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9066): 
https://lists.yoctoproject.org/g/linux-yocto/message/9066
Mute This Topic: https://lists.yoctoproject.org/mt/76904129/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Emulator tool for imx8m #linux #devtool #yocto

2020-09-17 Thread Amrun Nisha.R

Hi,

Actually I'm working on the DART-IMX8M board. I can able to build the image in 
linux machine and run it on the board. But for every build, i have to run the 
image on board. I have checked on the qemu but it is not supported for the 
machine imx8mq-var-dart.
Is there any emulator can be used for imx8mq-var-dart?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50713): https://lists.yoctoproject.org/g/yocto/message/50713
Mute This Topic: https://lists.yoctoproject.org/mt/76909115/21656
Mute #linux:https://lists.yoctoproject.org/g/yocto/mutehashtag/linux
Mute #devtool:https://lists.yoctoproject.org/g/yocto/mutehashtag/devtool
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][linux-yocto v5.4/standard/cn96xx] marvell-cn96xx for linux-yocto v5.4

2020-09-17 Thread Bruce Ashfield

In message: [linux-yocto][linux-yocto v5.4/standard/cn96xx] marvell-cn96xx for 
linux-yocto v5.4
on 16/09/2020 Ruiqiang Hao wrote:

> Hi Bruce,
> 
> Would you please help to merge follow kernel code into our linux-yocto 
> standard kernel?
> 
> The branch is
>   v5.4/standard/cn96xx
>   v5.4/standard/preempt-rt/cn96xx

merged.

Bruce

> 
> Thanks,
> Ruiqiang
> 
> The following changes since commit 527554070bcc0804ce6b079886d4ac559f44ce77:
> 
>   Merge branch 'v5.4/standard/base' into v5.4/standard/cn96xx (2020-09-14 
> 11:40:29 -0400)
> 
> are available in the Git repository at:
> 
>   https://github.com/cythe/linux-yocto.git v5.4/standard/cn96xx
> 
> for you to fetch changes up to a37c2c731fa64e245566d6b2d409253b9bfbe5d1:
> 
>   octeontx2: Add IPv6 fields to default MKEX profile (2020-09-15 07:19:23 
> +)
> 
> 
> George Cherian (2):
>   octeontx2-af: Add support for VLAN based RSS hashing
>   octeontx2-pf: Support to change VLAN based RSS hash options via ethtool
> 
> Kiran Kumar K (2):
>   octeontx2-af: add npc profile support to parse CPT_PARSE_HDR
>   octeontx2-af: add npc profile support to parse NAT-T-ESP
> 
> Naveen Mamindlapalli (4):
>   octeontx2-af: Update forwarding rule action targeting VF with its 
> default one
>   octeontx2-bphy-netdev: Set minimum length of Tx packets to 64 bytes
>   octeontx2-af: Ratelimit prints from AF error interrupt handlers
>   octeontx2-af: Fix updating wrong multicast list index in NIX_RX_ACTION
> 
> Rakesh Babu (3):
>   octeontx2-af: Backport upstream changes.
>   octeontx2-af: Free RVU NIX IRQs properly.
>   octeontx2-pf: Remove wrapper APIs for mutex lock and unlock
> 
> Rick Farrington (1):
>   drivers: marvell: otx2-sdei-ghes: correct issues with crashdump kernel
> 
> Smadar Fuks (3):
>   octeontx2-af: Fix REE large rule file programming
>   octeontx2-af: Fix REE warnings for no previous prototype
>   octeontx2-af: Free RVU REE irq properly
> 
> Subbaraya Sundeep (3):
>   octeontx2-af: Fix the BPID mask
>   octeontx2-af: Send transmit link in mbox
>   octeontx2-pf: cleanup transmit link deriving logic
> 
> Sunil Goutham (1):
>   octeontx2-pf: Fix receive buffer size calculation
> 
> Vidhya Vidhyaraman (1):
>   octeontx2: Add IPv6 fields to default MKEX profile
> 
>  drivers/net/ethernet/marvell/octeontx2/af/cgx.c|  19 +-
>  drivers/net/ethernet/marvell/octeontx2/af/cgx.h|   4 +-
>  .../net/ethernet/marvell/octeontx2/af/cgx_fw_if.h  |   1 +
>  drivers/net/ethernet/marvell/octeontx2/af/mbox.h   |   8 +-
>  drivers/net/ethernet/marvell/octeontx2/af/npc.h|   6 +-
>  .../ethernet/marvell/octeontx2/af/npc_profile.h| 374 
> +++--
>  drivers/net/ethernet/marvell/octeontx2/af/rvu.c|   2 -
>  drivers/net/ethernet/marvell/octeontx2/af/rvu.h|  11 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_nix.c|  66 ++--
>  .../net/ethernet/marvell/octeontx2/af/rvu_npa.c|   2 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_npc.c|  95 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c |  32 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_ree.c| 108 +++---
>  .../ethernet/marvell/octeontx2/bphy/otx2_cpri.c|   5 +-
>  .../ethernet/marvell/octeontx2/nic/otx2_common.c   | 118 +++
>  .../ethernet/marvell/octeontx2/nic/otx2_common.h   |  16 +-
>  .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c  |  38 ++-
>  .../ethernet/marvell/octeontx2/nic/otx2_flows.c|  74 ++--
>  .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c   | 100 +++---
>  .../net/ethernet/marvell/octeontx2/nic/otx2_ptp.c  |  20 +-
>  .../ethernet/marvell/octeontx2/nic/otx2_smqvf.c|  26 +-
>  .../net/ethernet/marvell/octeontx2/nic/otx2_txrx.c |   6 +-
>  .../net/ethernet/marvell/octeontx2/nic/otx2_vf.c   |   2 +-
>  drivers/soc/marvell/Kconfig|   1 +
>  .../soc/marvell/octeontx2-ghes/otx2-sdei-ghes.c|  10 +
>  25 files changed, 808 insertions(+), 336 deletions(-)
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9064): 
https://lists.yoctoproject.org/g/linux-yocto/message/9064
Mute This Topic: https://lists.yoctoproject.org/mt/76881913/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong cast that may cause wrong truncation

2020-09-17 Thread Bruce Ashfield

In message: Re: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong 
cast that may cause wrong truncation
on 17/09/2020 He Zhe wrote:

> Hi Bruce,
> 
> This patch is missing for linux-yocto-dev from the latest rebase.

Fixed. And added to the kernel-cache, so on my next -dev kernel,
it will either conflict or be in place automatically.

Bruce

> 
> Thanks,
> Zhe
> 
> On 8/21/20 3:03 AM, Bruce Ashfield wrote:
> > merged to linux-yocto-dev standard/* and linux-yocto v5.8/standard/*
> >
> > Bruce
> >
> >
> > In message: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong 
> > cast that may cause wrong truncation
> > on 21/08/2020 zhe...@windriver.com wrote:
> >
> >> From: He Zhe 
> >>
> >> tail is a pointer while buftail.fp is a u32.
> >>
> >> arch/arm64/kernel/perf_callchain.c:100:6: warning: cast from pointer to
> >> integer of different size [-Wpointer-to-int-cast]
> >>   100 |  if ((u32)tail + 4 >= buftail.fp)
> >>   |  ^
> >> arch/arm64/kernel/perf_callchain.c:103:9: warning: cast to pointer from
> >> integer of different size [-Wint-to-pointer-cast]{noformat}
> >>   103 |  return (struct compat_frame_tail __user *)(buftail.fp - 4);
> >>   | ^
> >>
> >> Fixes: 8818670c17d2 ("arm64/perf: fix backtrace for AAPCS with FP enabled")
> >> Signed-off-by: He Zhe 
> >> ---
> >>  arch/arm64/kernel/perf_callchain.c | 4 ++--
> >>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/arm64/kernel/perf_callchain.c 
> >> b/arch/arm64/kernel/perf_callchain.c
> >> index 1be96e3631ea..a4b0864c4e32 100644
> >> --- a/arch/arm64/kernel/perf_callchain.c
> >> +++ b/arch/arm64/kernel/perf_callchain.c
> >> @@ -97,10 +97,10 @@ compat_user_backtrace(struct compat_frame_tail __user 
> >> *tail,
> >> * Frame pointers should strictly progress back up the stack
> >> * (towards higher addresses).
> >> */
> >> -  if ((u32)tail + 4 >= buftail.fp)
> >> +  if ((u64)tail + 4 >= (u64)buftail.fp)
> >>return NULL;
> >>  
> >> -  return (struct compat_frame_tail __user *)(buftail.fp - 4);
> >> +  return (struct compat_frame_tail __user *)((u64)buftail.fp - 4);
> >>  }
> >>  #endif /* CONFIG_COMPAT */
> >>  
> >> -- 
> >> 2.17.1
> >>
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9061): 
https://lists.yoctoproject.org/g/linux-yocto/message/9061
Mute This Topic: https://lists.yoctoproject.org/mt/76312403/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto][linux-yocto-dev standard/cn96xx] marvell-cn96xx for linux-yocto-dev v5.9

2020-09-17 Thread Bruce Ashfield


In message: [linux-yocto][linux-yocto-dev standard/cn96xx] marvell-cn96xx for 
linux-yocto-dev v5.9
on 15/09/2020 Ruiqiang Hao wrote:

> Hi Bruce,
> 
> Please help to merge them into our linux-yocto-dev marvell-cn96xx repo.

Thanks for the update.

This is now merged!

Bruce

> 
> The branch is
>   standard/cn96xx
> 
> Thanks,
> Ruiqiang
> 
> The following changes since commit e7a3a1bc0fe5daf96e8ff2b6925b15b5be884c5b:
> 
>   drivers: marvell: otx2-sdei-ghes: correct issues with crashdump kernel 
> (2020-09-02 13:52:06 +0800)
> 
> are available in the Git repository at:
> 
>   https://github.com/cythe/linux.git marvell-cn96xx_v5.9-rc3
> 
> for you to fetch changes up to 5152499248ef8c6b998ce56ddfa9d17a058570ca:
> 
>   octeontx2: Add IPv6 fields to default MKEX profile (2020-09-14 07:33:03 
> +)
> 
> 
> Kiran Kumar K (2):
>   octeontx2-af: add npc profile support to parse CPT_PARSE_HDR
>   octeontx2-af: add npc profile support to parse NAT-T-ESP
> 
> Naveen Mamindlapalli (2):
>   octeontx2-af: Ratelimit prints from AF error interrupt handlers
>   octeontx2-af: Fix updating wrong multicast list index in NIX_RX_ACTION
> 
> Rakesh Babu (1):
>   octeontx2-af: Free RVU NIX IRQs properly.
> 
> Smadar Fuks (3):
>   octeontx2-af: Fix REE large rule file programming
>   octeontx2-af: Fix REE warnings for no previous prototype
>   octeontx2-af: Free RVU REE irq properly
> 
> Subbaraya Sundeep (3):
>   octeontx2-af: Fix the BPID mask
>   octeontx2-af: Send transmit link in mbox
>   octeontx2-pf: cleanup transmit link deriving logic
> 
> Vidhya Vidhyaraman (1):
>   octeontx2: Add IPv6 fields to default MKEX profile
> 
>  drivers/net/ethernet/marvell/octeontx2/af/mbox.h   |   5 +-
>  drivers/net/ethernet/marvell/octeontx2/af/npc.h|   6 +-
>  .../ethernet/marvell/octeontx2/af/npc_profile.h| 374 
> +++--
>  .../net/ethernet/marvell/octeontx2/af/rvu_nix.c|  46 ++-
>  .../net/ethernet/marvell/octeontx2/af/rvu_npa.c|   2 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_npc.c|   3 +-
>  .../net/ethernet/marvell/octeontx2/af/rvu_ree.c| 108 +++---
>  .../ethernet/marvell/octeontx2/nic/otx2_common.c   |  23 +-
>  .../ethernet/marvell/octeontx2/nic/otx2_common.h   |   1 +
>  9 files changed, 456 insertions(+), 112 deletions(-)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9063): 
https://lists.yoctoproject.org/g/linux-yocto/message/9063
Mute This Topic: https://lists.yoctoproject.org/mt/76860756/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: update patches for raspberrypi 4b platform

2020-09-17 Thread Bruce Ashfield

In message: [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: 
update patches for raspberrypi 4b platform
on 14/09/2020 meng...@windriver.com wrote:

> From: Limeng 
> 
> Hi Bruce,
> 
> Raspberry pi is updated continuously, so I get some latest patches from 
> raspberry pi git repo
> https://github.com/raspberrypi/linux.git rpi-5.9.y, and intend to merge them 
> into linux-yocto-dev.
> 
> There are 18 patches in my public repo 
> https://github.com/limeng-linux/linux-yocto-develop.git, branch 
> standard/bcm-2xxx-rpi
> Could you please help merge these patches into linux-ycoto-dev kernel, v5.9, 
> branch is standard/bcm-2xxx-rpi?

Thanks for the update!

These are now merged.

Bruce

> 
> diffstat info as below.
> 
>  Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml |  117 
>  Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml  |   18 
>  MAINTAINERS  |8 
>  arch/arm/boot/dts/bcm2711-rpi.dtsi   |1 
>  arch/arm/configs/bcm2711_defconfig   |1 
>  arch/arm/lib/uaccess_with_memcpy.c   |4 
>  drivers/clk/bcm/Kconfig  |1 
>  drivers/clk/bcm/clk-raspberrypi.c|1 
>  drivers/media/i2c/Kconfig|   11 
>  drivers/media/i2c/Makefile   |1 
>  drivers/media/i2c/imx477.c   | 2318 
> +-
>  drivers/media/platform/bcm2835/Kconfig   |   12 
>  drivers/media/platform/bcm2835/bcm2835-unicam.c  |  108 
>  drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c  |9 
>  drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c  |   12 
>  15 files changed, 2523 insertions(+), 99 deletions(-)
> 
> 
> Pull request info as below:
> 
> The following changes since commit 77925f58a52849c22d38490441f15de09345f6f0:
> 
>   Merge branch 'standard/base' into standard/bcm-2xxx-rpi (2020-09-13 
> 22:14:56 -0400)
> 
> are available in the Git repository at:
> 
>   https://github.com/limeng-linux/linux-yocto-develop.git 
> standard/bcm-2xxx-rpi
> 
> for you to fetch changes up to ffd444d9c951f6ee16e032f6c454804c4da9a6e9:
> 
>   brcmfmac: reserve tx credit only when txctl is ready to send (2020-09-14 
> 03:15:21 -0400)
> 
> 
> Chris Blake (1):
>   arm: fix mmap unlocks in uaccess_with_memcpy.c
> 
> Dave Stevenson (3):
>   media: bcm2835-unicam: Always service interrupts
>   media: bcm2835-unicam: Fixup review comments from Hans.
>   media: bcm2835-unicam: Retain packing information on G_FMT
> 
> David Plowman (1):
>   media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1
> 
> Hoegeun Kwon (1):
>   clk: bcm: rpi: Add register to control pixel bvb clk
> 
> Jacko Dirks (1):
>   media: bcm2835: unicam: Fix uninitialized warning
> 
> Laurent Pinchart (1):
>   media: i2c: imx477: Parse and register properties
> 
> Maxime Ripard (3):
>   dt-bindings: display: Add support for the BCM2711 HVS
>   dt-bindings: display: vc4: hdmi: Add BCM2711 HDMI controllers bindings
>   clk: bcm: dvp: Select the reset framework
> 
> Naushir Patuck (3):
>   media: i2c: Add driver for Sony IMX477 sensor
>   media: i2c: imx477: Add support for adaptive frame control
>   media: i2c: imx477: Return correct result on sensor id verification
> 
> Phil Elwell (3):
>   ARM: dts: Add required USB power domain for XHCI
>   brcmfmac: Increase power saving delay to 2s
>   configs: Restore VIDEO_IMX477=m
> 
> Wright Feng (1):
>   brcmfmac: reserve tx credit only when txctl is ready to send
> 
>  Documentation/devicetree/bindings/display/brcm,bcm2711-hdmi.yaml |  117 
> ++
>  Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml  |   18 +-
>  MAINTAINERS  |8 +
>  arch/arm/boot/dts/bcm2711-rpi.dtsi   |1 +
>  arch/arm/configs/bcm2711_defconfig   |1 +
>  arch/arm/lib/uaccess_with_memcpy.c   |4 +-
>  drivers/clk/bcm/Kconfig  |1 +
>  drivers/clk/bcm/clk-raspberrypi.c|1 +
>  drivers/media/i2c/Kconfig|   11 +
>  drivers/media/i2c/Makefile   |1 +
>  drivers/media/i2c/imx477.c   | 2270 
> +++
>  drivers/media/platform/bcm2835/Kconfig   |   12 +-
>  drivers/media/platform/bcm2835/bcm2835-unicam.c  |

Re: [yocto] wvdial

2020-09-17 Thread Maciej Pijanowski



On 17.09.2020 13:35, Maciej Pijanowski wrote:



On 17.09.2020 13:25, Zoltan Kerenyi Nagy wrote:

*now there is only one issue has left:*

/ERROR: ExpansionError during parsing 
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb 
                             | ETA:  0:00:00

Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable 
do_fetch[file-checksums], expression was 
${@bb.fetch.get_checksum_file_list(d)} 
 ${@get_lic_checksum_file_list(d)} which triggered exception 
NoMethodError: Could not find a fetcher which supports the URL: 
'files://typo_pon.wvdial.1.patch'/



I'm sorry, but you I think you really do need a pair of glasses ;)
It's supposed to be file:// not file:// in the URL.


It's supposed to be file:// not files:// in the URL.





This is the bb recipe:

/HOMEPAGE = "http://www.alumnit.ca/wiki/?WvDial;
DESCRIPTION = "WvDial is a program that makes it easy to connect your 
Linux workstation to the Internet."


LICENSE = "LGPLv2"
LIC_FILES_CHKSUM = 
"file://COPYING.LIB;md5=55ca817ccb7d5b5b66355690e9abc605"


inherit pkgconfig

DEPENDS = "wvstreams"
RDEPENDS_${PN} = "ppp"

SRC_URI = "http://${BPN}.googlecode.com/files/${BP}.tar.bz2 
 \

           files://typo_pon.wvdial.1.patch \
          "

SRC_URI[md5sum] = "d81642557d175d8e0818f4721c27dfcf"
SRC_URI[sha256sum] = 
"a2ce46c8c36870a0f2fa92ea64566df7251fb2d8d5aa2f6ef2b08d188287352e"


EXTRA_OEMAKE = ""
export WVLINK="${LD}"

PARALLEL_MAKE = ""

BUILD_CPPFLAGS += "-I${STAGING_INCDIR}/wvstreams"

do_configure() {
    sed -i 's/LDFLAGS+=-luniconf/LIBS+=-luniconf/' ${S}/Makefile
}

do_install() {
    oe_runmake prefix=${D}/usr PPPDIR=${D}/etc/ppp/peers install
}
# http://errors.yoctoproject.org/Errors/Details/186959/
EXCLUDE_FROM_WORLD_libc-musl = "1"/
/
/
Ive re-generated the md5 and sha256 hashes, and all the warnings have 
disapeared.


*Here is the patch:
*
*if I modify teh 3rd line to "Index: wvdial-1.61/files/pon.wvdial.1" 
- the error is the same

*

/Remove warnings found by lintian Last-Update: 2011-01-09 Index: 
wvdial-1.61/pon.wvdial.1 
=== 
--- wvdial-1.61.orig/pon.wvdial.1 2011-01-09 21:33:03.0 +0300 
+++ wvdial-1.61/pon.wvdial.1 2011-01-09 21:33:15.0 +0300 @@ 
-8,13 +8,11 @@ .SH DESCRIPTION .B pon.wvdial .br -.TR .B poff.wvdial 
.br .RS Replacement scripts for pon and poff. .RE -\." .SH SEE ALSO 
.BR wvdial (1), .BR pon (1),/






--
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com  | @3mdeb_com


--
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50712): https://lists.yoctoproject.org/g/yocto/message/50712
Mute This Topic: https://lists.yoctoproject.org/mt/76905081/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] wvdial

2020-09-17 Thread Maciej Pijanowski



On 17.09.2020 13:25, Zoltan Kerenyi Nagy wrote:

*now there is only one issue has left:*

/ERROR: ExpansionError during parsing 
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb 
                           | ETA:  0:00:00

Traceback (most recent call last):
bb.data_smart.ExpansionError: Failure expanding variable 
do_fetch[file-checksums], expression was 
${@bb.fetch.get_checksum_file_list(d)} 
 ${@get_lic_checksum_file_list(d)} which triggered exception 
NoMethodError: Could not find a fetcher which supports the URL: 
'files://typo_pon.wvdial.1.patch'/



I'm sorry, but you I think you really do need a pair of glasses ;)
It's supposed to be file:// not file:// in the URL.



This is the bb recipe:

/HOMEPAGE = "http://www.alumnit.ca/wiki/?WvDial;
DESCRIPTION = "WvDial is a program that makes it easy to connect your 
Linux workstation to the Internet."


LICENSE = "LGPLv2"
LIC_FILES_CHKSUM = 
"file://COPYING.LIB;md5=55ca817ccb7d5b5b66355690e9abc605"


inherit pkgconfig

DEPENDS = "wvstreams"
RDEPENDS_${PN} = "ppp"

SRC_URI = "http://${BPN}.googlecode.com/files/${BP}.tar.bz2 
 \

           files://typo_pon.wvdial.1.patch \
          "

SRC_URI[md5sum] = "d81642557d175d8e0818f4721c27dfcf"
SRC_URI[sha256sum] = 
"a2ce46c8c36870a0f2fa92ea64566df7251fb2d8d5aa2f6ef2b08d188287352e"


EXTRA_OEMAKE = ""
export WVLINK="${LD}"

PARALLEL_MAKE = ""

BUILD_CPPFLAGS += "-I${STAGING_INCDIR}/wvstreams"

do_configure() {
    sed -i 's/LDFLAGS+=-luniconf/LIBS+=-luniconf/' ${S}/Makefile
}

do_install() {
    oe_runmake prefix=${D}/usr PPPDIR=${D}/etc/ppp/peers install
}
# http://errors.yoctoproject.org/Errors/Details/186959/
EXCLUDE_FROM_WORLD_libc-musl = "1"/
/
/
Ive re-generated the md5 and sha256 hashes, and all the warnings have 
disapeared.


*Here is the patch:
*
*if I modify teh 3rd line to "Index: wvdial-1.61/files/pon.wvdial.1" - 
the error is the same

*

/Remove warnings found by lintian Last-Update: 2011-01-09 Index: 
wvdial-1.61/pon.wvdial.1 
=== 
--- wvdial-1.61.orig/pon.wvdial.1 2011-01-09 21:33:03.0 +0300 
+++ wvdial-1.61/pon.wvdial.1 2011-01-09 21:33:15.0 +0300 @@ 
-8,13 +8,11 @@ .SH DESCRIPTION .B pon.wvdial .br -.TR .B poff.wvdial 
.br .RS Replacement scripts for pon and poff. .RE -\." .SH SEE ALSO 
.BR wvdial (1), .BR pon (1),/






--
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50711): https://lists.yoctoproject.org/g/yocto/message/50711
Mute This Topic: https://lists.yoctoproject.org/mt/76905081/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] wvdial

2020-09-17 Thread Zoltan Kerenyi Nagy

*now there is only one issue has left:*



*ERROR: ExpansionError during parsing
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb

  | ETA:  0:00:00Traceback (most recent
call last):bb.data_smart.ExpansionError: Failure expanding variable
do_fetch[file-checksums], expression was
${@bb.fetch.get_checksum_file_list(d)}  ${@get_lic_checksum_file_list(d)}
which triggered exception NoMethodError: Could not find a fetcher which
supports the URL: 'files://typo_pon.wvdial.1.patch'*

This is the bb recipe:


































*HOMEPAGE = "http://www.alumnit.ca/wiki/?WvDial
"DESCRIPTION = "WvDial is a program
that makes it easy to connect your Linux workstation to the
Internet."LICENSE = "LGPLv2"LIC_FILES_CHKSUM =
"file://COPYING.LIB;md5=55ca817ccb7d5b5b66355690e9abc605"inherit
pkgconfigDEPENDS = "wvstreams"RDEPENDS_${PN} = "ppp"SRC_URI =
"http://${BPN}.googlecode.com/files/${BP}.tar.bz2
 \
 files://typo_pon.wvdial.1.patch \  "SRC_URI[md5sum] =
"d81642557d175d8e0818f4721c27dfcf"SRC_URI[sha256sum] =
"a2ce46c8c36870a0f2fa92ea64566df7251fb2d8d5aa2f6ef2b08d188287352e"EXTRA_OEMAKE
= ""export WVLINK="${LD}"PARALLEL_MAKE = ""BUILD_CPPFLAGS +=
"-I${STAGING_INCDIR}/wvstreams"do_configure() {sed -i
's/LDFLAGS+=-luniconf/LIBS+=-luniconf/' ${S}/Makefile}do_install() {
oe_runmake prefix=${D}/usr PPPDIR=${D}/etc/ppp/peers install}#
http://errors.yoctoproject.org/Errors/Details/186959/
EXCLUDE_FROM_WORLD_libc-musl
= "1"*

Ive  re-generated the md5 and sha256 hashes, and all the warnings have
disapeared.


*Here is the patch: *

*if I modify teh 3rd line to "Index: wvdial-1.61/files/pon.wvdial.1" - the
error is the same*

*Remove warnings found by lintian
Last-Update: 2011-01-09
Index: wvdial-1.61/pon.wvdial.1
===
--- wvdial-1.61.orig/pon.wvdial.1   2011-01-09 21:33:03.0 +0300
+++ wvdial-1.61/pon.wvdial.12011-01-09 21:33:15.0 +0300
@@ -8,13 +8,11 @@
 .SH DESCRIPTION
 .B pon.wvdial
 .br
-.TR
 .B poff.wvdial
 .br
 .RS
 Replacement scripts for pon and poff.
 .RE
-\."
 .SH SEE ALSO
 .BR wvdial (1),
 .BR pon (1),*

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50710): https://lists.yoctoproject.org/g/yocto/message/50710
Mute This Topic: https://lists.yoctoproject.org/mt/76905081/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH yocto-autobuilder-helper] auh: correct the SMTP server in config file

2020-09-17 Thread Alexander Kanavin

Michael Halstead has confirmed this.

Signed-off-by: Alexander Kanavin 
---
 scripts/auh-config/upgrade-helper.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/auh-config/upgrade-helper.conf 
b/scripts/auh-config/upgrade-helper.conf
index b012600..5284b4a 100644
--- a/scripts/auh-config/upgrade-helper.conf
+++ b/scripts/auh-config/upgrade-helper.conf
@@ -9,7 +9,7 @@ blacklist=linux-libc-headers linux-yocto alsa-utils-scripts 
build-appliance-imag
 # only recipes belonging to maintainers in whitelist will be attempted
 #maintainers_whitelist=anibal.li...@linux.intel.com
 # SMTP server
-smtp=smtp1.yoctoproject.org:25
+smtp=mail.yoctoproject.org:25
 # from whom should the mails arrive
 from=a...@auh.yoctoproject.org
 # who should get the status mail with statistics, at the end
-- 
2.28.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50709): https://lists.yoctoproject.org/g/yocto/message/50709
Mute This Topic: https://lists.yoctoproject.org/mt/76906938/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] RFC: Changes to meta-kernel layer

2020-09-17 Thread Jack Mitchell

On 17/09/2020 10:40, Bas Mevissen wrote:
> On 2020-09-17 10:43, Paul Barker wrote:
> 
>> Hi folks,
>>
>> After a bit of a break I'm looking again at the meta-kernel layer and
>> I've got some changes planned. I'd like to get some feedback on these
>> from anyone who has looked at or used the meta-kernel layer.
>>
>> 1) Change the name to meta-vanilla-kernel. This reflects the focus on
>> providing a fast moving layer for vanilla kernel recipes, covering
>> only what is available on kernel.org. Other common kernel recipes
>> (e.g. Linaro or Android common kernels) will no longer be considered
>> for acceptance into this layer. This clear focus should hopefully
>> reduce some of the confusion about the goals of this layer.
>>
> 
> I would suggest calling it something like meta-kernel.org then. Naming
> something "vanilla" might cause confusion as well.

I wasn't going to be blamed for the bike shedding of this but as we've
gotten started I'll stick my oar in. My suggestion would be
meta-mainline-kernel, meta-linux-kernel or potentially
meta-upstream-kernel but I'm not so keen on that. Vanilla is a confusing
term for people not in the game and you know at some point there will be
a "vanilla-pi" or "vanilla" board where you're going to hit confusion.

As an aside I saw no issues with meta-kernel as it's _the_ Linux kernel
from _the_ Linux kernel git repositories. Confusion due to doublespeak
from downstream kernel vendors should be corrected and not adhered to.

> 
>> 2) The dunfell branch will no longer get new non-LTS kernel recipes.
>> Providing non-LTS recipes on a stable branch has led to people
>> depending on kernels which are now out of their support period - I'd
>> like to drop the recipes for the 5.3.y and 5.6.y kernels but users are
>> depending on them so I'll have to keep them. To avoid this
>> proliferating, only LTS kernels and the bleeding edge mainline recipe
>> will be updated on the stable branch from now >>
>> 3) Aggressively drop end-of-life kernels on the master branch.
>>
>> 4) Drop all non-LTS kernel recipes in the gatesgarth branch when it is
>> created.
>>

I think these are fair, I can't speak for how other people are using the
layer but I would imagine as with most embedded boards, they're using
the tooling rather than the plain upstream recipes and the real value is
in catching problems with -next kernel compilation early and the
fixes/features pushed back to kernel.bbclass.

>> 5) Document the test coverage for meta-kernel. We don't test perf,
>> lttng or any out-of-tree modules. This layer isn't meant to replace
>> the linux-yocto recipes, the goals are different. If you're releasing
>> products based on meta-kernel you obviously need to do your own
>> testing on the components you're actually using.

I wouldn't be expecting anything more than basic build and boot on qemu
to be fair. Again, IMO the value of this is in the toolchain test and
tooling.

>>
>> 6) Document the policy for kernel patches. Patches for the kernel will
>> only be carried in this layer as a last resort. Kernel patches should
>> be submitted upstream and go through the usual process for inclusion
>> in the stable kernel releases.

Compilation patches only I would say.

>>
>> 7) Disable GitLab CI for this layer. It's costing me about £70 per
>> month to run CI for this layer and I need to eliminate that expense.
>> If anyone can sponsor this or host the CI service that would be welcome.
>>
>> 8) Add Jon Mason and Ross Burton (both at ARM) as backup maintainers
>> to reduce the bus factor for the layer. I'll continue to be the
>> primary maintainer for this layer but this will give some coverage if
>> I'm unable to continue working on it.
>>
>> Thanks,
>>
>> -- 
>>
>> Paul Barker
>> Konsulko Group
>>

Cheers,
Jack.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50708): https://lists.yoctoproject.org/g/yocto/message/50708
Mute This Topic: https://lists.yoctoproject.org/mt/76905426/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] split rootfs into partitions for rauc

2020-09-17 Thread Daniel Ammann

Hi

Is it possible to split a rootfs image into two images for two partitions?
Let's say I have a rootfs, but I want to split out /usr/local/applicationx into
a separate image so that I can have it on a different partition. The goal is to
have two ext4 images, one with everything except /usr/local/applicationx and
one with just /usr/local/applicationx.

Thanks, Daniel

-- 
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 550 50 67

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50707): https://lists.yoctoproject.org/g/yocto/message/50707
Mute This Topic: https://lists.yoctoproject.org/mt/76906026/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] RFC: Changes to meta-kernel layer

2020-09-17 Thread Bas Mevissen


On 2020-09-17 10:43, Paul Barker wrote:


Hi folks,

After a bit of a break I'm looking again at the meta-kernel layer and 
I've got some changes planned. I'd like to get some feedback on these 
from anyone who has looked at or used the meta-kernel layer.


1) Change the name to meta-vanilla-kernel. This reflects the focus on 
providing a fast moving layer for vanilla kernel recipes, covering only 
what is available on kernel.org. Other common kernel recipes (e.g. 
Linaro or Android common kernels) will no longer be considered for 
acceptance into this layer. This clear focus should hopefully reduce 
some of the confusion about the goals of this layer.




I would suggest calling it something like meta-kernel.org then. Naming 
something "vanilla" might cause confusion as well.


2) The dunfell branch will no longer get new non-LTS kernel recipes. 
Providing non-LTS recipes on a stable branch has led to people 
depending on kernels which are now out of their support period - I'd 
like to drop the recipes for the 5.3.y and 5.6.y kernels but users are 
depending on them so I'll have to keep them. To avoid this 
proliferating, only LTS kernels and the bleeding edge mainline recipe 
will be updated on the stable branch from now on.


I would recommend maintaining a "kernel-stable" moving target recipe 
that tracks the latest stable version of kernel.org. This is of use for 
people needing a very recent kernel, while needing a stable environment 
for the rest of the system (so where master is no option).



3) Aggressively drop end-of-life kernels on the master branch.

Always good to keep the amount of kernels at an absolut minimum to limit 
the amount of testing and maintenance.


4) Drop all non-LTS kernel recipes in the gatesgarth branch when it is 
created.



See 2); additionally the next-to-be-lts might be considered

5) Document the test coverage for meta-kernel. We don't test perf, 
lttng or any out-of-tree modules. This layer isn't meant to replace the 
linux-yocto recipes, the goals are different. If you're releasing 
products based on meta-kernel you obviously need to do your own testing 
on the components you're actually using.


6) Document the policy for kernel patches. Patches for the kernel will 
only be carried in this layer as a last resort. Kernel patches should 
be submitted upstream and go through the usual process for inclusion in 
the stable kernel releases.


7) Disable GitLab CI for this layer. It's costing me about £70 per 
month to run CI for this layer and I need to eliminate that expense. If 
anyone can sponsor this or host the CI service that would be welcome.


8) Add Jon Mason and Ross Burton (both at ARM) as backup maintainers to 
reduce the bus factor for the layer. I'll continue to be the primary 
maintainer for this layer but this will give some coverage if I'm 
unable to continue working on it.



And spreading the workload of course!


Thanks,

--

Paul Barker
Konsulko Group




Regards,

Bas.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50706): https://lists.yoctoproject.org/g/yocto/message/50706
Mute This Topic: https://lists.yoctoproject.org/mt/76905426/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] RFC: Changes to meta-kernel layer

2020-09-17 Thread Paul Barker

Hi folks,

After a bit of a break I'm looking again at the meta-kernel layer and I've
got some changes planned. I'd like to get some feedback on these from
anyone who has looked at or used the meta-kernel layer.

1) Change the name to meta-vanilla-kernel. This reflects the focus on
providing a fast moving layer for vanilla kernel recipes, covering only
what is available on kernel.org. Other common kernel recipes (e.g. Linaro
or Android common kernels) will no longer be considered for acceptance into
this layer. This clear focus should hopefully reduce some of the confusion
about the goals of this layer.

2) The dunfell branch will no longer get new non-LTS kernel recipes.
Providing non-LTS recipes on a stable branch has led to people depending on
kernels which are now out of their support period - I'd like to drop the
recipes for the 5.3.y and 5.6.y kernels but users are depending on them so
I'll have to keep them. To avoid this proliferating, only LTS kernels and
the bleeding edge mainline recipe will be updated on the stable branch from
now on.

3) Aggressively drop end-of-life kernels on the master branch.

4) Drop all non-LTS kernel recipes in the gatesgarth branch when it is
created.

5) Document the test coverage for meta-kernel. We don't test perf, lttng or
any out-of-tree modules. This layer isn't meant to replace the linux-yocto
recipes, the goals are different. If you're releasing products based on
meta-kernel you obviously need to do your own testing on the components
you're actually using.

6) Document the policy for kernel patches. Patches for the kernel will only
be carried in this layer as a last resort. Kernel patches should be
submitted upstream and go through the usual process for inclusion in the
stable kernel releases.

7) Disable GitLab CI for this layer. It's costing me about £70 per month to
run CI for this layer and I need to eliminate that expense. If anyone can
sponsor this or host the CI service that would be welcome.

8) Add Jon Mason and Ross Burton (both at ARM) as backup maintainers to
reduce the bus factor for the layer. I'll continue to be the primary
maintainer for this layer but this will give some coverage if I'm unable to
continue working on it.

Thanks,

-- 
Paul Barker
Konsulko Group

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50705): https://lists.yoctoproject.org/g/yocto/message/50705
Mute This Topic: https://lists.yoctoproject.org/mt/76905426/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] wvdial

2020-09-17 Thread Bas Mevissen


On 2020-09-17 10:02, Zoltan Kerenyi Nagy wrote:


Hi,

Here is the error now, all the files are there, it says that 
04_signed_request.diff is not there:


WARNING: wvstreams-4.6.1-r0 do_fetch: Failed to fetch URL 
file://04_signed_request.diff, attempting MIRRORS if available
ERROR: wvstreams-4.6.1-r0 do_fetch: Fetcher failure: Unable to find 
file file://04_signed_request.diff anywhere. The paths that were 
searched were:

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/
/home/kerenyiz/oe-core/build/downloads
ERROR: wvstreams-4.6.1-r0 do_fetch: Fetcher failure for URL: 
'file://04_signed_request.diff'. Unable to fetch URL from any source.


It is the first local file on the list, so this hints that it is 
probably a file location issue and not a file naming one.



ERROR: wvstreams-4.6.1-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/home/kerenyiz/oe-core/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/wvstreams/4.6.1-r0/temp/log.do_fetch.8864
ERROR: Task 
(/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams_4.6.1.bb:do_fetch) 
failed with exit code '1'


Here i sthe folder structure:

├── file


Here is your problem: this directory should be named "wvstreams"


│   ├── 0001-build-fix-parallel-make.patch
│   ├── 0001-Check-for-limits.h-during-configure.patch
│   ├── 0001-Forward-port-to-OpenSSL-1.1.x.patch
│   ├── 0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch
│   ├── 0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch
│   ├── 0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch
│   ├── 0004-wvcrash-Replace-use-of-basename-API.patch
│   ├── 0005-check-for-libexecinfo-during-configure.patch
│   ├── 04_signed_request.diff
│   ├── 05_gcc.diff
│   ├── 06_gcc-4.7.diff
│   ├── 07_buildflags.diff
│   ├── argp.patch
│   ├── gcc-6.patch
│   └── openssl-buildfix.patch
└── wvstreams_4.6.1.bb

And this is the recipie file:

HOMEPAGE = "http://alumnit.ca/wiki/index.php?page=WvStreams;
SUMMARY = "WvStreams is a network programming library in C++"

LICENSE = "LGPLv2"
LIC_FILES_CHKSUM = 
"file://LICENSE;md5=55ca817ccb7d5b5b66355690e9abc605"


DEPENDS = "zlib openssl (>= 0.9.8) dbus readline"
DEPENDS_append_libc-musl = " argp-standalone libexecinfo"

SRC_URI = "http://${BPN}.googlecode.com/files/${BP}.tar.gz \
file://04_signed_request.diff \
file://05_gcc.diff \
file://06_gcc-4.7.diff \
file://07_buildflags.diff \
file://gcc-6.patch \
file://argp.patch \
file://0001-Check-for-limits.h-during-configure.patch \
file://0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch \
file://0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch 
\

file://0004-wvcrash-Replace-use-of-basename-API.patch \
file://0005-check-for-libexecinfo-during-configure.patch \
file://0001-build-fix-parallel-make.patch \
file://0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch \
file://openssl-buildfix.patch \
file://0001-Forward-port-to-OpenSSL-1.1.x.patch \
"

SRC_URI[md5sum] =

Re: [yocto] wvdial

2020-09-17 Thread Quentin Schulz

Hi

On Thu, Sep 17, 2020 at 10:02:47AM +0200, Zoltan Kerenyi Nagy wrote:
[...]
> file://04_signed_request.diff anywhere. The paths that were searched were:
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/nodistro
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/nodistro
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/nodistro
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/barix-ipam400
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/barix-ipam400
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/barix-ipam400
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/sun8i
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/sun8i
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/sun8i
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/armv7ve
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/armv7ve
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/armv7ve
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/arm
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/arm
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/arm
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/
> 
> /home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/
>   /home/kerenyiz/oe-core/build/downloadsERROR: wvstreams-4.6.1-r0 do_fetch:
> Fetcher failure for URL: 'file://04_signed_request.diff'. Unable to fetch
> URL from any source.ERROR: wvstreams-4.6.1-r0 do_fetch: Function failed:
> base_do_fetchERROR: Logfile of failure stored in:
> /home/kerenyiz/oe-core/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/wvstreams/4.6.1-r0/temp/log.do_fetch.8864ERROR:
> Task
> (/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams_4.6.1.bb:do_fetch)
> failed with exit code '1'*
> 
> *Here i sthe folder structure:*
> 
> ├── file
  ^^^

If you read carefully the paths that were searched you'll see that this
directory is missing a trailing s :) It should be `files` and not `file`.

Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50703): https://lists.yoctoproject.org/g/yocto/message/50703
Mute This Topic: https://lists.yoctoproject.org/mt/76905081/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] wvdial

2020-09-17 Thread Maciej Pijanowski



On 17.09.2020 10:02, Zoltan Kerenyi Nagy wrote:

Hi,

Here is the error now, all the files are there, it says that 
*04_signed_request.diff* is not there:*

*

/WARNING: wvstreams-4.6.1-r0 do_fetch: Failed to fetch URL 
file://04_signed_request.diff, attempting MIRRORS if available
ERROR: wvstreams-4.6.1-r0 do_fetch: Fetcher failure: Unable to find 
file file://04_signed_request.diff anywhere. The paths that were 
searched were:

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/nodistro
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/barix-ipam400
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/sun8i
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/armv7ve
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/arm
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/
/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/
    /home/kerenyiz/oe-core/build/downloads
ERROR: wvstreams-4.6.1-r0 do_fetch: Fetcher failure for URL: 
'file://04_signed_request.diff'. Unable to fetch URL from any source.

ERROR: wvstreams-4.6.1-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: 
/home/kerenyiz/oe-core/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/wvstreams/4.6.1-r0/temp/log.do_fetch.8864
ERROR: Task 
(/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams_4.6.1.bb:do_fetch) 
failed with exit code '1'/


*Here i sthe folder structure:*

├── file
Well, as you can see this directory is not one of the search paths in 
the log above. Rename file -> files

│ ├── 0001-build-fix-parallel-make.patch
│   ├── 0001-Check-for-limits.h-during-configure.patch
│   ├── 0001-Forward-port-to-OpenSSL-1.1.x.patch
│   ├── 0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch
│   ├── 0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch
│   ├── 0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch
│   ├── 0004-wvcrash-Replace-use-of-basename-API.patch
│   ├── 0005-check-for-libexecinfo-during-configure.patch
│   ├── 04_signed_request.diff
│   ├── 05_gcc.diff
│   ├── 06_gcc-4.7.diff
│   ├── 07_buildflags.diff
│   ├── argp.patch
│   ├── gcc-6.patch
│   └── openssl-buildfix.patch
└── wvstreams_4.6.1.bb 

*And this is the recipie file:*

/HOMEPAGE = "http://alumnit.ca/wiki/index.php?page=WvStreams;
SUMMARY = "WvStreams is a network programming library in C++"

LICENSE = "LGPLv2"
LIC_FILES_CHKSUM = "file://LICENSE;md5=55ca817ccb7d5b5b66355690e9abc605"

DEPENDS = "zlib openssl (>= 0.9.8) dbus readline"
DEPENDS_append_libc-musl = " argp-standalone libexecinfo"

SRC_URI = "http://${BPN}.googlecode.com/files/${BP}.tar.gz 
 \

           file://04_signed_request.diff \
           file://05_gcc.diff \
           file://06_gcc-4.7.diff \
           file://07_buildflags.diff \
           file://gcc-6.patch \
           file://argp.patch \
 file://0001-Check-for-limits.h-during-configure.patch \
 file://0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch \
 file://0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch \
 file://0004-wvcrash-Replace-use-of-basename-API.patch \
 file://0005-check-for-libexecinfo-during-configure.patch \
           file://0001-build-fix-parallel-make.patch \
 file://0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch \

[yocto] wvdial

2020-09-17 Thread Zoltan Kerenyi Nagy

Hi,

Here is the error now, all the files are there, it says that
*04_signed_request.diff* is not there:

























*WARNING: wvstreams-4.6.1-r0 do_fetch: Failed to fetch URL
file://04_signed_request.diff, attempting MIRRORS if availableERROR:
wvstreams-4.6.1-r0 do_fetch: Fetcher failure: Unable to find file
file://04_signed_request.diff anywhere. The paths that were searched were:

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/nodistro

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/nodistro

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/nodistro

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/barix-ipam400

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/barix-ipam400

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/barix-ipam400

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/sun8i

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/sun8i

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/sun8i

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/armv7ve

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/armv7ve

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/armv7ve

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/arm

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/arm

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/arm

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams-4.6.1/

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams/

/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/files/
  /home/kerenyiz/oe-core/build/downloadsERROR: wvstreams-4.6.1-r0 do_fetch:
Fetcher failure for URL: 'file://04_signed_request.diff'. Unable to fetch
URL from any source.ERROR: wvstreams-4.6.1-r0 do_fetch: Function failed:
base_do_fetchERROR: Logfile of failure stored in:
/home/kerenyiz/oe-core/build/tmp-glibc/work/cortexa7hf-neon-vfpv4-oe-linux-gnueabi/wvstreams/4.6.1-r0/temp/log.do_fetch.8864ERROR:
Task
(/home/kerenyiz/oe-core/build/../stuff/meta-openembedded/meta-oe/recipes-connectivity/wvstreams/wvstreams_4.6.1.bb:do_fetch)
failed with exit code '1'*

*Here i sthe folder structure:*

├── file
│   ├── 0001-build-fix-parallel-make.patch
│   ├── 0001-Check-for-limits.h-during-configure.patch
│   ├── 0001-Forward-port-to-OpenSSL-1.1.x.patch
│   ├── 0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch
│   ├── 0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch
│   ├── 0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch
│   ├── 0004-wvcrash-Replace-use-of-basename-API.patch
│   ├── 0005-check-for-libexecinfo-during-configure.patch
│   ├── 04_signed_request.diff
│   ├── 05_gcc.diff
│   ├── 06_gcc-4.7.diff
│   ├── 07_buildflags.diff
│   ├── argp.patch
│   ├── gcc-6.patch
│   └── openssl-buildfix.patch
└── wvstreams_4.6.1.bb

*And this is the recipie file:*
























































*HOMEPAGE = "http://alumnit.ca/wiki/index.php?page=WvStreams
"SUMMARY = "WvStreams is a
network programming library in C++"LICENSE = "LGPLv2"LIC_FILES_CHKSUM =
"file://LICENSE;md5=55ca817ccb7d5b5b66355690e9abc605"DEPENDS = "zlib
openssl (>= 0.9.8) dbus readline"DEPENDS_append_libc-musl = "
argp-standalone libexecinfo"SRC_URI =
"http://${BPN}.googlecode.com/files/${BP}.tar.gz
 \
 file://04_signed_request.diff \   file://05_gcc.diff \
 file://06_gcc-4.7.diff \   file://07_buildflags.diff \
 file://gcc-6.patch \   file://argp.patch \
 file://0001-Check-for-limits.h-during-configure.patch \
 file://0002-wvtask-Dont-use-ucontext-on-non-glibc-systems.patch \
 file://0003-wvtask-Check-for-HAVE_LIBC_STACK_END-only-on-glibc-s.patch \
 file://0004-wvcrash-Replace-use-of-basename-API.patch \
 file://0005-check-for-libexecinfo-during-configure.patch \
 file://0001-build-fix-parallel-make.patch \
 file://0002-wvrules.mk-Use-_DEFAULT_SOURCE.patch \
 file://openssl-buildfix.patch \
 file://0001-Forward-port-to-OpenSSL-1.1.x.patch \
 "SRC_URI[md5sum] =

Re: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong cast that may cause wrong truncation

2020-09-17 Thread He Zhe

Hi Bruce,

This patch is missing for linux-yocto-dev from the latest rebase.

Thanks,
Zhe

On 8/21/20 3:03 AM, Bruce Ashfield wrote:
> merged to linux-yocto-dev standard/* and linux-yocto v5.8/standard/*
>
> Bruce
>
>
> In message: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong cast 
> that may cause wrong truncation
> on 21/08/2020 zhe...@windriver.com wrote:
>
>> From: He Zhe 
>>
>> tail is a pointer while buftail.fp is a u32.
>>
>> arch/arm64/kernel/perf_callchain.c:100:6: warning: cast from pointer to
>> integer of different size [-Wpointer-to-int-cast]
>>   100 |  if ((u32)tail + 4 >= buftail.fp)
>>   |  ^
>> arch/arm64/kernel/perf_callchain.c:103:9: warning: cast to pointer from
>> integer of different size [-Wint-to-pointer-cast]{noformat}
>>   103 |  return (struct compat_frame_tail __user *)(buftail.fp - 4);
>>   | ^
>>
>> Fixes: 8818670c17d2 ("arm64/perf: fix backtrace for AAPCS with FP enabled")
>> Signed-off-by: He Zhe 
>> ---
>>  arch/arm64/kernel/perf_callchain.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/perf_callchain.c 
>> b/arch/arm64/kernel/perf_callchain.c
>> index 1be96e3631ea..a4b0864c4e32 100644
>> --- a/arch/arm64/kernel/perf_callchain.c
>> +++ b/arch/arm64/kernel/perf_callchain.c
>> @@ -97,10 +97,10 @@ compat_user_backtrace(struct compat_frame_tail __user 
>> *tail,
>>   * Frame pointers should strictly progress back up the stack
>>   * (towards higher addresses).
>>   */
>> -if ((u32)tail + 4 >= buftail.fp)
>> +if ((u64)tail + 4 >= (u64)buftail.fp)
>>  return NULL;
>>  
>> -return (struct compat_frame_tail __user *)(buftail.fp - 4);
>> +return (struct compat_frame_tail __user *)((u64)buftail.fp - 4);
>>  }
>>  #endif /* CONFIG_COMPAT */
>>  
>> -- 
>> 2.17.1
>>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9060): 
https://lists.yoctoproject.org/g/linux-yocto/message/9060
Mute This Topic: https://lists.yoctoproject.org/mt/76312403/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.4/standard/base][PATCH] kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE

2020-09-17 Thread Xulin Sun

From: Muchun Song 

commit 10de795a5addd1962406796a6e13ba6cc0fc6bee upstream

Fix compiler warning(as show below) for !CONFIG_KPROBES_ON_FTRACE.

kernel/kprobes.c: In function 'kill_kprobe':
kernel/kprobes.c:1116:33: warning: statement with no effect
[-Wunused-value]
 1116 | #define disarm_kprobe_ftrace(p) (-ENODEV)
  | ^
kernel/kprobes.c:2154:3: note: in expansion of macro
'disarm_kprobe_ftrace'
 2154 |   disarm_kprobe_ftrace(p);

Link: https://lore.kernel.org/r/20200805142136.0331f...@canb.auug.org.au
Link: https://lkml.kernel.org/r/20200805172046.19066-1-songmuc...@bytedance.com

Reported-by: Stephen Rothwell 
Fixes: 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at 
kprobe_ftrace_handler")
Acked-by: Masami Hiramatsu 
Acked-by: John Fastabend 
Signed-off-by: Muchun Song 
Signed-off-by: Steven Rostedt (VMware) 
Signed-off-by: Xulin Sun 
---
 kernel/kprobes.c | 17 ++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/kernel/kprobes.c b/kernel/kprobes.c
index bbff4bccb885..6cc1d961f56a 100644
--- a/kernel/kprobes.c
+++ b/kernel/kprobes.c
@@ -1076,9 +1076,20 @@ static int disarm_kprobe_ftrace(struct kprobe *p)
ipmodify ? _ipmodify_enabled : _ftrace_enabled);
 }
 #else  /* !CONFIG_KPROBES_ON_FTRACE */
-#define prepare_kprobe(p)  arch_prepare_kprobe(p)
-#define arm_kprobe_ftrace(p)   (-ENODEV)
-#define disarm_kprobe_ftrace(p)(-ENODEV)
+static inline int prepare_kprobe(struct kprobe *p)
+{
+   return arch_prepare_kprobe(p);
+}
+
+static inline int arm_kprobe_ftrace(struct kprobe *p)
+{
+   return -ENODEV;
+}
+
+static inline int disarm_kprobe_ftrace(struct kprobe *p)
+{
+   return -ENODEV;
+}
 #endif
 
 /* Arm a kprobe with text_mutex */
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9059): 
https://lists.yoctoproject.org/g/linux-yocto/message/9059
Mute This Topic: https://lists.yoctoproject.org/mt/76904129/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto recipe for Tailscale #yocto #golang

[yocto] [meta-zephyr][PATCH] zephyr-kernel: add Zephyr RTOS version 2.3.0 support

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

[yocto] do_unpack() ISO Image

[linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 0/2] Delete mainline content

[linux-yocto][PATCH 2/2] arm64: zynqmp: delete mainline dts content

[linux-yocto] v5.2.x - stable updates comprising v5.2.60

Re: [yocto] Emulator tool for imx8m #linux #devtool #yocto

[yocto] QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

Re: [yocto] [yocto-builds] relocate_sdk.py is failing when installing yocto3.1.2 SDK

Re: [yocto] Emulator tool for imx8m #linux #devtool #yocto

Re: [linux-yocto][linux-yocto v5.4/standard/base][PATCH] kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE

[yocto] Emulator tool for imx8m #linux #devtool #yocto

Re: [linux-yocto][linux-yocto v5.4/standard/cn96xx] marvell-cn96xx for linux-yocto v5.4

Re: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong cast that may cause wrong truncation

Re: [linux-yocto][linux-yocto-dev standard/cn96xx] marvell-cn96xx for linux-yocto-dev v5.9

Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: update patches for raspberrypi 4b platform

Re: [yocto] wvdial

Re: [yocto] wvdial

[yocto] wvdial

[yocto] [PATCH yocto-autobuilder-helper] auh: correct the SMTP server in config file

Re: [yocto] RFC: Changes to meta-kernel layer

[yocto] split rootfs into partitions for rauc

Re: [yocto] RFC: Changes to meta-kernel layer

[yocto] RFC: Changes to meta-kernel layer

Re: [yocto] wvdial

Re: [yocto] wvdial

Re: [yocto] wvdial

[yocto] wvdial

Re: [linux-yocto] [standard/base] [PATCH] arm64/perf: Fix wrong cast that may cause wrong truncation

[linux-yocto][linux-yocto v5.4/standard/base][PATCH] kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE

31 matches

Site Navigation

Mail list logo

Footer information