[linux-yocto] [PATCH] Backport iSMT patch from mainline kernel to linux-yocto-4.1
From: Raymond TanHi Bruce, This is the patch to backport Intel Denverton patches on iSMT that are available in mainline Linux Kernel. Please review and provide feedback, if any. Thanks, Raymond Tan Mika Westerberg (1): i2c: ismt: Add Intel DNV PCI ID drivers/i2c/busses/i2c-ismt.c | 2 ++ 1 file changed, 2 insertions(+) -- 2.9.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] Help with DISTRO settings
On Sun, Jul 24, 2016 at 7:38 AM, Khem Rajwrote: > On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingate wrote: >> Ah, I found it. I had inadvertently deleted one line >> (DISTRO="mydistro") from my layer's conf/layer.conf. >> >> Am I doing this right though? Do I need DISTRO="mydistro" in both >> conf/layer.conf and conf/distro/mydistro.conf? > > Just conf/distro/mydistro.conf is needed. Well, it didn't work if it is only in conf/distro/mydistro.conf. I had to have it in conf/layer.conf as well. >> Removing it from >> either doesn't work, but it seems redundant to put it in mydistro.conf >> as well. > > did you make any other changes ? Not that I know of. It stopped working when it was mistakenly removed from conf/layer.conf. Started working again when I put it back in. And just to test it, I removed it from conf/distro/mydistro.conf and that also didn't work. I have to have it in both places. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package VersionUpstream version Maintainer NoUpgradeReason - --- -- perl 5.22.1 5.24.1Alejandro Hernandez texinfo 6.06.1 Alejandro Hernandez python-git2.0.5 2.0.7 Alejandro Hernandez python-numpy 1.11.0 1.11.1Alejandro Hernandez ruby 2.2.5 2.3.1 Alejandro Hernandez python3 3.5.1 3.5.2 Alejandro Hernandez python-native 2.7.11 2.7.12Alejandro Hernandez python3-git 1.0.2 2.0.7 Alejandro Hernandez cronie1.5.0 1.5.1 Alejandro Hernandez python-pexpect4.1.0 4.2.0 Alejandro Hernandez swig 3.0.8 3.0.10Alejandro Hernandez python3-setuptools22.0.5 25.0.0Alejandro Hernandez python-setuptools 22.0.5 25.0.0Alejandro Hernandez perl-native 5.22.1 5.24.1Alejandro Hernandez python3-native3.5.1 3.5.2 Alejandro Hernandez python2.7.11 2.7.12Alejandro Hernandez liberation-fonts 1.04 2.00.1Alexander Kanavin 2.x depends on fontforge pa... gnutls3.5.1 3.5.2 Alexander Kanavin libwebp 0.5.0 0.5.1 Alexander Kanavin nss 3.24 3.25 Alexander Kanavin lighttpd 1.4.39 1.4.40Alexander Kanavin ffmpeg3.13.1.1 Alexander Kanavin libassuan 2.4.2 2.4.3 Alexander Kanavin procps3.3.11 3.3.12Alexander Kanavin cmake 3.5.2 3.6.1 Alexander Kanavin cmake-native 3.5.2 3.6.1 Alexander Kanavin libidn1.32 1.33 Alexander Kanavin mkelfimage4.0+gitX 4.4+gitAUTOINC+58... Alexander Kanavin mkelfimage has been removed... mpg1231.23.5 1.23.6Alexander Kanavin dpkg 1.18.7 1.18.9Aníbal Limón pinentry 0.9.2 0.9.7 Armin Kuster guilt-native 0.35+gitX 0.36+gitAUTOINC+2... Bruce Ashfield linux-libc-headers4.44.7 Bruce Ashfield linux-yocto-rt4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield linux-yocto 4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield linux-yocto-tiny 4.4.14+gitX4.4.15+gitAUTOINC... Bruce Ashfield kmod-native 22+gitX23+gitAUTOINC+65a... Chen Qi curl 7.49.1 7.50.0Chen Qi kmod 22+gitX23+gitAUTOINC+65a... Chen Qi u-boot-fw-utils v2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-boot-mkimagev2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko u-bootv2016.03+gitX v2016.07+gitAUTOI... Denys Dmytriyenko createrepo0.4.11 0.10.4Hongxu Jia Versions after 0.9.* use YU... ncurses 6.0+20160319 6.0+20160625 Hongxu Jia man-pages 4.06 4.07 Hongxu Jia libgcrypt 1.7.0 1.7.2 Hongxu Jia gnupg 2.1.12 2.1.14Hongxu Jia libinput 1.3.0 1.4.0 Jussi Kukkonen xf86-input-synaptics 1.8.3 1.8.99.1 Jussi Kukkonen sgmlspl-native1.1+gitX 1.03+gitAUTOINC+f... Jussi Kukkonen dropbear 2016.732016.74 Jussi Kukkonen augeas1.4.0 1.5.0 Jussi Kukkonen libgpg-error 1.23 1.24 Jussi Kukkonen vte 0.44.1 0.44.2Jussi Kukkonen xserver-xorg 1.18.3 1.18.4Jussi Kukkonen wayland-protocols 1.41.5 Jussi Kukkonen
Re: [linux-yocto] yocto-kernel-cache][PATCH] features: add new rpmb feature
On 2016-07-23 8:02 AM, Tomas Winkler wrote: Replay Protected Memory Block (RPMB) subsystem The feature provides 3 configurations 1. Base : enables the subsystem 2. UAPI : enables user space api via /dev/rpmbX 3. Sim : RPMB HW simulation device Looks fine to me. This is now merged. If there are comments or changes requested, I'll just stack incremental commits. Bruce Signed-off-by: Tomas Winkler--- features/rpmb/rpmb-base.cfg | 1 + features/rpmb/rpmb-base.scc | 4 features/rpmb/rpmb-sim.cfg | 1 + features/rpmb/rpmb-sim.scc | 6 ++ features/rpmb/rpmb-uapi.cfg | 2 ++ features/rpmb/rpmb-uapi.scc | 6 ++ 6 files changed, 20 insertions(+) create mode 100644 features/rpmb/rpmb-base.cfg create mode 100644 features/rpmb/rpmb-base.scc create mode 100644 features/rpmb/rpmb-sim.cfg create mode 100644 features/rpmb/rpmb-sim.scc create mode 100644 features/rpmb/rpmb-uapi.cfg create mode 100644 features/rpmb/rpmb-uapi.scc diff --git a/features/rpmb/rpmb-base.cfg b/features/rpmb/rpmb-base.cfg new file mode 100644 index ..99e06c3c4d17 --- /dev/null +++ b/features/rpmb/rpmb-base.cfg @@ -0,0 +1 @@ +CONFIG_RPMB=y diff --git a/features/rpmb/rpmb-base.scc b/features/rpmb/rpmb-base.scc new file mode 100644 index ..d4a27715b635 --- /dev/null +++ b/features/rpmb/rpmb-base.scc @@ -0,0 +1,4 @@ +define KFEATURE_DESCRIPTION "Enable Replay Protected Memory Block (RPMB) subsystem" +define KFEATURE_COMPATIBILITY all + +kconf hardware rpmb-base.cfg diff --git a/features/rpmb/rpmb-sim.cfg b/features/rpmb/rpmb-sim.cfg new file mode 100644 index ..784aef008d86 --- /dev/null +++ b/features/rpmb/rpmb-sim.cfg @@ -0,0 +1 @@ +CONFIG_RPMB_SIM=m diff --git a/features/rpmb/rpmb-sim.scc b/features/rpmb/rpmb-sim.scc new file mode 100644 index ..0b9fa28d2066 --- /dev/null +++ b/features/rpmb/rpmb-sim.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION "Enable Replay Protected Memory Block (RPMB) Simulation Device" +define KFEATURE_COMPATIBILITY all + +include features/rpmb/rpmb-base.scc + +kconf hardware rpmb-sim.cfg diff --git a/features/rpmb/rpmb-uapi.cfg b/features/rpmb/rpmb-uapi.cfg new file mode 100644 index ..4206e2396128 --- /dev/null +++ b/features/rpmb/rpmb-uapi.cfg @@ -0,0 +1,2 @@ +CONFIG_RPMB_INTF_DEV=y + diff --git a/features/rpmb/rpmb-uapi.scc b/features/rpmb/rpmb-uapi.scc new file mode 100644 index ..02b68f9bca44 --- /dev/null +++ b/features/rpmb/rpmb-uapi.scc @@ -0,0 +1,6 @@ +define KFEATURE_DESCRIPTION "Enable Replay Protected Memory Block (RPMB) char device" +define KFEATURE_COMPATIBILITY all + +include features/rpmb/rpmb-base.scc + +kconf hardware rpmb-uapi.cfg -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PULL REQUEST] rpmb upstream pending patches
On 2016-07-23 7:31 AM, Winkler, Tomas wrote: Hi Bruce Please pull RPMB patches for BXT. These patches tare waiting in LKML on review. Also here he patches are staged on standard/base but for now you may want to consider margining them to bxt-rebase similar to the mei ones, I put these on standard/intel/base Bruce The following changes since commit ddab242999407fadae68e7ee5381b0ec6679d443: mei: drop wr_msg from the mei_dev structure (2016-07-21 13:05:40 -0400) are available in the git repository at: https://github.com/tomasbw/linux-yocto-4.4.git standard/base-rpmb for you to fetch changes up to 6f4d28d4d1aae3eeefdd169025c0325cf0ba4819: scsi: ufs: connect to RPMB subsystem (2016-07-23 14:22:04 +0300) Tomas Winkler (8): rpmb: add Replay Protected Memory Block (RPMB) subsystem char: rpmb: add sysfs-class ABI documentation char: rpmb: add device attributes char: rpmb: provide a user space interface char: rpmb: add RPMB simulation device tools rpmb: add RPBM access tool mmc: block: register RPMB partition with the RPMB subsystem scsi: ufs: connect to RPMB subsystem Documentation/ABI/testing/sysfs-class-rpmb | 44 + Documentation/ioctl/ioctl-number.txt | 1 + MAINTAINERS| 10 + drivers/char/Kconfig | 2 + drivers/char/Makefile | 1 + drivers/char/rpmb/Kconfig | 25 +++ drivers/char/rpmb/Makefile | 6 + drivers/char/rpmb/cdev.c | 276 ++ drivers/char/rpmb/core.c | 484 + drivers/char/rpmb/rpmb-cdev.h | 25 +++ drivers/char/rpmb/rpmb_sim.c | 668 +++ drivers/mmc/card/Kconfig | 1 + drivers/mmc/card/block.c | 258 +++- drivers/scsi/ufs/Kconfig | 1 + drivers/scsi/ufs/ufshcd.c | 182 + drivers/scsi/ufs/ufshcd.h | 2 + include/linux/rpmb.h | 165 include/uapi/linux/Kbuild | 1 + include/uapi/linux/rpmb.h | 152 +++ tools/Makefile | 14 +- tools/rpmb/.gitignore | 2 + tools/rpmb/Makefile| 33 tools/rpmb/rpmb.c | 948 + 23 files changed, 3293 insertions(+), 8 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-rpmb create mode 100644 drivers/char/rpmb/Kconfig create mode 100644 drivers/char/rpmb/Makefile create mode 100644 drivers/char/rpmb/cdev.c create mode 100644 drivers/char/rpmb/core.c create mode 100644 drivers/char/rpmb/rpmb-cdev.h create mode 100644 drivers/char/rpmb/rpmb_sim.c create mode 100644 include/linux/rpmb.h create mode 100644 include/uapi/linux/rpmb.h create mode 100644 tools/rpmb/.gitignore create mode 100644 tools/rpmb/Makefile create mode 100644 tools/rpmb/rpmb.c -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] linux-yocto: memory leak in krogoth 4.1.28 kernel
On Sun, Jul 24, 2016 at 2:42 PM, Chris Sykes < ch...@newforest-technology.co.uk> wrote: > Hi, > > At the end of last week I hit a known kernel memory leak in the > linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly > results in an OOM kernel panic on my platform (x86, 1G RAM). > > The patch below fixed the problem for me: > http://www.spinics.net/lists/stable/msg138760.html > > It's already queued for 4.1.29, but thought I'd mention it here for the > benefit of the list. Perhaps it might be worth expediting a fix for 2.1? > > There's plenty of other bugs lurking, no real rush to fix something that is already queued for -stable .. that's the best place to pick up a fix. > I also raised bugzilla 10014 - I hope this was the right thing to do... > > Actually, sending a patch is even better. If you've seen the problem, tested a fix, you are by far in the best position to send a patch to fix the issue. Just fire something to the linux-yocto list with the information you've added above, and it'll go into the queue .. most likely before I get to the 4.1.29 stable :) Cheers, Bruce > -- > Chris Sykes > New Forest Technology Ltd. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel bug 109051
On 2016-07-24 6:09 PM, Chris Tapp wrote: I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051. I’m using a J1900 (listed as affected) and the system locks up totally (running a graphics-based application) after an indeterminate period. Using the scripts referenced on the related bug page for comment 437 (https://bugzilla.kernel.org/show_bug.cgi?id=109051#c437) appears to resolve the issue. Is anyone aware of this and/or know if it will be fixed within the Yocto kernel tree? Not unless someone sends a patch. If you have a platform showing the error, and have tested a fix .. why not just send the patch ? Bruce -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Kernel bug 109051
I’m using the meta-intel “valley-island” BSP under “krogoth” and think I may have run into https://bugzilla.kernel.org/show_bug.cgi?id=109051. I’m using a J1900 (listed as affected) and the system locks up totally (running a graphics-based application) after an indeterminate period. Using the scripts referenced on the related bug page for comment 437 (https://bugzilla.kernel.org/show_bug.cgi?id=109051#c437) appears to resolve the issue. Is anyone aware of this and/or know if it will be fixed within the Yocto kernel tree? -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] linux-yocto: memory leak in krogoth 4.1.28 kernel
On Sun, Jul 24, 2016 at 11:42 AM, Chris Sykeswrote: > Hi, > > At the end of last week I hit a known kernel memory leak in the linux-yocto > 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly results in an > OOM kernel panic on my platform (x86, 1G RAM). > > The patch below fixed the problem for me: > http://www.spinics.net/lists/stable/msg138760.html > > It's already queued for 4.1.29, but thought I'd mention it here for the > benefit of the list. Perhaps it might be worth expediting a fix for 2.1? > > I also raised bugzilla 10014 - I hope this was the right thing to do... Thanks for report, you did the right thing. Our Kernel maintainer will take care of it. > > -- > Chris Sykes > New Forest Technology Ltd. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] linux-yocto: memory leak in krogoth 4.1.28 kernel
Hi, At the end of last week I hit a known kernel memory leak in the linux-yocto 4.1 branch, as delivered in 2.1 / krogoth. It rather quickly results in an OOM kernel panic on my platform (x86, 1G RAM). The patch below fixed the problem for me: http://www.spinics.net/lists/stable/msg138760.html It's already queued for 4.1.29, but thought I'd mention it here for the benefit of the list. Perhaps it might be worth expediting a fix for 2.1? I also raised bugzilla 10014 - I hope this was the right thing to do... -- Chris Sykes New Forest Technology Ltd. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help with DISTRO settings
On Sun, Jul 24, 2016 at 12:34 AM, Edward Wingatewrote: > Ah, I found it. I had inadvertently deleted one line > (DISTRO="mydistro") from my layer's conf/layer.conf. > > Am I doing this right though? Do I need DISTRO="mydistro" in both > conf/layer.conf and conf/distro/mydistro.conf? Just conf/distro/mydistro.conf is needed. Removing it from > either doesn't work, but it seems redundant to put it in mydistro.conf > as well. did you make any other changes ? > > > On Sun, Jul 24, 2016 at 12:04 AM, Edward Wingate wrote: >> On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote: >>> Move these DISTRO settings above require conf/distro/poky.conf >> >> That didn't change anything. And it had been working like that for a >> long time now. Just a few days ago, it stopped taking effect and >> reverting back to poky. I have not been able to figure out what >> caused it to stop working. >> >> Thanks for your reply nonetheless. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help with DISTRO settings
Ah, I found it. I had inadvertently deleted one line (DISTRO="mydistro") from my layer's conf/layer.conf. Am I doing this right though? Do I need DISTRO="mydistro" in both conf/layer.conf and conf/distro/mydistro.conf? Removing it from either doesn't work, but it seems redundant to put it in mydistro.conf as well. On Sun, Jul 24, 2016 at 12:04 AM, Edward Wingatewrote: > On Sat, Jul 23, 2016 at 11:05 PM, Khem Raj wrote: >> Move these DISTRO settings above require conf/distro/poky.conf > > That didn't change anything. And it had been working like that for a > long time now. Just a few days ago, it stopped taking effect and > reverting back to poky. I have not been able to figure out what > caused it to stop working. > > Thanks for your reply nonetheless. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help with DISTRO settings
On Sat, Jul 23, 2016 at 11:05 PM, Khem Rajwrote: > Move these DISTRO settings above require conf/distro/poky.conf That didn't change anything. And it had been working like that for a long time now. Just a few days ago, it stopped taking effect and reverting back to poky. I have not been able to figure out what caused it to stop working. Thanks for your reply nonetheless. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help with DISTRO settings
On Sat, Jul 23, 2016 at 10:49 PM, Edward Wingatewrote: > This is in my layer's conf/distro/mydistro.conf file: > > require conf/distro/poky.conf > DISTRO = "mydistro" > DISTRO_NAME = "MyDistro" Move these DISTRO settings above require conf/distro/poky.conf > > These variables took effect before, but now bitbake is reverting back > to DISTRO="poky" and DISTRO_NAME = "Poky (Yocto Project Reference > Distro)" (used for /etc/issue) for some reason. > > How can I determine what is reverting it? I don't know what I might > have changed to make it do this. Thank you. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto