date:20190829

On Tue, Aug 20, 2019 at 07:29:20PM +0800, Kevin Hao wrote:
> This adds the cfg files to support the Marvell OCTEON TX2
> CN96XX multicore arm64 SoC.

Ping...

Thanks,
Kevin

> 
> Signed-off-by: Kevin Hao 
> ---
>  bsp/marvell-cn96xx/marvell-cn96xx-standard.scc |   7 ++
>  bsp/marvell-cn96xx/marvell-cn96xx.cfg  | 104 
> +
>  bsp/marvell-cn96xx/marvell-cn96xx.scc  |   6 ++
>  3 files changed, 117 insertions(+)
>  create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx-standard.scc
>  create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.cfg
>  create mode 100644 bsp/marvell-cn96xx/marvell-cn96xx.scc
> 
> diff --git a/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc 
> b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc
> new file mode 100644
> index ..8d92dc15f87b
> --- /dev/null
> +++ b/bsp/marvell-cn96xx/marvell-cn96xx-standard.scc
> @@ -0,0 +1,7 @@
> +define KMACHINE marvell-cn96xx
> +define KTYPE standard
> +define KARCH arm64
> +
> +include ktypes/standard
> +
> +include marvell-cn96xx.scc
> diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.cfg 
> b/bsp/marvell-cn96xx/marvell-cn96xx.cfg
> new file mode 100644
> index ..6b83cd0659aa
> --- /dev/null
> +++ b/bsp/marvell-cn96xx/marvell-cn96xx.cfg
> @@ -0,0 +1,104 @@
> +..
> +.WARNING
> +.
> +. This file is a kernel configuration fragment, and not a full kernel
> +. configuration file.  The final kernel configuration is made up of
> +. an assembly of processed fragments, each of which is designed to
> +. capture a specific part of the final configuration (e.g. platform
> +. configuration, feature configuration, and board specific hardware
> +. configuration).  For more information on kernel configuration, please
> +. consult the product documentation.
> +.
> +..
> +
> +CONFIG_ARM64=y
> +CONFIG_ARM64_VA_BITS_48=y
> +CONFIG_ARM_SMMU_V3=y
> +CONFIG_NR_CPUS=24
> +CONFIG_ARCH_THUNDER=y
> +
> +# uboot set "coherent_pool=16M" kernel parameter by default, so we need to
> +# make sure CONFIG_FORCE_MAX_ZONEORDER is big enough
> +CONFIG_ARM64_64K_PAGES=y
> +CONFIG_TRANSPARENT_HUGEPAGE=y
> +
> +# PCIe
> +CONFIG_PCI=y
> +CONFIG_PCIEPORTBUS=y
> +CONFIG_HOTPLUG_PCI=y
> +CONFIG_HOTPLUG_PCI_PCIE=y
> +CONFIG_PCI_IOV=y
> +
> +CONFIG_PCI_HOST_GENERIC=y
> +CONFIG_PCI_HOST_THUNDER_PEM=y
> +CONFIG_PCI_HOST_OCTEONTX2_PEM=y
> +
> +# Ethernet
> +CONFIG_OCTEONTX2_AF=y
> +CONFIG_OCTEONTX2_PF=y
> +CONFIG_OCTEONTX2_VF=y
> +CONFIG_USB_USBNET=y
> +CONFIG_USB_NET_AX88179_178A=y
> +
> +# NVMe
> +CONFIG_BLK_DEV_NVME=y
> +
> +# DMA
> +CONFIG_OCTEONTX2_DPI_PF=y
> +
> +# MTD
> +CONFIG_MTD=y
> +CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_M25P80=y
> +CONFIG_MTD_BLOCK=y
> +
> +# USB
> +CONFIG_USB=y
> +CONFIG_USB_XHCI_HCD=y
> +
> +# SPI
> +CONFIG_SPI=y
> +CONFIG_SPI_OCTEONTX2=y
> +
> +# I2C
> +CONFIG_I2C=y
> +CONFIG_I2C_THUNDERX=y
> +
> +# Serial
> +CONFIG_SERIAL_AMBA_PL011=y
> +CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
> +
> +# Watchdog
> +CONFIG_ARM_SBSA_WATCHDOG=y
> +
> +# SD
> +CONFIG_MMC=y
> +CONFIG_MMC_CAVIUM_THUNDERX=y
> +
> +# GPIO
> +CONFIG_GPIOLIB=y
> +CONFIG_GPIO_THUNDERX=y
> +
> +# HWMON
> +CONFIG_SENSORS_MAX6697=y
> +CONFIG_SENSORS_JC42=y
> +
> +# RTC
> +CONFIG_RTC_CLASS=y
> +CONFIG_RTC_DRV_DS1307=y
> +
> +# Regulator
> +CONFIG_REGULATOR=y
> +CONFIG_REGULATOR_FIXED_VOLTAGE=y
> +CONFIG_REGULATOR_GPIO=y
> +
> +# VFIO
> +CONFIG_VFIO=y
> +CONFIG_VFIO_PCI=y
> +
> +# Misc
> +CONFIG_EEPROM_AT24=y
> +CONFIG_HW_RANDOM=y
> +CONFIG_HW_RANDOM_CAVIUM=y
> +CONFIG_OCTEONTX2_RM=y
> +CONFIG_OCTEONTX2_RM_DOM_SYSFS=y
> diff --git a/bsp/marvell-cn96xx/marvell-cn96xx.scc 
> b/bsp/marvell-cn96xx/marvell-cn96xx.scc
> new file mode 100644
> index ..0d104fad583b
> --- /dev/null
> +++ b/bsp/marvell-cn96xx/marvell-cn96xx.scc
> @@ -0,0 +1,6 @@
> +kconf hardware marvell-cn96xx.cfg
> +kconf hardware features/edac/edac.cfg
> +
> +include cfg/usb-mass-storage.scc
> +
> +include features/hugetlb/hugetlb.scc
> -- 
> 2.14.4
> 


signature.asc
Description: PGP signature
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [linux-yocto-dev] Add the support for the Marvell cn96xx SoC

On Tue, Aug 20, 2019 at 07:21:04PM +0800, Kevin Hao wrote:
> Hi Bruce,
> 
> This patch series adds the support for the Marvell cn96xx SoC. The OCTEON TX2
> cn96xx SoC is a scalable architecture that integrates high performance 64-bit
> Armv8.2 processors, a cache-coherent interconnect, hardware accelerators,
> virtualized networking, and scalable I/O. It support the following
> industry-standard I/O interfaces:
>   DDR4 DRAM
>   PCI Express 4.0 version 1.0
>   SGMII
>   QSGMII
>   XAUI
>   XFI
>   CAUI
> 
> Most of the patches are for the Marvell specific drivers. So in theory, it
> should be safe to merge these patches to the standard/base branch. But I
> prefer to stage them to the specific standard/cn96xx branch. The reason is
> that we plan to support other Marvell SoCs, and the SDK for them may be
> based on different SDK versions. They will definitely touch some common
> files affect by this patch series. So it would be a nightmare for us to
> support them if these patches are merged to the standard/base branch.

Ping...

Thanks,
Kevin

> 
> The following changes since commit ce4ec6ff9589e3b1dcc4e3a0b192b02823631c3e:
> 
>   Merge tag 'v5.3-rc5' into standard/base (2019-08-18 22:40:47 -0400)
> 
> are available in the Git repository at:
> 
>   git://github.com/haokexin/linux standard/cn96xx
> 
> for you to fetch changes up to 4fae437f7ea88d2aab10cac684e11d94b12114bd:
> 
>   octeontx2-af: Fix the using of variable length arrays (2019-08-20 11:25:36 
> +0800)
> 
> 
> Aleksey Makarov (6):
>   octeontx2-pf: Set irq affinity hints for CQ interrupts
>   octeontx2-pf: Implement ndo_tx_timeout callback
>   octeontx2-pf: Support queue interrupts
>   octeontx2-pf: Add reset count to stats
>   octeontx2-af: Add low level support for Marvell PTP coprocessor
>   octeontx2-pf: Add support for PTP clock
> 
> Angela Czubak (2):
>   octeontx2-af: fix rvu_sso_ggrp_taq_flush
>   octeontx2-af: fix cgx_lmac_rx_tx_enable
> 
> Chandrakala Chavva (1):
>   mmc: cavium_thunderx: Use proper register to clear interrupts
> 
> Christina Jacob (21):
>   octeontx2-pf: BQL support.
>   octeontx2-pf: IRQ coalescing config and tuning via ethtool
>   octeontx2-af: Dump current resource provisioning status
>   octeontx2-pf: Adding ethtool support for link status information.
>   octeontx2-af: Patch to prevent redundant message from pf to af.
>   octeontx2-pf: Fix redundant message from AF to PF
>   octeontx2-af: Support to get link info like current speed, fec etc
>   octeontx2-pf: Ethtool support for fec configuration
>   octeontx2-pf: Fix smmuv3 messages while deferring pf driver probe.
>   octeontx2-af: Move to rvu_fwdata version 1.
>   octeontx2-pf: Add ethtool -m option support.
>   octeontx2-af: Extend fwdata structure with additional information.
>   octeontx2-af: Update fwadata structure with few more reserved fields.
>   octeontx2-af: Fetch FEC stats of the physical link
>   octeontx2-pf: Support to display fec counters also in ethtool stats.
>   octeontx2-af: sync ATF and Kernel firmware data structure.
>   octeontx2-pf: Support to display current settings of a vf network 
> interface via ethtool
>   net:thunderx: fix memory leak in nicvf driver.
>   soc: octeontx2: Add mdio command interface using debugfs
>   octeontx2-af: Introduce SET_LINK_MODE command to change various 
> configurations of a network interface.
>   octeontx2-pf: support to change link speed and autoneg
> 
> Felix Manlunas (2):
>   octeontx2-af: Add new CGX_CMDs to set and get PHY modulation type
>   octeontx2-pf: Add ethtool priv flag to control PAM4 on/off
> 
> Geetha sowjanya (26):
>   octeontx2-af: Sync hw mbox with bounce buffer.
>   octeontx2-pf: Add mailbox bounce buffer
>   octeontx2-pf: Add interface stats to ndo_get_stats64
>   octeontx2-af: Config receive and transmission of pause frames
>   octeontx2-af: Add mbox message to enable/disable pause frames.
>   octeontx2-af: Add mbox messages to configure backpressure for an 
> interface.
>   octeontx2-pf: Add ethtool support to enable/disable pause frames
>   octeontx2-pf: Configure RED drop levels for packet reception.
>   octeontx2-pf: Configure backpressure level for packet reception
>   octeontx2-pf: Skip CQ_STATUS read if pending CQEs greater than budget
>   octeontx2-pf: Set RVU PF/VF watchdog timeout
>   octeontx2-af: Check SQ counters to detect the deadlock
>   octeontx2-af: Enable pci bus mastering
>   octeontx2-af: Fix rvu probe on cgx disable
>   octeontx2-pf: Add VF function level reset (FLR) support
>   octeontx2-vf: Configure backpressure level for packet reception
>   octeontx2-af: Support configurable NDC cache way_mask
>   octeontx2: Fix mbox driver compilation dependency.
>   octeontx2-pf: Set

Re: [linux-yocto] [kernel-meta v5.2 0/2] Fix the kernel_configcheck warnings for the v5.2 kernel

Thanks Kevin,

I now have these merged and they'll be part of my next 5.2 recipe revision.

Bruce

On Thu, Aug 29, 2019 at 4:30 AM Kevin Hao  wrote:
>
> These two patches fix the kernel_configcheck warnings when building the
> v5.2 kernel.
>
> Kevin Hao (2):
>   fsl-mpc8315e-rdb/beaglebone: Replace CONFIG_MTD_NAND with
> CONFIG_MTD_RAW_NAND
>   beaglebone: Drop the stale kernel options
>
>  bsp/beaglebone/beaglebone.cfg | 4 +---
>  bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 2 +-
>  2 files changed, 2 insertions(+), 4 deletions(-)
>
> --
> 2.14.4
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [kernel-cache master] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx

merged

Bruce

On Thu, Aug 29, 2019 at 3:08 AM Xulin Sun  wrote:
>
> This adds the cfg & scc files to support the LS2088A-RDB.
>
> Signed-off-by: Xulin Sun 
> ---
>  bsp/nxp-ls20xx/nxp-ls20xx-standard.scc |   8 ++
>  bsp/nxp-ls20xx/nxp-ls20xx.cfg  | 162 +
>  bsp/nxp-ls20xx/nxp-ls20xx.scc  |   7 ++
>  3 files changed, 177 insertions(+)
>  create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
>  create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.cfg
>  create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.scc
>
> diff --git a/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc 
> b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
> new file mode 100755
> index ..e0d9b2b7
> --- /dev/null
> +++ b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
> @@ -0,0 +1,8 @@
> +define KMACHINE nxp-ls20xx
> +define KTYPE standard
> +define KARCH arm64
> +
> +include ktypes/standard/standard.scc
> +branch nxp-ls20xx
> +
> +include nxp-ls20xx.scc
> diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.cfg b/bsp/nxp-ls20xx/nxp-ls20xx.cfg
> new file mode 100755
> index ..f554c916
> --- /dev/null
> +++ b/bsp/nxp-ls20xx/nxp-ls20xx.cfg
> @@ -0,0 +1,162 @@
> +..
> +.WARNING
> +.
> +. This file is a kernel configuration fragment, and not a full kernel
> +. configuration file.  The final kernel configuration is made up of
> +. an assembly of processed fragments, each of which is designed to
> +. capture a specific part of the final configuration (e.g. platform
> +. configuration, feature configuration, and board specific hardware
> +. configuration).  For more information on kernel configuration, please
> +. consult the product documentation.
> +.
> +..
> +
> +CONFIG_ARM64=y
> +CONFIG_ARM64_VA_BITS_48=y
> +CONFIG_ARCH_LAYERSCAPE=y
> +CONFIG_SCHED_MC=y
> +CONFIG_ARM_SMMU=y
> +CONFIG_ARM_SMMU_V3=y
> +
> +CONFIG_PCI=y
> +CONFIG_PCI_LAYERSCAPE=y
> +CONFIG_PCI_HOST_GENERIC=y
> +CONFIG_PCI_XGENE=y
> +CONFIG_PCI_MSI=y
> +
> +CONFIG_CPU_FREQ=y
> +CONFIG_CPU_FREQ_STAT=y
> +CONFIG_CPU_FREQ_GOV_POWERSAVE=y
> +CONFIG_CPU_FREQ_GOV_USERSPACE=y
> +CONFIG_CPU_FREQ_GOV_ONDEMAND=y
> +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
> +CONFIG_CPUFREQ_DT=y
> +CONFIG_QORIQ_CPUFREQ=y
> +
> +CONFIG_MTD=y
> +CONFIG_MTD_CMDLINE_PARTS=y
> +CONFIG_MTD_BLOCK=y
> +CONFIG_MTD_CFI=y
> +CONFIG_MTD_CFI_ADV_OPTIONS=y
> +CONFIG_MTD_CFI_INTELEXT=y
> +CONFIG_MTD_CFI_AMDSTD=y
> +CONFIG_MTD_CFI_STAA=y
> +CONFIG_MTD_DATAFLASH=y
> +CONFIG_MTD_M25P80=y
> +CONFIG_MTD_SST25L=y
> +CONFIG_MTD_SPI_NOR=y
> +CONFIG_MTD_RAW_NAND=y
> +CONFIG_MTD_NAND_FSL_IFC=y
> +CONFIG_SPI_FSL_QUADSPI=y
> +CONFIG_SCSI_SAS_ATA=y
> +CONFIG_SCSI_HISI_SAS=y
> +CONFIG_ATA=y
> +CONFIG_SATA_AHCI=y
> +CONFIG_SATA_AHCI_PLATFORM=y
> +CONFIG_AHCI_CEVA=y
> +CONFIG_AHCI_XGENE=y
> +CONFIG_AHCI_QORIQ=y
> +CONFIG_SATA_SIL24=y
> +
> +CONFIG_FSL_XGMAC_MDIO=y
> +CONFIG_HNS_DSAF=y
> +CONFIG_HNS_ENET=y
> +CONFIG_E1000=y
> +CONFIG_E1000E=y
> +
> +CONFIG_SERIAL_8250=y
> +CONFIG_SERIAL_8250_CONSOLE=y
> +CONFIG_SERIAL_8250_DW=y
> +CONFIG_SERIAL_OF_PLATFORM=y
> +CONFIG_SERIAL_FSL_LPUART=y
> +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
> +
> +CONFIG_SPI=y
> +CONFIG_SPI_FSL_DSPI=y
> +CONFIG_SPI_PL022=y
> +CONFIG_SPI_NXP_FLEXSPI=y
> +
> +CONFIG_POWER_RESET_XGENE=y
> +CONFIG_POWER_RESET_SYSCON=y
> +CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
> +
> +CONFIG_THERMAL=y
> +CONFIG_THERMAL_OF=y
> +CONFIG_CPU_THERMAL=y
> +CONFIG_THERMAL_EMULATION=y
> +CONFIG_WATCHDOG=y
> +CONFIG_ARM_SP805_WATCHDOG=y
> +
> +CONFIG_USB=y
> +CONFIG_USB_OTG=y
> +CONFIG_USB_XHCI_HCD=y
> +CONFIG_USB_STORAGE=y
> +CONFIG_USB_DWC3=y
> +CONFIG_USB_DWC2=y
> +CONFIG_USB_GADGET=y
> +
> +CONFIG_MMC=y
> +CONFIG_MMC_ARMMMCI=y
> +CONFIG_MMC_SDHCI=y
> +CONFIG_MMC_SDHCI_PLTFM=y
> +CONFIG_MMC_SDHCI_OF_ARASAN=y
> +CONFIG_MMC_SDHCI_OF_ESDHC=y
> +CONFIG_MMC_SDHCI_CADENCE=y
> +CONFIG_MMC_SPI=y
> +CONFIG_MMC_DW=y
> +
> +CONFIG_GPIOLIB=y
> +CONFIG_OF_GPIO=y
> +
> +CONFIG_MDIO_DEVICE=y
> +CONFIG_MDIO_BITBANG=y
> +CONFIG_PHYLIB=y
> +CONFIG_AQUANTIA_PHY=y
> +CONFIG_CORTINA_PHY=y
> +
> +#
> +# I2C support
> +#
> +CONFIG_I2C=y
> +CONFIG_I2C_MUX=y
> +CONFIG_I2C_IMX=y
> +CONFIG_I2C_MUX_PCA954x=y
> +
> +CONFIG_RTC_CLASS=y
> +CONFIG_RTC_DRV_DS3232=y
> +CONFIG_RTC_DRV_PL031=y
> +CONFIG_RTC_DRV_PCF2127=y
> +
> +CONFIG_DMADEVICES=y
> +CONFIG_FSL_EDMA=y
> +CONFIG_CMA=y
> +CONFIG_DMA_CMA=y
> +
> +CONFIG_VFIO=y
> +CONFIG_VFIO_PCI=y
> +
> +CONFIG_STAGING=y
> +CONFIG_FSL_MC_BUS=y
> +CONFIG_FSL_MC_DPIO=y
> +
> +CONFIG_CLK_QORIQ=y
> +
> +CONFIG_PHY_XGENE=y
> +
> +CONFIG_CRYPTO_DEV_FSL_CAAM=y
> +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y
> +CONFIG_ARM64_CRYPTO=y
> +CONFIG_CRYPTO_SHA1_ARM64_CE=y
> +CONFIG_CRYPTO_SHA2_ARM64_CE=y
> +CONFIG_CRYPTO_GHASH_ARM64_CE=y
> +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
> +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
> +# CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT is not set
> +
> +# EDAC
> +CONFIG_EDAC_LAYERSCAPE=y
> +
> +CONFIG_SENSORS_LM90=y
>

Re: [linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: add some patches to improve features on renesas-rcar platform

all three are now merged to linux-yocto-dev.

Bruce

On Thu, Aug 29, 2019 at 2:31 AM  wrote:
>
> From: Limeng 
>
> Hi Bruce,
>
> I am working on BSP renesas-rcar platform, and intend to merge this BSP 
> supporting into yocto community.
> Below 3 patches are used to improve gpio, CAN BUS, audio and PCIe features
>
> 0001-arch-arm64-dts-Set-gpio5-pin9-as-input-by-default.patch
> 0002-driver-net-can-disable-clock-when-it-is-in-enable-st.patch
> 0003-pci-pcie-rcar-add-regulators-support.patch
>
> Could you please merge the 3 patches into linux-yocto-dev, branch is 
> standard/base?
>
>  arch/arm64/boot/dts/renesas/ulcb-kf.dtsi |   56 +++
>  drivers/net/can/rcar/rcar_can.c  |5 +-
>  drivers/pci/controller/pcie-rcar.c   |   64 
> +++
>  3 files changed, 124 insertions(+), 1 deletion(-)
>
>
> thanks,
> Limeng



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH] renesas-rcar: enable PCM3168A-I2C codec drvier

merged to master.

Bruce

On Tue, Aug 27, 2019 at 4:59 AM  wrote:
>
> From: Limeng 
>
> On KingFisher board, there is PCM3168A codec chip, so enable
> PCM3168A-I2C codec driver by setting configure
> CONFIG_SND_SOC_PCM3168A_I2C
>
> Signed-off-by: Meng Li 
> ---
>  bsp/renesas-rcar/renesas-rcar.cfg | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/bsp/renesas-rcar/renesas-rcar.cfg 
> b/bsp/renesas-rcar/renesas-rcar.cfg
> index 102441ab..cc896276 100644
> --- a/bsp/renesas-rcar/renesas-rcar.cfg
> +++ b/bsp/renesas-rcar/renesas-rcar.cfg
> @@ -96,6 +96,7 @@ CONFIG_SND_SOC_AK4613=y
>  CONFIG_SND_SOC_HDMI_CODEC=y
>  CONFIG_SND_SIMPLE_CARD=y
>  CONFIG_SND_AUDIO_GRAPH_CARD=y
> +CONFIG_SND_SOC_PCM3168A_I2C=y
>
>  # Clock configuration
>  CONFIG_COMMON_CLK=y
> --
> 2.17.1
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH] aufs: for v5.3-rc3, update UAPI SPDX

merged

Bruce

On Thu, Aug 29, 2019 at 9:52 AM  wrote:
>
> From: "J. R. Okajima" 
>
> Simply follows the commit in mainline,
> 622445541b75 2019-07-29 kbuild: detect missing "WITH
> Linux-syscall-note" for uapi headers
>
> Signed-off-by: J. R. Okajima 
>
> Backport from git://github.com/sfjro/aufs5-linux.git
> 90ff497cebbb ("aufs: for v5.3-rc3, update UAPI SPDX")
> to fix,
> error: kernel-source/include/uapi/linux/aufs_type.h: missing "WITH 
> Linux-syscall-note" for SPDX-License-Identifier
>
> Signed-off-by: He Zhe 
> ---
> This is for linux-yocto-dev all branches.
>
>  include/uapi/linux/aufs_type.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/aufs_type.h b/include/uapi/linux/aufs_type.h
> index 0e3e2b1..59f050c 100644
> --- a/include/uapi/linux/aufs_type.h
> +++ b/include/uapi/linux/aufs_type.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL-2.0 */
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
>  /*
>   * Copyright (C) 2005-2019 Junjiro R. Okajima
>   *
> --
> 2.7.4
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] [meta-raspberrypi] Error trying to generate Raspberry Pi initramfs

2019-08-29 Thread Zoran Stojsavljevic

Hello Greg,

This, what I have posted as answer work for me on BBB (BeagleBone
Black) seamlessly.

I did not try it on Sabre Automotive, but as we speak, I just
straightened out the optimal local.conf for it (with very rich
networking services on the top of Linux), and I am 100% sure the above
initramfs methodology will work on Sabre Automotive as well.

I have no idea about specifics on RPI 3. Sorry for that.

Best Regads,
Zoran
___

On Thu, Aug 29, 2019 at 7:40 PM Greg Wilson-Lindberg
 wrote:
>
> Hi Zoran,
> Thanks for your comments.
>
> I'm adding [meta-raspberrypi] to the as I have realized that some might have 
> missed this Raspberry-pi specific question.
>
> Thanks,
> Greg Wilson-Lindberg
>
> > -Original Message-
> > From: Zoran Stojsavljevic [mailto:zoran.stojsavlje...@gmail.com]
> > Sent: Wednesday, August 28, 2019 05:08 PM
> > To: Greg Wilson-Lindberg 
> > Cc: Yocto list discussion 
> > Subject: Re: [yocto] Error trying to generate Raspberry Pi initramfs
> >
> > Three things:
> > [1] The initramfs is NOT the initrd (te second one is the temp
> >   stage in booting the linux to mmcblk...); [2] There are some config 
> > parameters
> > you need to set up in
> >   your kernel .config file:
> >   
> > https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/custom/config-
> > initramfs
> > [3] The command line is formed in u-boot or in grub2, or in
> >   your Linux boot loader (you need to add some lines
> >   in ash u-boot config script, as the following example):
> >   
> > https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/custom/u-boot.ash
> >
> > Good Luck,
> > Zoran
> > ___
> >
> >
> > On Wed, Aug 28, 2019 at 7:26 PM Greg Wilson-Lindberg
> >  wrote:
> > >
> > > I'm trying to generate an initramfs for a raspberry pi 3 for a sumo 
> > > build. We are
> > based off of the Qt boot2qt system.
> > >
> > > I have followed the instructions in the meta-raspberrypi.pdf 
> > > documentation,
> > section 3.14 Image with Initramfs.
> > >
> > > I edited the meta-raspberrypi/recipes-kernel/linux/linux-raspberry.inc 
> > > file and
> > added the variables into my local.conf file. I created a 
> > rpi-minimal-initramfs.bb
> > recipe and it is created when I build the system. But the command line that 
> > is put
> > into the boot partition is:
> > >
> > > dwc_otg.lpm_enable=0  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
> > fbcon=map:10 fbcon=font:VGA8x8
> > >
> > > No initramfs.
> > >
> > > In the linux-raspberry.inc file, after the insertion point for the new 
> > > kernel variables,
> > there is a test for KERNEL_INITRAMFS. I tried setting this in my local.conf 
> > file, but
> > when I do I get an error for a missing file:
> > >
> > > | /home//tmp/deploy/images/raspberrypi3/uImage1-raspberrypi3.bin:
> > > | No such file or directory
> > >
> > > So, apparently that can't be set directly.
> > >
> > > There seems to be something missing in the instructions in the meta-
> > raspberrypi.pdf documentation. Anyone that has any experience with setting 
> > this up
> > and can help me figure out what I'm missing, I would greatly appreciate the 
> > help.
> > >
> > > Regards,
> > > Greg Wilson-Lindberg
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > ___
> > > 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] Yocto Project Summit 2019 - CFP Open

2019-08-29 Thread Volosincu, Andreea S

Yocto Project is pleased to announce the Yocto Project Summit 2019, a technical 
conference for engineers, open source technologists, students and academia in 
the OSS space.

Organized in conjunction with ELCE 2019, this 2-day event is where individuals 
will learn about Yocto Projects' direction - including, but not limited to, new 
releases, development tools, features - get training on the next wave of 
embedded Linux technologies (segment previously known as Yocto Project 
Developer Day), and network with their industry peers, Yocto Project 
maintainers and experts.

DATE: Thursday, October 31 - Friday, November 1, 2019
TIME: 9:00 am - 5:00 pm
LOCATION: Lyon Convention Center
REGISTRATION: Together with your ELCE 
registration
EVENT PAGE: https://www.yoctoproject.org/yocto-project-summit-2019-2/

The CFP is currently open.
CFP Closes: 11:59 PM PST on Monday, September 16
CFP Notifications: Monday, September 23
Schedule Announcement: Thursday, September 30
Slide Due Date: Monday, October 21

CFP list of topics:

?  DevTool

?  Layer quality: e.g. creating robust layers, safely using existing layers

?  Future languages (e.g. Rust)

?  Productivity tricks and tools

?  Security

?  Reproducibility

?  Init systems: pros and cons, selection, configuration

?  Leveraging the new runqueue optimizations for mirrors, reproducible builds

?  Supporting the Application Developer

?  DevOps

?  Working with/creating BSPs

?  Practical use of the Yocto Project

Submit your proposals at 
conferen...@yoctoproject.org

Best regards,
Yocto Project Advocacy Team


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] python-scapy: drop py2 package

2019-08-29 Thread Armin Kuster

fixup run-ptest

Signed-off-by: Armin Kuster 
---
 recipes-security/scapy/files/run-ptest|  2 +-
 recipes-security/scapy/python-scapy.inc   | 22 ---
 recipes-security/scapy/python-scapy_2.4.3.bb  | 11 
 recipes-security/scapy/python3-scapy_2.4.3.bb | 27 ---
 4 files changed, 25 insertions(+), 37 deletions(-)
 delete mode 100644 recipes-security/scapy/python-scapy.inc
 delete mode 100644 recipes-security/scapy/python-scapy_2.4.3.bb

diff --git a/recipes-security/scapy/files/run-ptest 
b/recipes-security/scapy/files/run-ptest
index 91b29f9..797d8ec 100644
--- a/recipes-security/scapy/files/run-ptest
+++ b/recipes-security/scapy/files/run-ptest
@@ -1,4 +1,4 @@
 #!/bin/sh
-UTscapy -t regression.uts -f text -l -C \
+UTscapy3 -t regression.uts -f text -l -C \
 -o @PTEST_PATH@/scapy_ptest_$(date +%Y%m%d-%H%M%S).log \
 2>&1 | sed -e 's/^passed None/PASS:/' -e 's/^failed None/FAIL:/'
diff --git a/recipes-security/scapy/python-scapy.inc 
b/recipes-security/scapy/python-scapy.inc
deleted file mode 100644
index 28e13f2..000
--- a/recipes-security/scapy/python-scapy.inc
+++ /dev/null
@@ -1,22 +0,0 @@
-SUMMARY = "Network scanning and manipulation tool"
-DESCRIPTION = "Scapy is a powerful interactive packet manipulation program. It 
is able to forge or decode packets of a wide number of protocols, send them on 
the wire, capture them, match requests and replies, and much more. It can 
easily handle most classical tasks like scanning, tracerouting, probing, unit 
tests, attacks or network discovery (it can replace hping, 85% of nmap, 
arpspoof, arp-sk, arping, tcpdump, tethereal, p0f, etc.). It also performs very 
well at a lot of other specific tasks that most other tools can't handle, like 
sending invalid frames, injecting your own 802.11 frames, combining technics 
(VLAN hopping+ARP cache poisoning, VOIP decoding on WEP encrypted channel, 
...), etc."
-SECTION = "security"
-LICENSE = "GPLv2"
-
-LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
-
-S = "${WORKDIR}/git"
-
-SRCREV = "3047580162a9407ef05fe981983cacfa698f1159"
-SRC_URI = "git://github.com/secdev/scapy.git"
-
-inherit ptest
-
-do_install_ptest() {
-install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
-sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
-}
-
-RDEPENDS_${PN} = "tcpdump ${PYTHON_PN}-compression ${PYTHON_PN}-cryptography 
${PYTHON_PN}-netclient  \
-  ${PYTHON_PN}-netserver ${PYTHON_PN}-pydoc 
${PYTHON_PN}-pkgutil ${PYTHON_PN}-shell \
-  ${PYTHON_PN}-threading ${PYTHON_PN}-numbers 
${PYTHON_PN}-pycrypto"
diff --git a/recipes-security/scapy/python-scapy_2.4.3.bb 
b/recipes-security/scapy/python-scapy_2.4.3.bb
deleted file mode 100644
index 982620e..000
--- a/recipes-security/scapy/python-scapy_2.4.3.bb
+++ /dev/null
@@ -1,11 +0,0 @@
-inherit setuptools
-require python-scapy.inc
-
-SRC_URI += "file://run-ptest"
-
-RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
-
-do_install_append() {
-mv ${D}${bindir}/scapy ${D}${bindir}/scapy2
-mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy2
-}
diff --git a/recipes-security/scapy/python3-scapy_2.4.3.bb 
b/recipes-security/scapy/python3-scapy_2.4.3.bb
index abcaeeb..925f188 100644
--- a/recipes-security/scapy/python3-scapy_2.4.3.bb
+++ b/recipes-security/scapy/python3-scapy_2.4.3.bb
@@ -1,9 +1,30 @@
-inherit setuptools3
-require python-scapy.inc
+SUMMARY = "Network scanning and manipulation tool"
+DESCRIPTION = "Scapy is a powerful interactive packet manipulation program. It 
is able to forge or decode packets of a wide number of protocols, send them on 
the wire, capture them, match requests and replies, and much more. It can 
easily handle most classical tasks like scanning, tracerouting, probing, unit 
tests, attacks or network discovery (it can replace hping, 85% of nmap, 
arpspoof, arp-sk, arping, tcpdump, tethereal, p0f, etc.). It also performs very 
well at a lot of other specific tasks that most other tools can't handle, like 
sending invalid frames, injecting your own 802.11 frames, combining technics 
(VLAN hopping+ARP cache poisoning, VOIP decoding on WEP encrypted channel, 
...), etc."
+SECTION = "security"
+LICENSE = "GPLv2"
 
-SRC_URI += "file://run-ptest"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
+
+S = "${WORKDIR}/git"
+
+SRCREV = "3047580162a9407ef05fe981983cacfa698f1159"
+SRC_URI = "git://github.com/secdev/scapy.git \
+   file://run-ptest"
+
+S = "${WORKDIR}/git"
+
+inherit setuptools3 ptest
 
 do_install_append() {
 mv ${D}${bindir}/scapy ${D}${bindir}/scapy3
 mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy3
 }
+
+do_install_ptest() {
+install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
+sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
+}
+
+RDEPENDS_${PN} = "tcpdump ${PYTHON_PN}-compression ${PYTHON_PN}-cryptography 
${PYTHON_PN}-netclient  \
+

Re: [yocto] [meta-selinux][PATCH 3/3] util-linux: drop obsolete patch

2019-08-29 Thread Joe MacDonald

[Re: [yocto] [meta-selinux][PATCH 3/3] util-linux: drop obsolete patch] On 
19.08.29 (Thu 16:00) Yi Zhao wrote:

> Hi Joe,
> 
> 
> Seems you were missing this patch. Would you please merge it? Thanks.

Oh, yeah, sure.  It got classified as spam.  Since it was the end of a
queue I just assumed they were mis-numbered when I only found 1/3 and
2/3.

Thanks for pinging me on it.

-J.

> 
> 
> //Yi
> 
> 
> On 5/20/19 12:41 PM, Yi Zhao wrote:
> > Signed-off-by: Yi Zhao 
> > ---
> >   .../util-linux/fix-libmount_la_DEPENDENCIES.patch  | 28 
> > --
> >   1 file changed, 28 deletions(-)
> >   delete mode 100644 
> > recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch
> > 
> > diff --git 
> > a/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch 
> > b/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch
> > deleted file mode 100644
> > index ab54818..000
> > --- a/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch
> > +++ /dev/null
> > @@ -1,28 +0,0 @@
> > -Subject: [PATCH] util-linux: fix libmount_la_DEPENDENCIES.
> > -
> > -Upstream-Status: Pending
> > -
> > -libmount_la_LIBADD contains "-lselinux", this is not a object that
> > -could consider as a dependency target. So fix this.
> > -
> > -Signed-off-by: Xin Ouyang 
> > 
> > - libmount/src/Makemodule.am |2 +-
> > - 1 files changed, 1 insertions(+), 1 deletions(-)
> > -
> > -diff --git a/libmount/src/Makemodule.am b/libmount/src/Makemodule.am
> > -index 494e02a..bf494a4 100644
> >  a/libmount/src/Makemodule.am
> > -+++ b/libmount/src/Makemodule.am
> > -@@ -38,7 +38,7 @@ libmount_la_CFLAGS = \
> > -   -I$(top_srcdir)/libmount/src
> > -
> > - libmount_la_DEPENDENCIES = \
> > --  $(libmount_la_LIBADD) \
> > -+  libcommon.la libblkid.la \
> > -   libmount/src/libmount.sym \
> > -   libmount/src/libmount.h.in
> > -
> > ---
> > -1.7.5.4
> > -

-- 
-Joe MacDonald.
Linux Architect | Mentor® A Siemens Business
:wq


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Error trying to generate Raspberry Pi initramfs

2019-08-29 Thread Greg Wilson-Lindberg

Hi Zoran,
Thanks for your comments. 

I'm adding [meta-raspberrypi] to the as I have realized that some might have 
missed this Raspberry-pi specific question.

Thanks,
Greg Wilson-Lindberg  
 
> -Original Message-
> From: Zoran Stojsavljevic [mailto:zoran.stojsavlje...@gmail.com]
> Sent: Wednesday, August 28, 2019 05:08 PM
> To: Greg Wilson-Lindberg 
> Cc: Yocto list discussion 
> Subject: Re: [yocto] Error trying to generate Raspberry Pi initramfs
> 
> Three things:
> [1] The initramfs is NOT the initrd (te second one is the temp
>   stage in booting the linux to mmcblk...); [2] There are some config 
> parameters
> you need to set up in
>   your kernel .config file:
>   
> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/custom/config-
> initramfs
> [3] The command line is formed in u-boot or in grub2, or in
>   your Linux boot loader (you need to add some lines
>   in ash u-boot config script, as the following example):
>   
> https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/custom/u-boot.ash
> 
> Good Luck,
> Zoran
> ___
> 
> 
> On Wed, Aug 28, 2019 at 7:26 PM Greg Wilson-Lindberg
>  wrote:
> >
> > I'm trying to generate an initramfs for a raspberry pi 3 for a sumo build. 
> > We are
> based off of the Qt boot2qt system.
> >
> > I have followed the instructions in the meta-raspberrypi.pdf documentation,
> section 3.14 Image with Initramfs.
> >
> > I edited the meta-raspberrypi/recipes-kernel/linux/linux-raspberry.inc file 
> > and
> added the variables into my local.conf file. I created a 
> rpi-minimal-initramfs.bb
> recipe and it is created when I build the system. But the command line that 
> is put
> into the boot partition is:
> >
> > dwc_otg.lpm_enable=0  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
> fbcon=map:10 fbcon=font:VGA8x8
> >
> > No initramfs.
> >
> > In the linux-raspberry.inc file, after the insertion point for the new 
> > kernel variables,
> there is a test for KERNEL_INITRAMFS. I tried setting this in my local.conf 
> file, but
> when I do I get an error for a missing file:
> >
> > | /home//tmp/deploy/images/raspberrypi3/uImage1-raspberrypi3.bin:
> > | No such file or directory
> >
> > So, apparently that can't be set directly.
> >
> > There seems to be something missing in the instructions in the meta-
> raspberrypi.pdf documentation. Anyone that has any experience with setting 
> this up
> and can help me figure out what I'm missing, I would greatly appreciate the 
> help.
> >
> > Regards,
> > Greg Wilson-Lindberg
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux] [PATCH] python-scapy: upgrade 2.4.2 -> 2.4.3

2019-08-29 Thread akuster808



On 8/29/19 7:25 AM, Joe MacDonald wrote:
> [Re: [yocto] [meta-selinux] [PATCH] python-scapy: upgrade 2.4.2 -> 2.4.3] On 
> 19.08.29 (Thu 07:14) akuster808 wrote:
>
No v2 required. does not affect patchwork.

- armin
>>
>> On 8/28/19 10:41 PM, Yuan Chao wrote:
>>> License file changed from bin/scapy to LICENSE
>> Is this the correct layer?
> There's no scapy in meta-selinux, AFAIK.  So proably this was destined
> for meta-security instead.
>
> -J.
>
>> -armin
>>> Signed-off-by: Yuan Chao 
>>> ---
>>>  recipes-security/scapy/python-scapy.inc   | 4 ++--
>>>  .../scapy/{python-scapy_2.4.2.bb => python-scapy_2.4.3.bb}| 0
>>>  .../scapy/{python3-scapy_2.4.2.bb => python3-scapy_2.4.3.bb}  | 0
>>>  3 files changed, 2 insertions(+), 2 deletions(-)
>>>  rename recipes-security/scapy/{python-scapy_2.4.2.bb => 
>>> python-scapy_2.4.3.bb} (100%)
>>>  rename recipes-security/scapy/{python3-scapy_2.4.2.bb => 
>>> python3-scapy_2.4.3.bb} (100%)
>>>
>>> diff --git a/recipes-security/scapy/python-scapy.inc 
>>> b/recipes-security/scapy/python-scapy.inc
>>> index baa69b2..28e13f2 100644
>>> --- a/recipes-security/scapy/python-scapy.inc
>>> +++ b/recipes-security/scapy/python-scapy.inc
>>> @@ -3,11 +3,11 @@ DESCRIPTION = "Scapy is a powerful interactive packet 
>>> manipulation program. It i
>>>  SECTION = "security"
>>>  LICENSE = "GPLv2"
>>>  
>>> -LIC_FILES_CHKSUM = 
>>> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
>>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>>>  
>>>  S = "${WORKDIR}/git"
>>>  
>>> -SRCREV = "bad14cb1a5aee29f8107fbe8ad008d4645f14da7"
>>> +SRCREV = "3047580162a9407ef05fe981983cacfa698f1159"
>>>  SRC_URI = "git://github.com/secdev/scapy.git"
>>>  
>>>  inherit ptest
>>> diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
>>> b/recipes-security/scapy/python-scapy_2.4.3.bb
>>> similarity index 100%
>>> rename from recipes-security/scapy/python-scapy_2.4.2.bb
>>> rename to recipes-security/scapy/python-scapy_2.4.3.bb
>>> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
>>> b/recipes-security/scapy/python3-scapy_2.4.3.bb
>>> similarity index 100%
>>> rename from recipes-security/scapy/python3-scapy_2.4.2.bb
>>> rename to recipes-security/scapy/python3-scapy_2.4.3.bb
>> -- 
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto




signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [help] Multiconfig - Depending on Recipe multiple times

2019-08-29 Thread Mark Hatle

On 8/29/19 10:05 AM, Johannes Wiesböck wrote:
> Hello Everyone,
> 
> i am using Yocto on the thud branch to build images for a real-time

This is not implemented in thud.  Thud had multiconfig supported, but didn't yet
allow for dependencies between configurations.

Master has support for multiconfig dependencies as well, but I'm not sure how
well tested they are.

--Mark

> operating system based on FreeRTOS. I would like to run multiple images
> on different CPU cores in an asynchronous multi-processing (AMP) 
> configuration.
> Each image will contain the software for only one single core. For
> deployment, i would like to pack all images into one package.
> 
> Therefore, i would like to use multiconfig to build the same recipe four
> times for the same hardware but with different compiler options,
> determined by to core the image should run on. These builds are all based on
> the same source code but differ in compiler options used for building. After
> the images for all configurations are built, i would like to pack all images
> into a single package for deployment.
> 
> I have created two recipes, one called amp-image, that should be built
> once for every multiconfig. A second recipe called master-image,
> depends on amp-image for every configuration, i.e. i have the line
> 
> do_compile[mcdepends] = "multiconfig:amp-c0:amp-c0:amp-image:do_build 
> multiconfig:amp-c0:amp-c1:amp-image:do_build"
> 
> in my master-image.bb file. I also have set up my multiconfigs according
> to [0].
> 
> When i try to build master-image with 
> 
> bitbake multiconfig:amp-c0:master-image
> 
> i get an error, which i have attached in [1].
> 
> My question is: Is it generally possible for a recipe to depend on one
> recipe multiple times but from a different multiconfig, like shown above?
> Also, if possible, are the sysroots of the dependencies automatically
> populated to the recipe depending on them, like with the usual DEPENDS
> variable.
> 
> 
> Thanks for any help!
> Johannes Wiesboeck
> 
> [0] 
> https://www.yoctoproject.org/docs/2.6/dev-manual/dev-manual.html#dev-building-images-for-multiple-targets-using-multiple-configurations
> [1] https://home.in.tum.de/~wiesboec/bitbake.txt
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [help] Multiconfig - Depending on Recipe multiple times

2019-08-29 Thread Johannes Wiesböck

Hello Everyone,

i am using Yocto on the thud branch to build images for a real-time
operating system based on FreeRTOS. I would like to run multiple images
on different CPU cores in an asynchronous multi-processing (AMP) configuration.
Each image will contain the software for only one single core. For
deployment, i would like to pack all images into one package.

Therefore, i would like to use multiconfig to build the same recipe four
times for the same hardware but with different compiler options,
determined by to core the image should run on. These builds are all based on
the same source code but differ in compiler options used for building. After
the images for all configurations are built, i would like to pack all images
into a single package for deployment.

I have created two recipes, one called amp-image, that should be built
once for every multiconfig. A second recipe called master-image,
depends on amp-image for every configuration, i.e. i have the line

do_compile[mcdepends] = "multiconfig:amp-c0:amp-c0:amp-image:do_build
multiconfig:amp-c0:amp-c1:amp-image:do_build"

in my master-image.bb file. I also have set up my multiconfigs according
to [0].

When i try to build master-image with

bitbake multiconfig:amp-c0:master-image

i get an error, which i have attached in [1].

My question is: Is it generally possible for a recipe to depend on one
recipe multiple times but from a different multiconfig, like shown above?
Also, if possible, are the sysroots of the dependencies automatically
populated to the recipe depending on them, like with the usual DEPENDS
variable.

Thanks for any help!
Johannes Wiesboeck

[0]
https://www.yoctoproject.org/docs/2.6/dev-manual/dev-manual.html#dev-building-images-for-multiple-targets-using-multiple-configurations
[1] https://home.in.tum.de/~wiesboec/bitbake.txt
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux] [PATCH] python-scapy: upgrade 2.4.2 -> 2.4.3

2019-08-29 Thread Joe MacDonald

[Re: [yocto] [meta-selinux] [PATCH] python-scapy: upgrade 2.4.2 -> 2.4.3] On 
19.08.29 (Thu 07:14) akuster808 wrote:

> 
> 
> On 8/28/19 10:41 PM, Yuan Chao wrote:
> > License file changed from bin/scapy to LICENSE
> Is this the correct layer?

There's no scapy in meta-selinux, AFAIK.  So proably this was destined
for meta-security instead.

-J.

> 
> -armin
> >
> > Signed-off-by: Yuan Chao 
> > ---
> >  recipes-security/scapy/python-scapy.inc   | 4 ++--
> >  .../scapy/{python-scapy_2.4.2.bb => python-scapy_2.4.3.bb}| 0
> >  .../scapy/{python3-scapy_2.4.2.bb => python3-scapy_2.4.3.bb}  | 0
> >  3 files changed, 2 insertions(+), 2 deletions(-)
> >  rename recipes-security/scapy/{python-scapy_2.4.2.bb => 
> > python-scapy_2.4.3.bb} (100%)
> >  rename recipes-security/scapy/{python3-scapy_2.4.2.bb => 
> > python3-scapy_2.4.3.bb} (100%)
> >
> > diff --git a/recipes-security/scapy/python-scapy.inc 
> > b/recipes-security/scapy/python-scapy.inc
> > index baa69b2..28e13f2 100644
> > --- a/recipes-security/scapy/python-scapy.inc
> > +++ b/recipes-security/scapy/python-scapy.inc
> > @@ -3,11 +3,11 @@ DESCRIPTION = "Scapy is a powerful interactive packet 
> > manipulation program. It i
> >  SECTION = "security"
> >  LICENSE = "GPLv2"
> >  
> > -LIC_FILES_CHKSUM = 
> > "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
> > +LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> >  
> >  S = "${WORKDIR}/git"
> >  
> > -SRCREV = "bad14cb1a5aee29f8107fbe8ad008d4645f14da7"
> > +SRCREV = "3047580162a9407ef05fe981983cacfa698f1159"
> >  SRC_URI = "git://github.com/secdev/scapy.git"
> >  
> >  inherit ptest
> > diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
> > b/recipes-security/scapy/python-scapy_2.4.3.bb
> > similarity index 100%
> > rename from recipes-security/scapy/python-scapy_2.4.2.bb
> > rename to recipes-security/scapy/python-scapy_2.4.3.bb
> > diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
> > b/recipes-security/scapy/python3-scapy_2.4.3.bb
> > similarity index 100%
> > rename from recipes-security/scapy/python3-scapy_2.4.2.bb
> > rename to recipes-security/scapy/python3-scapy_2.4.3.bb
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
-Joe MacDonald.
Linux Architect | Mentor® A Siemens Business
:wq


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux] [PATCH] python-scapy: upgrade 2.4.2 -> 2.4.3

2019-08-29 Thread akuster808




On 8/28/19 10:41 PM, Yuan Chao wrote:
> License file changed from bin/scapy to LICENSE
Is this the correct layer?

-armin
>
> Signed-off-by: Yuan Chao 
> ---
>  recipes-security/scapy/python-scapy.inc   | 4 ++--
>  .../scapy/{python-scapy_2.4.2.bb => python-scapy_2.4.3.bb}| 0
>  .../scapy/{python3-scapy_2.4.2.bb => python3-scapy_2.4.3.bb}  | 0
>  3 files changed, 2 insertions(+), 2 deletions(-)
>  rename recipes-security/scapy/{python-scapy_2.4.2.bb => 
> python-scapy_2.4.3.bb} (100%)
>  rename recipes-security/scapy/{python3-scapy_2.4.2.bb => 
> python3-scapy_2.4.3.bb} (100%)
>
> diff --git a/recipes-security/scapy/python-scapy.inc 
> b/recipes-security/scapy/python-scapy.inc
> index baa69b2..28e13f2 100644
> --- a/recipes-security/scapy/python-scapy.inc
> +++ b/recipes-security/scapy/python-scapy.inc
> @@ -3,11 +3,11 @@ DESCRIPTION = "Scapy is a powerful interactive packet 
> manipulation program. It i
>  SECTION = "security"
>  LICENSE = "GPLv2"
>  
> -LIC_FILES_CHKSUM = 
> "file://bin/scapy;beginline=9;endline=13;md5=1d5249872cc54cd4ca3d3879262d0c69"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
>  S = "${WORKDIR}/git"
>  
> -SRCREV = "bad14cb1a5aee29f8107fbe8ad008d4645f14da7"
> +SRCREV = "3047580162a9407ef05fe981983cacfa698f1159"
>  SRC_URI = "git://github.com/secdev/scapy.git"
>  
>  inherit ptest
> diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
> b/recipes-security/scapy/python-scapy_2.4.3.bb
> similarity index 100%
> rename from recipes-security/scapy/python-scapy_2.4.2.bb
> rename to recipes-security/scapy/python-scapy_2.4.3.bb
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
> b/recipes-security/scapy/python3-scapy_2.4.3.bb
> similarity index 100%
> rename from recipes-security/scapy/python3-scapy_2.4.2.bb
> rename to recipes-security/scapy/python3-scapy_2.4.3.bb

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [PATCH] aufs: for v5.3-rc3, update UAPI SPDX

2019-08-29 Thread zhe.he

From: "J. R. Okajima" 

Simply follows the commit in mainline,
622445541b75 2019-07-29 kbuild: detect missing "WITH
Linux-syscall-note" for uapi headers

Signed-off-by: J. R. Okajima 

Backport from git://github.com/sfjro/aufs5-linux.git
90ff497cebbb ("aufs: for v5.3-rc3, update UAPI SPDX")
to fix,
error: kernel-source/include/uapi/linux/aufs_type.h: missing "WITH 
Linux-syscall-note" for SPDX-License-Identifier

Signed-off-by: He Zhe 
---
This is for linux-yocto-dev all branches.

 include/uapi/linux/aufs_type.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/uapi/linux/aufs_type.h b/include/uapi/linux/aufs_type.h
index 0e3e2b1..59f050c 100644
--- a/include/uapi/linux/aufs_type.h
+++ b/include/uapi/linux/aufs_type.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL-2.0 */
+/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
 /*
  * Copyright (C) 2005-2019 Junjiro R. Okajima
  *
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] [meta-selinux][PATCH 2/2] mcstrans: specify INITDIR

2019-08-29 Thread Yi Zhao

By default the mcstrans init script will be installed to
/etc/rc.d/init.d directory. Specify INITDIR to install it to /etc/init.d
directory.

Signed-off-by: Yi Zhao 
---
 recipes-security/selinux/mcstrans.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/selinux/mcstrans.inc 
b/recipes-security/selinux/mcstrans.inc
index e66633d..0eb8720 100644
--- a/recipes-security/selinux/mcstrans.inc
+++ b/recipes-security/selinux/mcstrans.inc
@@ -15,7 +15,7 @@ inherit systemd update-rc.d
 DEPENDS += "libsepol libselinux libcap"
 
 # We do not need "${D}/" as a prefix anymore.
-EXTRA_OEMAKE += "SBINDIR=${base_sbindir}"
+EXTRA_OEMAKE += "SBINDIR=${base_sbindir} INITDIR=${sysconfdir}/init.d"
 
 do_install_append() {
 install -d ${D}${sbindir}
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH 1/2] setools: update SRC_URI

2019-08-29 Thread Yi Zhao

SETools has moved from https://github.com/TresysTechnology/setools to
https://github.com/SELinuxProject/setools
See: https://github.com/TresysTechnology/setools/wiki

Signed-off-by: Yi Zhao 
---
 recipes-security/setools/setools_4.1.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/setools/setools_4.1.1.bb 
b/recipes-security/setools/setools_4.1.1.bb
index 8bdbfba..db529f4 100644
--- a/recipes-security/setools/setools_4.1.1.bb
+++ b/recipes-security/setools/setools_4.1.1.bb
@@ -9,7 +9,7 @@ SECTION = "base"
 LICENSE = "GPLv2 & LGPLv2.1"
 
 S = "${WORKDIR}/git"
-SRC_URI = "git://github.com/TresysTechnology/${BPN}.git;branch=4.1 \
+SRC_URI = "git://github.com/SELinuxProject/${BPN}.git;branch=4.1 \
file://setools4-fixes-for-cross-compiling.patch \
file://setools4-fix-cross-compiling-errors-for-powerpc-mips.patch \
file://Fix-build-failure-with-GCC-7-due-to-possible-truncat.patch \
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [kernel-meta v5.2 1/2] fsl-mpc8315e-rdb/beaglebone: Replace CONFIG_MTD_NAND with CONFIG_MTD_RAW_NAND

The kernel option MTD_NAND has been renamed to MTD_RAW_NAND in the
kernel commit 72c5af002723 ("mtd: rawnand: Clarify Kconfig entry
MTD_NAND"), so adjust the cfg file according to this change.

Signed-off-by: Kevin Hao 
---
 bsp/beaglebone/beaglebone.cfg | 2 +-
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index f044061032b9..95000f78fc54 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -70,7 +70,7 @@ CONFIG_MTD_CFI_INTELEXT=y
 #
 # Disk-On-Chip Device Drivers
 #
-CONFIG_MTD_NAND=y
+CONFIG_MTD_RAW_NAND=y
 CONFIG_MTD_NAND_OMAP2=y
 CONFIG_MTD_NAND_OMAP_BCH=y
 
diff --git a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg 
b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
index cb7c40d37c22..91ea14614284 100644
--- a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
+++ b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
@@ -57,7 +57,7 @@ CONFIG_MTD_PHYSMAP_OF=y
 #
 # NAND Flash Device Drivers
 #
-CONFIG_MTD_NAND=y
+CONFIG_MTD_RAW_NAND=y
 CONFIG_MTD_NAND_FSL_ELBC=y
 
 #
-- 
2.14.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [kernel-meta v5.2 2/2] beaglebone: Drop the stale kernel options

These two kernel options have been delete by the following kernel
commits:
  99f629718272 ("net: ethernet: ti: cpsw: drop TI_DAVINCI_CPDMA config option")
  8c5dc8d9f19c ("video: backlight: Remove useless BACKLIGHT_LCD_SUPPORT kernel 
symbol")

Signed-off-by: Kevin Hao 
---
 bsp/beaglebone/beaglebone.cfg | 2 --
 1 file changed, 2 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index 95000f78fc54..ee2e623e740d 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -91,7 +91,6 @@ CONFIG_SMC91X=y
 CONFIG_SMSC911X=y
 CONFIG_TI_CPSW_PHY_SEL=y
 CONFIG_TI_CPSW=y
-CONFIG_TI_DAVINCI_CPDMA=y
 CONFIG_TI_DAVINCI_MDIO=y
 
 #
@@ -211,7 +210,6 @@ CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
 #
 # OMAP Display Device Drivers (new device model)
 #
-CONFIG_BACKLIGHT_LCD_SUPPORT=y
 CONFIG_LCD_CLASS_DEVICE=y
 CONFIG_LCD_PLATFORM=y
 CONFIG_BACKLIGHT_CLASS_DEVICE=y
-- 
2.14.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [kernel-meta v5.2 0/2] Fix the kernel_configcheck warnings for the v5.2 kernel

These two patches fix the kernel_configcheck warnings when building the
v5.2 kernel.

Kevin Hao (2):
  fsl-mpc8315e-rdb/beaglebone: Replace CONFIG_MTD_NAND with
CONFIG_MTD_RAW_NAND
  beaglebone: Drop the stale kernel options

 bsp/beaglebone/beaglebone.cfg | 4 +---
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 2 +-
 2 files changed, 2 insertions(+), 4 deletions(-)

-- 
2.14.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] [meta-selinux][PATCH 3/3] util-linux: drop obsolete patch

2019-08-29 Thread Yi Zhao


Hi Joe,


Seems you were missing this patch. Would you please merge it? Thanks.


//Yi


On 5/20/19 12:41 PM, Yi Zhao wrote:

Signed-off-by: Yi Zhao 
---
  .../util-linux/fix-libmount_la_DEPENDENCIES.patch  | 28 --
  1 file changed, 28 deletions(-)
  delete mode 100644 
recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch

diff --git 
a/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch 
b/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch
deleted file mode 100644
index ab54818..000
--- a/recipes-core/util-linux/util-linux/fix-libmount_la_DEPENDENCIES.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-Subject: [PATCH] util-linux: fix libmount_la_DEPENDENCIES.
-
-Upstream-Status: Pending
-
-libmount_la_LIBADD contains "-lselinux", this is not a object that
-could consider as a dependency target. So fix this.
-
-Signed-off-by: Xin Ouyang 

- libmount/src/Makemodule.am |2 +-
- 1 files changed, 1 insertions(+), 1 deletions(-)
-
-diff --git a/libmount/src/Makemodule.am b/libmount/src/Makemodule.am
-index 494e02a..bf494a4 100644
 a/libmount/src/Makemodule.am
-+++ b/libmount/src/Makemodule.am
-@@ -38,7 +38,7 @@ libmount_la_CFLAGS = \
-   -I$(top_srcdir)/libmount/src
-
- libmount_la_DEPENDENCIES = \
--  $(libmount_la_LIBADD) \
-+  libcommon.la libblkid.la \
-   libmount/src/libmount.sym \
-   libmount/src/libmount.h.in
-
---
-1.7.5.4
-

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [kernel-cache master] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx

2019-08-29 Thread Xulin Sun

This adds the cfg & scc files to support the LS2088A-RDB.

Signed-off-by: Xulin Sun 
---
 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc |   8 ++
 bsp/nxp-ls20xx/nxp-ls20xx.cfg  | 162 +
 bsp/nxp-ls20xx/nxp-ls20xx.scc  |   7 ++
 3 files changed, 177 insertions(+)
 create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
 create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.cfg
 create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.scc

diff --git a/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc 
b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
new file mode 100755
index ..e0d9b2b7
--- /dev/null
+++ b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc
@@ -0,0 +1,8 @@
+define KMACHINE nxp-ls20xx
+define KTYPE standard
+define KARCH arm64
+
+include ktypes/standard/standard.scc
+branch nxp-ls20xx
+
+include nxp-ls20xx.scc
diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.cfg b/bsp/nxp-ls20xx/nxp-ls20xx.cfg
new file mode 100755
index ..f554c916
--- /dev/null
+++ b/bsp/nxp-ls20xx/nxp-ls20xx.cfg
@@ -0,0 +1,162 @@
+..
+.WARNING
+.
+. This file is a kernel configuration fragment, and not a full kernel
+. configuration file.  The final kernel configuration is made up of
+. an assembly of processed fragments, each of which is designed to
+. capture a specific part of the final configuration (e.g. platform
+. configuration, feature configuration, and board specific hardware
+. configuration).  For more information on kernel configuration, please
+. consult the product documentation.
+.
+..
+
+CONFIG_ARM64=y
+CONFIG_ARM64_VA_BITS_48=y
+CONFIG_ARCH_LAYERSCAPE=y
+CONFIG_SCHED_MC=y
+CONFIG_ARM_SMMU=y
+CONFIG_ARM_SMMU_V3=y
+
+CONFIG_PCI=y
+CONFIG_PCI_LAYERSCAPE=y
+CONFIG_PCI_HOST_GENERIC=y
+CONFIG_PCI_XGENE=y
+CONFIG_PCI_MSI=y
+
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_STAT=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_QORIQ_CPUFREQ=y
+
+CONFIG_MTD=y
+CONFIG_MTD_CMDLINE_PARTS=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_ADV_OPTIONS=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_CFI_AMDSTD=y
+CONFIG_MTD_CFI_STAA=y
+CONFIG_MTD_DATAFLASH=y
+CONFIG_MTD_M25P80=y
+CONFIG_MTD_SST25L=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_MTD_RAW_NAND=y
+CONFIG_MTD_NAND_FSL_IFC=y
+CONFIG_SPI_FSL_QUADSPI=y
+CONFIG_SCSI_SAS_ATA=y
+CONFIG_SCSI_HISI_SAS=y
+CONFIG_ATA=y
+CONFIG_SATA_AHCI=y
+CONFIG_SATA_AHCI_PLATFORM=y
+CONFIG_AHCI_CEVA=y
+CONFIG_AHCI_XGENE=y
+CONFIG_AHCI_QORIQ=y
+CONFIG_SATA_SIL24=y
+
+CONFIG_FSL_XGMAC_MDIO=y
+CONFIG_HNS_DSAF=y
+CONFIG_HNS_ENET=y
+CONFIG_E1000=y
+CONFIG_E1000E=y
+
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_DW=y
+CONFIG_SERIAL_OF_PLATFORM=y
+CONFIG_SERIAL_FSL_LPUART=y
+CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
+
+CONFIG_SPI=y
+CONFIG_SPI_FSL_DSPI=y
+CONFIG_SPI_PL022=y
+CONFIG_SPI_NXP_FLEXSPI=y
+
+CONFIG_POWER_RESET_XGENE=y
+CONFIG_POWER_RESET_SYSCON=y
+CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
+
+CONFIG_THERMAL=y
+CONFIG_THERMAL_OF=y
+CONFIG_CPU_THERMAL=y
+CONFIG_THERMAL_EMULATION=y
+CONFIG_WATCHDOG=y
+CONFIG_ARM_SP805_WATCHDOG=y
+
+CONFIG_USB=y
+CONFIG_USB_OTG=y
+CONFIG_USB_XHCI_HCD=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_DWC3=y
+CONFIG_USB_DWC2=y
+CONFIG_USB_GADGET=y
+
+CONFIG_MMC=y
+CONFIG_MMC_ARMMMCI=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_OF_ARASAN=y
+CONFIG_MMC_SDHCI_OF_ESDHC=y
+CONFIG_MMC_SDHCI_CADENCE=y
+CONFIG_MMC_SPI=y
+CONFIG_MMC_DW=y
+
+CONFIG_GPIOLIB=y
+CONFIG_OF_GPIO=y
+
+CONFIG_MDIO_DEVICE=y
+CONFIG_MDIO_BITBANG=y
+CONFIG_PHYLIB=y
+CONFIG_AQUANTIA_PHY=y
+CONFIG_CORTINA_PHY=y
+
+#
+# I2C support
+#
+CONFIG_I2C=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_IMX=y
+CONFIG_I2C_MUX_PCA954x=y
+
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_DS3232=y
+CONFIG_RTC_DRV_PL031=y
+CONFIG_RTC_DRV_PCF2127=y
+
+CONFIG_DMADEVICES=y
+CONFIG_FSL_EDMA=y
+CONFIG_CMA=y
+CONFIG_DMA_CMA=y
+
+CONFIG_VFIO=y
+CONFIG_VFIO_PCI=y
+
+CONFIG_STAGING=y
+CONFIG_FSL_MC_BUS=y
+CONFIG_FSL_MC_DPIO=y
+
+CONFIG_CLK_QORIQ=y
+
+CONFIG_PHY_XGENE=y
+
+CONFIG_CRYPTO_DEV_FSL_CAAM=y
+CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y
+CONFIG_ARM64_CRYPTO=y
+CONFIG_CRYPTO_SHA1_ARM64_CE=y
+CONFIG_CRYPTO_SHA2_ARM64_CE=y
+CONFIG_CRYPTO_GHASH_ARM64_CE=y
+CONFIG_CRYPTO_AES_ARM64_CE_CCM=y
+CONFIG_CRYPTO_AES_ARM64_CE_BLK=y
+# CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT is not set
+
+# EDAC
+CONFIG_EDAC_LAYERSCAPE=y
+
+CONFIG_SENSORS_LM90=y
+CONFIG_SENSORS_INA2XX=y
+
+CONFIG_ARM_SBSA_WATCHDOG=y
diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.scc b/bsp/nxp-ls20xx/nxp-ls20xx.scc
new file mode 100755
index ..36f0ee7a
--- /dev/null
+++ b/bsp/nxp-ls20xx/nxp-ls20xx.scc
@@ -0,0 +1,7 @@
+kconf hardware nxp-ls20xx.cfg
+kconf hardware features/edac/edac.cfg
+
+include cfg/usb-mass-storage.scc
+
+include features/hugetlb/hugetlb.scc
+include arch/arm/32bit-compat.scc
-- 
2.17.1

--

[yocto] [meta-security] [PATCH] checksec: upgrade 1.11.1 -> 2.1.0

2019-08-29 Thread Yuan Chao

Signed-off-by: Yuan Chao 
---
 .../checksec/{checksec_1.11.1.bb => checksec_2.1.0.bb}  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename recipes-security/checksec/{checksec_1.11.1.bb => checksec_2.1.0.bb} 
(91%)

diff --git a/recipes-security/checksec/checksec_1.11.1.bb 
b/recipes-security/checksec/checksec_2.1.0.bb
similarity index 91%
rename from recipes-security/checksec/checksec_1.11.1.bb
rename to recipes-security/checksec/checksec_2.1.0.bb
index 835dffc..5c6528e 100644
--- a/recipes-security/checksec/checksec_1.11.1.bb
+++ b/recipes-security/checksec/checksec_2.1.0.bb
@@ -6,7 +6,7 @@ HOMEPAGE="https://github.com/slimm609/checksec.sh;
 
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=93fddcca19f6c897871f9b5f9a035f4a"
 
-SRCREV = "3c15cb89641c700096fdec0c1904a0cf9b83c5e2"
+SRCREV = "04582bad41589ad479ca8b1f0170ed317475b5a5"
 SRC_URI = "git://github.com/slimm609/checksec.sh"
 
 S = "${WORKDIR}/git"
-- 
2.17.1



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 1/2] meson-selinux.bbclass: fix meson flags for glib-2.0-native

2019-08-29 Thread Mikko.Rapeli

Hi,

On Wed, Aug 28, 2019 at 01:19:17PM -0400, Joe MacDonald wrote:
> Hi Mikko,
> 
> Is this specifically for warrior (or thud), maybe?  The following commit
> explains the current logic:
> 
> commit bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0
> Author: Yi Zhao 
> Date:   Wed Jun 12 15:53:20 2019 +0800
> 
> glib-2.0: fix configure error for meson build
> 
> In glib 2.60.x, it turns selinux into a meson feature. We should use
> '-Dselinux=enabled/disabled' rather than '-Dselinux=true/false' to
> enable/disable the feature.
> 
> Add meso-enable-selinux.bbclass for this change and inherit it in
> glib-2.0 bbappend to fix the configure error.
> 
> Signed-off-by: Yi Zhao 
> Signed-off-by: Joe MacDonald 
> 
> and the second patch is already present in tree:
> 
> commit 087fe5c8144c246c6361bd8bcbd1ffd9e9b675bb
> Author: Yi Zhao 
> Date:   Fri Aug 9 17:48:00 2019 +0800
> 
> libselinux: fix build with glibc 2.30
> 
> Fix build error:
> procattr.c:27:14: error: static declaration of 'gettid' follows
> non-static declaration
>27 | static pid_t gettid(void)
>   |  ^~
> In file included from 
> /buildarea/build/tmp/work/core2-64-poky-linux/libselinux/2.8-r0/recipe-sysroot/usr/include/unistd.h:1170,
>  from procattr.c:2:
> 
> /buildarea/build/tmp/work/core2-64-poky-linux/libselinux/2.8-r0/recipe-sysroot/usr/include/bits/unistd_ext.h:34:16:
> note: previous declaration of 'gettid' was here
>34 | extern __pid_t gettid (void) __THROW;
>   |^~
> 
> Signed-off-by: Yi Zhao 
> Signed-off-by: Joe MacDonald 
> 
> This is what my current work tree looks like, for reference:
> 
>   $ repo forall -p -c git log -1 --pretty=oneline
>   project meta-openembedded/
>   2ebaa8df1257389161d0bee9e553c28f63e52005 python3-pyatspi: Add Dbus ATSPI 
> recipe
>   
>   project meta-selinux/
>   154654a6fe12206a6b9ad6d8c36a4dbe672bcc46 selinux-python: Fix dependency for 
> ntpath
>   
>   project yocto-mainline/
>   ca2207f418b7847ffce4b8c53a5a442e5cf461d9 commands.py: fix typo

Hmm, good that same patches are already in master branch but I somehow got a
much older master branch state from remote 
git://git.yoctoproject.org/meta-selinux

commit a917c322c120c05fc6746fc9aca38c27398ffb4a
Author: Yi Zhao 
AuthorDate: Fri Apr 19 10:46:32 2019 +0800
Commit: Joe MacDonald 
CommitDate: Tue Apr 23 11:12:57 2019 -0400

Was also checking master-next there.

Based on time stamps in .git/modules/meta-selinux/refs/remotes/upstream/ my 
last fetch
was Aug 28 11:02 CET. Seems like the "libselinux: fix build with glibc 2.30"
was pushed to the server just after I had been checking for it:

commit 087fe5c8144c246c6361bd8bcbd1ffd9e9b675bb
Author: Yi Zhao 
AuthorDate: Fri Aug 9 17:48:00 2019 +0800
Commit: Joe MacDonald 
CommitDate: Wed Aug 28 10:26:52 2019 -0400

libselinux: fix build with glibc 2.30

Anyway, fixes are in and life continues :)

Thanks,

-Mikko

> -J.
> 
> [[yocto] [meta-selinux][PATCH 1/2] meson-selinux.bbclass: fix meson flags for 
> glib-2.0-native] On 19.08.28 (Wed 18:30) Mikko Rapeli wrote:
> 
> > With latest poky master, glib-2.0-native fails to compile:
> > 
> > | meson.build:1:0: ERROR: Value "false" for combo option is not one of the 
> > choices. Possible choices are: "enabled",
> >  "disabled", "auto".
> > 
> > Thus use enabled and disabled when enabling and disabling flags
> > with meson. Now glib-2.0-native compiles again.
> > 
> > Signed-off-by: Mikko Rapeli 
> > ---
> >  classes/meson-selinux.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/classes/meson-selinux.bbclass b/classes/meson-selinux.bbclass
> > index 77a763a..91c2a2b 100644
> > --- a/classes/meson-selinux.bbclass
> > +++ b/classes/meson-selinux.bbclass
> > @@ -1,4 +1,4 @@
> >  inherit selinux
> >  
> >  PACKAGECONFIG_append = " ${@target_selinux(d)}"
> > -PACKAGECONFIG[selinux] = "-Dselinux=true,-Dselinux=false,libselinux,"
> > +PACKAGECONFIG[selinux] = "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
> > -- 
> > 1.9.1
> > 
> > -- 
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> -- 
> -Joe MacDonald.
> :wq

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [PATCH 3/3] pci: pcie-rcar: add regulators support

From: Andrey Gusakov 

Add PCIe regulators for KingFisher board.

Signed-off-by: Meng Li 
---
 arch/arm64/boot/dts/renesas/ulcb-kf.dtsi | 47 +
 drivers/pci/controller/pcie-rcar.c   | 64 
 2 files changed, 111 insertions(+)

diff --git a/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi 
b/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
index a1e70b52727b..e8d431028fc7 100644
--- a/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
+++ b/arch/arm64/boot/dts/renesas/ulcb-kf.dtsi
@@ -50,6 +50,25 @@
startup-delay-us = <7>;
enable-active-high;
};
+
+   mpcie_3v3: regulator-mpcie_3v3 {
+   compatible = "regulator-fixed";
+   regulator-name = "mPCIe 3v3";
+   regulator-min-microvolt = <330>;
+   regulator-max-microvolt = <330>;
+   gpio = <_exp_77 14 GPIO_ACTIVE_HIGH>;
+   enable-active-high;
+   };
+
+   mpcie_1v8: regulator-mpcie_1v8 {
+   compatible = "regulator-fixed";
+   regulator-name = "mPCIe 1v8";
+   regulator-min-microvolt = <180>;
+   regulator-max-microvolt = <180>;
+   gpio = <_exp_77 15 GPIO_ACTIVE_HIGH>;
+   startup-delay-us = <20>;
+   enable-active-high;
+   };
 };
 
  {
@@ -233,6 +252,31 @@
interrupt-controller;
interrupt-parent = <>;
interrupts = <9 IRQ_TYPE_EDGE_FALLING>;
+
+   mpcie_wake {
+   gpio-hog;
+   gpios = <0 GPIO_ACTIVE_HIGH>;
+   output-low;
+   line-name = "mPCIe WAKE#";
+   };
+   mpcie_wdisable {
+   gpio-hog;
+   gpios = <1 GPIO_ACTIVE_HIGH>;
+   output-high;
+   line-name = "mPCIe W_DISABLE";
+   };
+   mpcie_clreq {
+   gpio-hog;
+   gpios = <2 GPIO_ACTIVE_HIGH>;
+   input;
+   line-name = "mPCIe CLKREQ#";
+   };
+   mpcie_ovc {
+   gpio-hog;
+   gpios = <3 GPIO_ACTIVE_HIGH>;
+   input;
+   line-name = "mPCIe OVC";
+   };
};
 
i2cswitch4: i2c-switch@71 {
@@ -259,6 +303,9 @@
 
  {
status = "okay";
+
+   pcie3v3-supply = <_3v3>;
+   pcie1v8-supply = <_1v8>;
 };
 
  {
diff --git a/drivers/pci/controller/pcie-rcar.c 
b/drivers/pci/controller/pcie-rcar.c
index f6a669a9af41..8e7e714e33fd 100644
--- a/drivers/pci/controller/pcie-rcar.c
+++ b/drivers/pci/controller/pcie-rcar.c
@@ -14,6 +14,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -151,6 +152,8 @@ struct rcar_pcie {
struct list_headresources;
int root_bus_nr;
struct clk  *bus_clk;
+   struct regulator*pcie3v3; /* 3.3V power supply */
+   struct regulator*pcie1v8; /* 1.8V power supply */
struct  rcar_msi msi;
 };
 
@@ -1120,6 +1123,36 @@ static const struct of_device_id rcar_pcie_of_match[] = {
{},
 };
 
+static int rcar_pcie_set_vpcie(struct rcar_pcie *pcie)
+{
+   struct device *dev = pcie->dev;
+   int err;
+
+   if (!IS_ERR(pcie->pcie3v3)) {
+   err = regulator_enable(pcie->pcie3v3);
+   if (err) {
+   dev_err(dev, "fail to enable vpcie3v3 regulator\n");
+   goto err_out;
+   }
+   }
+
+   if (!IS_ERR(pcie->pcie1v8)) {
+   err = regulator_enable(pcie->pcie1v8);
+   if (err) {
+   dev_err(dev, "fail to enable vpcie1v8 regulator\n");
+   goto err_disable_3v3;
+   }
+   }
+
+   return 0;
+
+err_disable_3v3:
+   if (!IS_ERR(pcie->pcie3v3))
+   regulator_disable(pcie->pcie3v3);
+err_out:
+   return err;
+}
+
 static int rcar_pcie_probe(struct platform_device *pdev)
 {
struct device *dev = >dev;
@@ -1138,6 +1171,31 @@ static int rcar_pcie_probe(struct platform_device *pdev)
pcie->dev = dev;
platform_set_drvdata(pdev, pcie);
 
+   pcie->pcie3v3 = devm_regulator_get_optional(dev, "pcie3v3");
+   if (IS_ERR(pcie->pcie3v3)) {
+   if (PTR_ERR(pcie->pcie3v3) == -EPROBE_DEFER) {
+   pci_free_host_bridge(bridge);
+   return -EPROBE_DEFER;
+   }
+   dev_info(dev, "no pcie3v3 regulator found\n");
+   }
+
+   pcie->pcie1v8 = devm_regulator_get_optional(dev, "pcie1v8");
+   if (IS_ERR(pcie->pcie1v8)) {
+   if (PTR_ERR(pcie->pcie1v8) == -EPROBE_DEFER) {
+   pci_free_host_bridge(bridge);
+

[linux-yocto] [PATCH 2/3] driver: net: can: disable clock when it is in enable status

From: Limeng 

If disable a clock when it is already in disable status, there
will be a warning trace generated. So, it is need to confirm
whether what status the clock is in before disable it.

Signed-off-by: Meng Li 
---
 drivers/net/can/rcar/rcar_can.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/net/can/rcar/rcar_can.c b/drivers/net/can/rcar/rcar_can.c
index 13e66297b65f..f788b826e4aa 100644
--- a/drivers/net/can/rcar/rcar_can.c
+++ b/drivers/net/can/rcar/rcar_can.c
@@ -15,6 +15,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 
@@ -864,7 +865,9 @@ static int __maybe_unused rcar_can_suspend(struct device 
*dev)
writew(ctlr, >regs->ctlr);
priv->can.state = CAN_STATE_SLEEPING;
 
-   clk_disable(priv->clk);
+   if(__clk_is_enabled(priv->clk))
+   clk_disable(priv->clk);
+
return 0;
 }
 
-- 
2.17.1

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [linux-yocto-dev]: [kernel standard/base]: renesas-rcar: add some patches to improve features on renesas-rcar platform

From: Limeng 

Hi Bruce,

I am working on BSP renesas-rcar platform, and intend to merge this BSP 
supporting into yocto community.
Below 3 patches are used to improve gpio, CAN BUS, audio and PCIe features

0001-arch-arm64-dts-Set-gpio5-pin9-as-input-by-default.patch
0002-driver-net-can-disable-clock-when-it-is-in-enable-st.patch
0003-pci-pcie-rcar-add-regulators-support.patch

Could you please merge the 3 patches into linux-yocto-dev, branch is 
standard/base?

 arch/arm64/boot/dts/renesas/ulcb-kf.dtsi |   56 +++
 drivers/net/can/rcar/rcar_can.c  |5 +-
 drivers/pci/controller/pcie-rcar.c   |   64 +++
 3 files changed, 124 insertions(+), 1 deletion(-)


thanks,
Limeng
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 1/3] arch: arm64: dts: Set gpio5-pin9 as input by default