[linux-yocto] [PATCH v5.2] nvme-pci: Set the prp2 correctly when using more than 4k page

2019-10-18 Thread Kevin Hao 
commit a4f40484e7f1dff56bb9f286cc59ffa36e0259eb from
git://git.infradead.org/nvme.git

In the current code, the nvme is using a fixed 4k PRP entry size,
but if the kernel use a page size which is more than 4k, we should
consider the situation that the bv_offset may be larger than the
dev->ctrl.page_size. Otherwise we may miss setting the prp2 and then
cause the command can't be executed correctly.

Fixes: dff824b2aadb ("nvme-pci: optimize mapping of small single segment 
requests")
Cc: sta...@vger.kernel.org
Reviewed-by: Christoph Hellwig 
Signed-off-by: Kevin Hao 
Signed-off-by: Keith Busch 
---
Hi Bruce,

This patch has already been merged into nvme-5.4 and I also CCed 
sta...@vger.kernel.org,
so in theory it could propagate to linux-yocto via the stable update.
But this issue cause a critical malfunction for the nvme interface and
block our validation for it. So I would like to pick this patch ASAP.
We should merge this into v5.2/standard/base branch.

 drivers/nvme/host/pci.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 4b181969c432..869f462e6b6e 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -773,7 +773,8 @@ static blk_status_t nvme_setup_prp_simple(struct nvme_dev 
*dev,
struct bio_vec *bv)
 {
struct nvme_iod *iod = blk_mq_rq_to_pdu(req);
-   unsigned int first_prp_len = dev->ctrl.page_size - bv->bv_offset;
+   unsigned int offset = bv->bv_offset & (dev->ctrl.page_size - 1);
+   unsigned int first_prp_len = dev->ctrl.page_size - offset;
 
iod->first_dma = dma_map_bvec(dev->dev, bv, rq_dma_dir(req), 0);
if (dma_mapping_error(dev->dev, iod->first_dma))
-- 
2.14.4

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

[linux-yocto] [PATCH v5.2] cn96xx: Another patch series for the cn96xx SoC support

2019-09-23 Thread Kevin Hao 
Hi Bruce,

Here is another patch series got from Marvell for the cn96xx SoC support.
It mainly include some fixes for the mmc and Ethernet. Please help me
merge this into both v5.2/standard/cn96xx and v5.2/standard/preempt-rt/cn96xx 
branch.

The following changes since commit d186856ba1914ca0fbf715fe9b0f31067dd517a4:

  mmc: cavium: Drop the aligned check for the dma address (2019-09-20 00:23:49 
-0400)

are available in the Git repository at:

  https://github.com/haokexin/linux v5.2/standard/cn96xx

for you to fetch changes up to 8ddd7904ae8f42c95c7b13bb877e663d39e802ac:

  octeontx2-af: Add T98 devid to PTP id table (2019-09-23 17:02:17 +0800)


Christina Jacob (2):
  octeontx2-pf: Disply the link detected status in ethtool command
  net: thunderx: Do a PCS reset upon SGMII link toggle

Geetha sowjanya (1):
  octeontx2-pf: Ignore NPC parser layer errors

Hao Zheng (2):
  octeontx2-af: add parser support for DSA, extended DSA and eDSA
  octeontx2-af: combine LB_STAG and LB_QINQ to one LB ltype

Peter Swain (4):
  mmc: cavium: reorganize before vqmmc switching
  mmc: cavium: slot switch by vqmmc/gpio
  mmc: cavium: do not drop bus lock in tuning
  mmc: cavium: use calibrated timing taps

Subbaraya Sundeep (8):
  octeontx2-pf: Fix memory leaks
  octeontx2-af: Change message level to debug
  octeontx2-af: Enable odd number of AF VFs also
  octeontx2-pf: Use helper function for LBK VF
  octeontx2-af: Use nix_smq_flush function
  octeontx2-af: Always enable mcam rules for TX
  octeontx2-af: Transmit packets during SMQ flush
  octeontx2-pf: Add barrier to sync interface status

Sunil Goutham (8):
  octeontx2-af: Fix programming and logical issues
  octeontx2-pf: Fix VF id in the FLR handler
  octeontx2-pf: Fix interface init and shutdown sequence
  octeontx2-pf: Use post increment STP to free pointers to Aura
  octeontx2-pf: Add debug messages for MSIX alloc failure
  arm64: Increase NR_IRQS to a large number
  octeontx2-af: Fix compilation issue
  octeontx2-pf: Fix memory leak while freeing SQBs

Tomasz Michalec (1):
  octeontx2-af: Add T98 devid to PTP id table

Vidhya Vidhyaraman (1):
  octeontx2-af: Add programmed macaddr to RVU pfvf

 Documentation/devicetree/bindings/mmc/cavium-mmc.txt  |  10 +-
 arch/arm64/include/asm/irq.h  |   9 ++
 drivers/mmc/host/cavium-thunderx.c|  97 ++---
 drivers/mmc/host/cavium.c | 227 
-
 drivers/mmc/host/cavium.h |   7 +-
 drivers/net/ethernet/cavium/thunder/thunder_bgx.c |  35 ++---
 drivers/net/ethernet/marvell/octeontx2/af/cgx.c   |   6 +-
 drivers/net/ethernet/marvell/octeontx2/af/mbox.c  |   2 +-
 drivers/net/ethernet/marvell/octeontx2/af/npc.h   |   9 +-
 drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h   | 731 
+---
 drivers/net/ethernet/marvell/octeontx2/af/ptp.c   |   4 +
 drivers/net/ethernet/marvell/octeontx2/af/rvu.c   |  12 --
 drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c   |  26 ++--
 drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c   |  23 ++-
 drivers/net/ethernet/marvell/octeontx2/af/rvu_fixes.c |  14 ++
 drivers/net/ethernet/marvell/octeontx2/af/rvu_fixes.h |  21 +++
 drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c   |  26 ++--
 drivers/net/ethernet/marvell/octeontx2/af/rvu_npc.c   |  17 +--
 drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c|  15 +-
 drivers/net/ethernet/marvell/octeontx2/nic/Makefile   |   2 +-
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c  |  49 ++-
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h  |  29 ++--
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_ethtool.c |  33 -
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c  |  57 +---
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_smqvf.c   | 291 
+
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.c|   9 ++
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_txrx.h|   6 +-
 drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c  |  32 ++--
 28 files changed, 1463 insertions(+), 336 deletions(-)
 create mode 100644 drivers/net/ethernet/marvell/octeontx2/af/rvu_fixes.h
 create mode 100644 drivers/net/ethernet/marvell/octeontx2/nic/otx2_smqvf.c

Thanks,
Kevin


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 v5.2] Add the support for the Marvell cn96xx SoC

2019-09-03 Thread Kevin Hao 
On Tue, Sep 03, 2019 at 02:00:11PM -0400, Bruce Ashfield wrote:
> On Tue, Sep 3, 2019 at 3:39 AM Kevin Hao  wrote:
> >
> > Hi Bruce,
> >
> > This patch series adds the kernel and kernel meta for the support of the
> > Marvell cn96xx SoC support. These patches are almost the same as what I
> > have sent for the linux-yocto-dev [1] [2]. The major difference between
> 
> I assume that you still also want the linux-yocto-dev changes merged ?

Yes, Thanks Bruce.

Kevin

> That is mhy plan.
> 
> > them is that the BPHY driver is added. The BPHY driver handles ioctl to
> > set/clear irq handlers in EL3 using SMC calls. The purpose of this is to
> > handle some BPHY interrupts in userspace directly. In order to support this,
> > we have to make some ugly hack to some core files like 
> > arch/arm64/mm/context.c
> > or arch/arm64/mm/context.c, but the change is pretty simple and are 
> > protected
> > with the specific kernel option.
> 
> perfect. Sounds safe for standard/base, so I'll look at merging it there.
> 
> Bruce
> 
> >
> > [1] 
> > https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007886.html
> > [2] 
> > https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007887.html
> >
> > Thanks,
> > Kevin
> 
> 
> 
> -- 
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II


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

[linux-yocto] [kernel-meta] bsp: Add the support for the marvell-cn96xx BSP

2019-09-03 Thread Kevin Hao 
This adds the cfg files to support the Marvell OCTEON TX2
CN96XX multicore arm64 SoC.

Signed-off-by: Kevin Hao 
---
 bsp/marvell-cn96xx/marvell-cn96xx-standard.scc |   7 ++
 bsp/marvell-cn96xx/marvell-cn96xx.cfg  | 107 +
 bsp/marvell-cn96xx/marvell-cn96xx.scc  |   6 ++
 3 files changed, 120 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 ..7dc73ac245f5
--- /dev/null
+++ b/bsp/marvell-cn96xx/marvell-cn96xx.cfg
@@ -0,0 +1,107 @@
+..
+.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
+
+# BPHY
+CONFIG_MARVELL_OTX_BPHY_CTR=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

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

[linux-yocto] [kernel] The kernel patches for the Marvell cn96xx support

2019-09-03 Thread Kevin Hao 
 parser support for mpls in udp
  octeontx2-af: fix parser error for udp packets with no payload

Harman Kalra (3):
  octeontx2-af: Support for PTP notification to PF
  octeontx2-af: Adding PTP CGX config cleanup in FLR
  octeontx2-af: Sending tsc value to the userspace

Jerin Jacob (3):
  octeontx2-af: add npa error af interrupt handlers
  octeontx2-af: add nix error af interrupt handlers
  octeontx2-af: Workaround for NIX CQ hang HW issue

Kevin Hao (1):
  octeontx2-af: Fix the using of variable length arrays

Kiran Kumar K (6):
  octeontx2-af: Add support for rss key types
  octeontx2-af: Add rss flow key tunnel types
  octeontx2-af: Add inner layer rss support
  octeontx2-af: align rss flow alg with npc profile
  octeontx2-af: Extract layer ID LE's ltypes to NPC parse key
  octeontx2-af: NPC Tx parse data key ext profile

Krzysztof Garczynski (1):
  octeontx2-af: txschq limits handling

Linu Cherian (12):
  iommu/arm-smmu-v3: Force 32 byte command queue memory reads on CN96XX SMMU
  octeontx2-af: Get PF macaddress from firmware
  octeontx2-af: Restore MSIXTR_BASE register upon module exit
  octeontx2-af: Misc CGX changes
  octeontx2-af: Use the right wake_up API variant in CGX command interface
  octeontx2-pf: Add support to configure loopback
  octeontx2-pf: Register and handle CGX link notifications
  octeontx2-af: Update CGX speed mapping table for 80G
  Revert "octeontx2-af: Get PF macaddress from firmware"
  octeontx2-af: Add support for importing firmware data
  octeontx2-pf: Keep link notification enabled until device detach
  octeontx2-af: Support NIX rx/tx counters at CGX port level

Lukasz Bartosik (2):
  octeontx2-af: add CPT support to AF driver
  octeontx2-af: don't register CPT AF interrupts

Nithin Dabilpuram (5):
  octeontx2-af: Clear NPC MCAM entries before update
  octeontx2-af: add support for changing vlan tpid
  octeontx2-af: enable cgx lmac tx link while flush
  octeontx2-af: NDC sync op af mbox support
  octeontx2-af: Fix inner l4 layer id

Pavan Nikhilesh (16):
  octeontx2-af: add mbox to configure thresholds per HWGRP
  octeontx2-af: Add TIM unit support.
  octeontx2-af: add workaround for TIM reverse lookup
  octeontx2-af: update TIM 10ns clk source min interval
  octeontx2-af: add mbox to get SSO GWS/GGRP stats
  octeontx2-af: update SSO GWS teardown sequence
  octeontx2-af: update SSO HWGRP teardown sequence
  octeontx2-af: manually dain partially consumed TAQ buffers
  octeontx2-af: add intradevice FLR handling
  octeontx2-af: ignore sso lf count when checking pffunc validity
  octeontx2-af: restore sso hwgrp default thresholds
  octeontx2-af: drain xaq before reconfiguring aura
  octeontx2-af: use get blkaddr function instead of macro
  octeontx2-af: add sso error af interrupt handlers
  octeontx2-af: add debugfs support for sso
  octeontx2-af: fix TIM slot to lf lookup

Peter Swain (14):
  gpio: octeontx2: extend PIN_SEL to cover cn96xx
  gpio: thunderx: avoid potential deadlock
  mmc: cavium: fix shutdown deadlock with active sd-card
  mmc: cavium: forbid unaligned DMA
  mmc: cavium: finish_dma_single() should teardown/unmap
  mmc: cavium: skip unavailable slots
  mmc: cavium: CMD19/21 type correction
  mmc: octeontx: cn96xx HS200-8wide-100MHz
  mmc: cavium: track & apply CMD6 bus changes ASAP
  mmc: cavium: execute_tuning for octeontx2
  mmc: cavium: avoid single-slot startup issues
  mmc: cavium: fix swiotlb buffer is full
  mmc: cavium: correct clock divisor
  mmc: cavium: amend hs400 tuning

Prakash Brahmajyosyula (7):
  octeontx2-af: Add NPA qsize {aura,pool}_contexts to debugfs
  octeontx2-af: Add CGX LMAC stats to debugfs
  octeontx2-af: Add NIX RQ, SQ and CQ contexts to debugfs
  octeontx2-af: Add NDC block stats to debugfs.
  octeontx2-af: add nix {cq,rq and sq} qsize contexts to debugfs.
  net: cavium: Add PTP subsystem ids, to recongnize new chips.
  octeontx2-pf: msglvl based debug support.

Radha Mohan Chintakuntla (8):
  octeontx2-af: Add SSO unit support to the AF driver
  gpio: thunderx: Add support for EL0 interrupts for GPIO
  gpio: thunderx: Remove char device when exiting driver
  gpio: thunderx: Adjust the msi base for cn96xx gpio
  misc: otx_bphy_ctr: Add OcteonTx2 BPHY control driver
  misc: otx_bphy_ctr: Increase the maximum BPHY interrupts to be supported
  misc: otx_bphy_ctr: Allow maximum interrupts of 27 to userspace in BPHY
  octeontx2-af: Skip CGX probe if not connected to NIX

SrujanaChalla (2):
  octeontx2-af: Add CPT debug entries to debugfs
  crypto: restructure marvell directory

Stanislaw Kardach (17):
  octeontx2-af: Add resource partitioning config
  octeontx2-af: Add free rsrc count mbox msg

[linux-yocto] [linux-yocto v5.2] Add the support for the Marvell cn96xx SoC

2019-09-03 Thread Kevin Hao 
Hi Bruce,

This patch series adds the kernel and kernel meta for the support of the
Marvell cn96xx SoC support. These patches are almost the same as what I
have sent for the linux-yocto-dev [1] [2]. The major difference between
them is that the BPHY driver is added. The BPHY driver handles ioctl to
set/clear irq handlers in EL3 using SMC calls. The purpose of this is to
handle some BPHY interrupts in userspace directly. In order to support this,
we have to make some ugly hack to some core files like arch/arm64/mm/context.c
or arch/arm64/mm/context.c, but the change is pretty simple and are protected
with the specific kernel option.

[1] https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007886.html
[2] https://lists.yoctoproject.org/pipermail/linux-yocto/2019-August/007887.html

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

Re: [linux-yocto] [kernel-cache master] bsp: Add the support for the marvell-cn96xx BSP

2019-08-29 Thread Kevin Hao 
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

2019-08-29 Thread Kevin Hao 
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

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

2019-08-29 Thread Kevin Hao 
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

2019-08-29 Thread Kevin Hao 
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

2019-08-29 Thread Kevin Hao 
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: [linux-yocto] [kernel-cache yocto-5.0][PATCH 0/1] ti-am335x: add base support

2019-08-28 Thread Kevin Hao 
On Wed, Aug 28, 2019 at 10:47:47PM -0400, Jun Miao wrote:
> Hi Bruce,
>   Beacuse the CI/CD project must contain the linux-yocto kernel building 
> successfully, we usually choose the yocto-5.0 branch. 
>   Please help me add this scc/cfg to yocto-5.0 branch.

Bruce has sent out the recipe for the 5.2 kernel and plan to drop the
recipe for the 5.0 kernel. Then it will make no sense for this patch series.

Thanks,
Kevin

> 
> Thanks 
> 
> 
> 
> Jun Miao (1):
>   ti-am335x: add the basic scc/cfg enablement
> 
>  bsp/ti-am335x/ti-am335x-standard.scc |   8 +
>  bsp/ti-am335x/ti-am335x.cfg  | 239 +++
>  bsp/ti-am335x/ti-am335x.scc  |   7 +
>  3 files changed, 254 insertions(+)
>  create mode 100644 bsp/ti-am335x/ti-am335x-standard.scc
>  create mode 100644 bsp/ti-am335x/ti-am335x.cfg
>  create mode 100644 bsp/ti-am335x/ti-am335x.scc
> 
> -- 
> 2.22.0
> 
> -- 
> ___
> linux-yocto mailing list
> linux-yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto


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

[linux-yocto] [kernel-cache master] bsp: Add the support for the marvell-cn96xx BSP

2019-08-20 Thread Kevin Hao 
This adds the cfg files to support the Marvell OCTEON TX2
CN96XX multicore arm64 SoC.

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

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

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

2019-08-20 Thread Kevin Hao 
-pf: Update hardware workarounds for 95xx A1 silicon
  PCI: quirks : Apply ACS quirk for all devices
  octeontx2-pf: Enable CQ interrupt coalescing
  octeontx2-pf: Fix RQ CQ RED and DROP levels for 96xx B0

Hao Zheng (10):
  octeontx2-af: change NPC KPU profile format
  octeontx2-af: NPC KPU profile update (ver 1.3.0):
  octeontx2-af: NPC KPU profile fix
  octeontx2-af: add NPC parser support for QinQ with TPID of 0x8100
  octeontx2-af: Turn on L2 multicast address check
  octeontx2-af: NPC parser profile change, move lb_ptr to point to tpid
  octeontx2-af: NPC parser profile add support for nix_inst_hdr on tx
  octeontx2-af: reorganize NPC parser profile for tunnel protocols
  octeontx2-af: provide parser support for mpls in udp
  octeontx2-af: fix parser error for udp packets with no payload

Harman Kalra (3):
  octeontx2-af: Support for PTP notification to PF
  octeontx2-af: Adding PTP CGX config cleanup in FLR
  octeontx2-af: Sending tsc value to the userspace

Jerin Jacob (3):
  octeontx2-af: add npa error af interrupt handlers
  octeontx2-af: add nix error af interrupt handlers
  octeontx2-af: Workaround for NIX CQ hang HW issue

Kevin Hao (2):
  octeontx2-af: Compatible with the old firmware version
  octeontx2-af: Fix the using of variable length arrays

Kiran Kumar K (6):
  octeontx2-af: Add support for rss key types
  octeontx2-af: Add rss flow key tunnel types
  octeontx2-af: Add inner layer rss support
  octeontx2-af: align rss flow alg with npc profile
  octeontx2-af: Extract layer ID LE's ltypes to NPC parse key
  octeontx2-af: NPC Tx parse data key ext profile

Krzysztof Garczynski (1):
  octeontx2-af: txschq limits handling

Linu Cherian (10):
  iommu/arm-smmu-v3: Force 32 byte command queue memory reads on CN96XX SMMU
  octeontx2-af: Restore MSIXTR_BASE register upon module exit
  octeontx2-af: Misc CGX changes
  octeontx2-af: Use the right wake_up API variant in CGX command interface
  octeontx2-pf: Add support to configure loopback
  octeontx2-pf: Register and handle CGX link notifications
  octeontx2-af: Update CGX speed mapping table for 80G
  octeontx2-af: Add support for importing firmware data
  octeontx2-pf: Keep link notification enabled until device detach
  octeontx2-af: Support NIX rx/tx counters at CGX port level

Lukasz Bartosik (2):
  octeontx2-af: add CPT support to AF driver
  octeontx2-af: don't register CPT AF interrupts

Nithin Dabilpuram (5):
  octeontx2-af: Clear NPC MCAM entries before update
  octeontx2-af: add support for changing vlan tpid
  octeontx2-af: enable cgx lmac tx link while flush
  octeontx2-af: NDC sync op af mbox support
  octeontx2-af: Fix inner l4 layer id

Pavan Nikhilesh (16):
  octeontx2-af: add mbox to configure thresholds per HWGRP
  octeontx2-af: Add TIM unit support.
  octeontx2-af: add workaround for TIM reverse lookup
  octeontx2-af: update TIM 10ns clk source min interval
  octeontx2-af: add mbox to get SSO GWS/GGRP stats
  octeontx2-af: update SSO GWS teardown sequence
  octeontx2-af: update SSO HWGRP teardown sequence
  octeontx2-af: manually dain partially consumed TAQ buffers
  octeontx2-af: add intradevice FLR handling
  octeontx2-af: ignore sso lf count when checking pffunc validity
  octeontx2-af: restore sso hwgrp default thresholds
  octeontx2-af: drain xaq before reconfiguring aura
  octeontx2-af: use get blkaddr function instead of macro
  octeontx2-af: add sso error af interrupt handlers
  octeontx2-af: add debugfs support for sso
  octeontx2-af: fix TIM slot to lf lookup

Peter Swain (14):
  gpio: octeontx2: extend PIN_SEL to cover cn96xx
  gpio: thunderx: avoid potential deadlock
  mmc: cavium: fix shutdown deadlock with active sd-card
  mmc: cavium: forbid unaligned DMA
  mmc: cavium: finish_dma_single() should teardown/unmap
  mmc: cavium: skip unavailable slots
  mmc: cavium: CMD19/21 type correction
  mmc: octeontx: cn96xx HS200-8wide-100MHz
  mmc: cavium: track & apply CMD6 bus changes ASAP
  mmc: cavium: execute_tuning for octeontx2
  mmc: cavium: avoid single-slot startup issues
  mmc: cavium: fix swiotlb buffer is full
  mmc: cavium: correct clock divisor
  mmc: cavium: amend hs400 tuning

Prakash Brahmajyosyula (7):
  octeontx2-af: Add NPA qsize {aura,pool}_contexts to debugfs
  octeontx2-af: Add CGX LMAC stats to debugfs
  octeontx2-af: Add NIX RQ, SQ and CQ contexts to debugfs
  octeontx2-af: Add NDC block stats to debugfs.
  octeontx2-af: add nix {cq,rq and sq} qsize contexts to debugfs.
  net: cavium: Add PTP subsystem ids, to recongnize new chips.
  octeontx2-pf: msglvl based debug support.

Radha Mohan Chintakuntla (8):
  octeontx2-af: Add SSO unit support to the AF driver

Re: [yocto] [PATCH][thud] meta-yocto-bsp: Bump to the latest stable kernel for the BSPs

2019-08-12 Thread Kevin Hao 
On Fri, Apr 19, 2019 at 01:23:35PM +0800, Kevin Hao wrote:
> In order to fix a systemtap bug [1] on arm board, we backport a kernel
> patch from v5.0 kernel to v4.14 & v4.18 kernel, then need to bump the
> kernel version to include this patch. Even this is only an arm specific
> bug, we would like to bump the kernel version for the BSPs at the same
> time. Boot test for all the boards.
> 
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273

Hi Armin,

Could you help merge this patch to thud branch?

Thanks,
Kevin

> 
> Signed-off-by: Kevin Hao 
> ---
>  .../recipes-kernel/linux/linux-yocto_4.14.bbappend   | 20 
> ++--
>  .../recipes-kernel/linux/linux-yocto_4.18.bbappend   | 20 
> ++--
>  2 files changed, 20 insertions(+), 20 deletions(-)
> 
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend 
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> index 502485a94b15..426757e48c9e 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>  
> -SRCREV_machine_genericx86?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
> -SRCREV_machine_genericx86-64 ?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
> -SRCREV_machine_edgerouter ?= "e06bfa18c727bd0e6e10cf26d9f161e4c791f52b"
> -SRCREV_machine_beaglebone-yocto ?= "b8805de77dcf8f59d8368fee4921c146c1300a6a"
> -SRCREV_machine_mpc8315e-rdb ?= "f88e87360b10f8fbd853a7d412982e6620f3f96d"
> +SRCREV_machine_genericx86?= "5252513a39b4b3773debab1f77071d7c430ecb10"
> +SRCREV_machine_genericx86-64 ?= "5252513a39b4b3773debab1f77071d7c430ecb10"
> +SRCREV_machine_edgerouter ?= "d8fb40cd0e99325715c70aed6f361a8318097829"
> +SRCREV_machine_beaglebone-yocto ?= "c67809688bd22cb4cb909bcf1a1045e6337c3229"
> +SRCREV_machine_mpc8315e-rdb ?= "258ee8228e0a512c6dbe2a0dadcd9f030ba45964"
>  
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>  
> -LINUX_VERSION_genericx86 = "4.14.76"
> -LINUX_VERSION_genericx86-64 = "4.14.76"
> -LINUX_VERSION_edgerouter = "4.14.71"
> -LINUX_VERSION_beaglebone-yocto = "4.14.71"
> -LINUX_VERSION_mpc8315e-rdb = "4.14.71"
> +LINUX_VERSION_genericx86 = "4.14.98"
> +LINUX_VERSION_genericx86-64 = "4.14.98"
> +LINUX_VERSION_edgerouter = "4.14.98"
> +LINUX_VERSION_beaglebone-yocto = "4.14.98"
> +LINUX_VERSION_mpc8315e-rdb = "4.14.98"
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend 
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
> index 7f15843f3a90..11b35cc1c2f8 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
> @@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>  
> -SRCREV_machine_genericx86?= "db2d813869a0501782469ecdb17e277a501c9f57"
> -SRCREV_machine_genericx86-64 ?= "db2d813869a0501782469ecdb17e277a501c9f57"
> -SRCREV_machine_edgerouter ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
> -SRCREV_machine_beaglebone-yocto ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
> -SRCREV_machine_mpc8315e-rdb ?= "99071a599d8650b069fb8135866fca203f375350"
> +SRCREV_machine_genericx86?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
> +SRCREV_machine_genericx86-64 ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
> +SRCREV_machine_edgerouter ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
> +SRCREV_machine_beaglebone-yocto ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
> +SRCREV_machine_mpc8315e-rdb ?= "0802dc980cbc8bdb156d6fe305e7b88e6b602634"
>  
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> @@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
>  
> -LINUX_VERSION_genericx86 = "4.18.22"
> -LINUX_VERSION_genericx86-64 = "4.18.22"
> -LINUX_VERSION_edgerouter = "4.18.25"
> -LINUX_VERSION_beaglebone-yocto = "4.18.25"
> -LINUX_VERSION_mpc8315e-rdb = "4.18.25"
> +LINUX_VERSION_genericx86 = "4.18.35"
> +LINUX_VERSION_genericx86-64 = "4.18.35"
> +LINUX_VERSION_edgerouter = "4.18.35"
> +LINUX_VERSION_beaglebone-yocto = "4.18.35"
> +LINUX_VERSION_mpc8315e-rdb = "4.18.35"
> -- 
> 2.14.4
> 


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

[yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

2019-05-09 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao 
---
 .../recipes-kernel/linux/linux-yocto_4.19.bbappend   | 20 ++--
 .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 ++--
 2 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
index 6025230c7306..ec269d905c4b 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.19.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
-SRCREV_machine_genericx86-64 ?= "11e0e616ed095bb8012e1b4a231254c9656a0193"
-SRCREV_machine_edgerouter ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
-SRCREV_machine_beaglebone-yocto ?= "eebb51300a07804a020ec468b5f8c5bf720198d9"
-SRCREV_machine_mpc8315e-rdb ?= "8b60f968823256f5d2889c4520d70299ca21411b"
+SRCREV_machine_genericx86?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_genericx86-64 ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_edgerouter ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_beaglebone-yocto ?= "5664dc14399edcaad210bbeb6343d84561fb3ea8"
+SRCREV_machine_mpc8315e-rdb ?= "d419f4ca6ba4b097b8ad710a93b89510f5b2998c"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.19.19"
-LINUX_VERSION_genericx86-64 = "4.19.19"
-LINUX_VERSION_edgerouter = "4.19.14"
-LINUX_VERSION_beaglebone-yocto = "4.19.14"
-LINUX_VERSION_mpc8315e-rdb = "4.19.14"
+LINUX_VERSION_genericx86 = "4.19.34"
+LINUX_VERSION_genericx86-64 = "4.19.34"
+LINUX_VERSION_edgerouter = "4.19.34"
+LINUX_VERSION_beaglebone-yocto = "4.19.34"
+LINUX_VERSION_mpc8315e-rdb = "4.19.34"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
index 5cf6e1f0649e..d7cf1216f45d 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_beaglebone-yocto ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
-SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
+SRCREV_machine_genericx86?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_genericx86-64 ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_edgerouter ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_beaglebone-yocto ?= "f990fd0ce123aa6035042efad09b2ddc3e7d48f4"
+SRCREV_machine_mpc8315e-rdb ?= "670ce7e9db627d0c2067cfdb571ddc1f117818d8"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "5.0.3"
-LINUX_VERSION_genericx86-64 = "5.0.3"
-LINUX_VERSION_edgerouter = "5.0.3"
-LINUX_VERSION_beaglebone-yocto = "5.0.3"
-LINUX_VERSION_mpc8315e-rdb = "5.0.3"
+LINUX_VERSION_genericx86 = "5.0.13"
+LINUX_VERSION_genericx86-64 = "5.0.13"
+LINUX_VERSION_edgerouter = "5.0.13"
+LINUX_VERSION_beaglebone-yocto = "5.0.13"
+LINUX_VERSION_mpc8315e-rdb = "5.0.13"
-- 
2.14.4

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

[yocto] [PATCH][thud] meta-yocto-bsp: Bump to the latest stable kernel for the BSPs

2019-04-18 Thread Kevin Hao 
In order to fix a systemtap bug [1] on arm board, we backport a kernel
patch from v5.0 kernel to v4.14 & v4.18 kernel, then need to bump the
kernel version to include this patch. Even this is only an arm specific
bug, we would like to bump the kernel version for the BSPs at the same
time. Boot test for all the boards.

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273

Signed-off-by: Kevin Hao 
---
 .../recipes-kernel/linux/linux-yocto_4.14.bbappend   | 20 ++--
 .../recipes-kernel/linux/linux-yocto_4.18.bbappend   | 20 ++--
 2 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
index 502485a94b15..426757e48c9e 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
-SRCREV_machine_genericx86-64 ?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
-SRCREV_machine_edgerouter ?= "e06bfa18c727bd0e6e10cf26d9f161e4c791f52b"
-SRCREV_machine_beaglebone-yocto ?= "b8805de77dcf8f59d8368fee4921c146c1300a6a"
-SRCREV_machine_mpc8315e-rdb ?= "f88e87360b10f8fbd853a7d412982e6620f3f96d"
+SRCREV_machine_genericx86?= "5252513a39b4b3773debab1f77071d7c430ecb10"
+SRCREV_machine_genericx86-64 ?= "5252513a39b4b3773debab1f77071d7c430ecb10"
+SRCREV_machine_edgerouter ?= "d8fb40cd0e99325715c70aed6f361a8318097829"
+SRCREV_machine_beaglebone-yocto ?= "c67809688bd22cb4cb909bcf1a1045e6337c3229"
+SRCREV_machine_mpc8315e-rdb ?= "258ee8228e0a512c6dbe2a0dadcd9f030ba45964"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.14.76"
-LINUX_VERSION_genericx86-64 = "4.14.76"
-LINUX_VERSION_edgerouter = "4.14.71"
-LINUX_VERSION_beaglebone-yocto = "4.14.71"
-LINUX_VERSION_mpc8315e-rdb = "4.14.71"
+LINUX_VERSION_genericx86 = "4.14.98"
+LINUX_VERSION_genericx86-64 = "4.14.98"
+LINUX_VERSION_edgerouter = "4.14.98"
+LINUX_VERSION_beaglebone-yocto = "4.14.98"
+LINUX_VERSION_mpc8315e-rdb = "4.14.98"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
index 7f15843f3a90..11b35cc1c2f8 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "db2d813869a0501782469ecdb17e277a501c9f57"
-SRCREV_machine_genericx86-64 ?= "db2d813869a0501782469ecdb17e277a501c9f57"
-SRCREV_machine_edgerouter ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
-SRCREV_machine_beaglebone-yocto ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
-SRCREV_machine_mpc8315e-rdb ?= "99071a599d8650b069fb8135866fca203f375350"
+SRCREV_machine_genericx86?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_genericx86-64 ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_edgerouter ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_beaglebone-yocto ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_mpc8315e-rdb ?= "0802dc980cbc8bdb156d6fe305e7b88e6b602634"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.18.22"
-LINUX_VERSION_genericx86-64 = "4.18.22"
-LINUX_VERSION_edgerouter = "4.18.25"
-LINUX_VERSION_beaglebone-yocto = "4.18.25"
-LINUX_VERSION_mpc8315e-rdb = "4.18.25"
+LINUX_VERSION_genericx86 = "4.18.35"
+LINUX_VERSION_genericx86-64 = "4.18.35"
+LINUX_VERSION_edgerouter = "4.18.35"
+LINUX_VERSION_beaglebone-yocto = "4.18.35"
+LINUX_VERSION_mpc8315e-rdb = "4.18.35"
-- 
2.14.4

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

[linux-yocto] [linux-yocto v4.14] arm/Makefile: Fix systemtap

2019-04-15 Thread Kevin Hao 
From: Richard Purdie 

Currently systemtap fails to operate correctly on armv7 systems such as 
beaglebone and
soon, qemuarm.

root@qemuarm:/usr/src/kernel# env -uARCH -uKBUILD_EXTMOD -uCROSS_COMPILE 
-uKBUILD_IMAGE -uKCONFIG_CONFIG -uINSTALL_PATH -uLD_LIBRARY_PATH 
PATH=/usr/bin:/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin 
make -C /lib/modules/4.19.19-yocto-standard/build M=/tmp/staptcNU6M modules 
CONFIG_DEBUG_INFO= CONFIG_STACK_VALIDATION= ARCH=arm stap_4321_src.i 
--no-print-directory -j2 V=1
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
mkdir -p /tmp/staptcNU6M/.tmp_versions ; rm -f /tmp/staptcNU6M/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/staptcNU6M
(cat /dev/null;   echo kernel//tmp/staptcNU6M/stap_4321.ko;) > 
/tmp/staptcNU6M/modules.order
  gcc -Wp,-MD,/tmp/staptcNU6M/.stap_4321_src.o.d  -nostdinc -isystem 
/usr/lib/gcc/arm-poky-linux-gnueabi/8.3.0/include -I./arch/arm/include 
-I./arch/arm/include/generated  -I./include -I./arch/arm/include/uapi 
-I./arch/arm/include/generated/uapi -I./include/uapi -I./include/generated/uapi 
-include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h 
-D__KERNEL__ -mlittle-endian -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar 
-Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE 
-DCC_HAVE_ASM_GOTO -fno-dwarf2-cfi-asm -fno-omit-frame-pointer -mapcs 
-mno-sched-prolog -fno-ipa-sra -mabi=aapcs-linux -mfpu=vfp -funwind-tables 
-marm -Wa,-mno-warn-deprecated -D__LINUX_ARM_ARCH__=7 -march=armv5t 
-Wa,-march=armv7-a -msoft-float -Uarm -fno-delete-null-pointer-checks 
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow 
-Wno-int-in-bool-context -Os -Wno-maybe-uninitialized --param=allow-store
 -data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong 
-Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer 
-fno-optimize-sibling-calls -fno-var-tracking-assignments -pg 
-Wdeclaration-after-statement -Wno-pointer-sign -Wno-stringop-truncation 
-fno-strict-overflow -fno-merge-all-constants -fmerge-constants 
-fno-stack-check -fconserve-stack -Werror=implicit-int 
-Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types 
-Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned 
-Iinclude2/asm/mach-default -I/lib/modules/4.19.19-yocto-standard/build 
-include /tmp/staptcNU6M/stapconf_4321.h -D "STP_NO_VELREL_CHECK" 
-freorder-blocks -fasynchronous-unwind-tables -Wframe-larger-than=512 
-fno-ipa-icf -Wno-unused -Wno-tautological-compare -Werror 
-I/usr/share/systemtap/runtime  -DMODULE  -DKBUILD_BASENAME='"stap_4321_src"' 
-DKBUILD_MODNAME='"stap_4321"' -c -o /tmp/staptcNU6M/stap_4321_src.o 
/tmp/staptcNU6M/stap_4321_s
 rc.c
/tmp/ccaE9CMG.s: Assembler messages:
/tmp/ccaE9CMG.s:49: Error: selected processor does not support `dmb ish' in ARM 
mode
/tmp/ccaE9CMG.s:52: Error: architectural extension `mp' is not allowed for the 
current b

(which was from running the stap command with -v -v -v -k and then being able 
to run the command individually)

Note that it says armv5t above.

That comes from the code this patch changes

root@qemuarm:/usr/src/kernel# gcc -march=armv7-a 
/tmp/staptcNU6M/stap_4321_aux_0.c
cc1: error: -mfloat-abi=hard: selected processor lacks an FPU

which makes me wonder if cc-option fails unless -mfpu-vfp is on the commandline 
too.

Since we have a gcc which accepts the armv7-a arch, just remove the cc-option
wrapper unconditionally here.

Signed-off-by: Richard Purdie 
Signed-off-by: Bruce Ashfield 
---
Backport a kernel patch from v5.0 to v4.14 kernel in order to fix
the same issue on Yocto 2.6.

 arch/arm/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index 1f95ede8063f..9253b7533cb1 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -64,7 +64,7 @@ KBUILD_CFLAGS += $(call cc-option,-fno-ipa-sra)
 # macro, but instead defines a whole series of macros which makes
 # testing for a specific architecture or later rather impossible.
 arch-$(CONFIG_CPU_32v7M)   =-D__LINUX_ARM_ARCH__=7 -march=armv7-m 
-Wa,-march=armv7-m
-arch-$(CONFIG_CPU_32v7)=-D__LINUX_ARM_ARCH__=7 $(call 
cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
+arch-$(CONFIG_CPU_32v7)=-D__LINUX_ARM_ARCH__=7 -march=armv7-a 
-Wa$(comma)-march=armv7-a
 arch-$(CONFIG_CPU_32v6)=-D__LINUX_ARM_ARCH__=6 $(call

[linux-yocto] [kernel-meta v4.19 PATCH] mips: Enable the poweroff driver for the qemumips/qemumips64

2019-04-03 Thread Kevin Hao 
As Indicated by Richard Purdie, in order to shutdown the machine we have
to explicitly enable the PIIX4 poweroff driver for the
qemumips/qemumips64 after the kernel commit dd129c6374e9 ("MIPS: Malta:
Use PIIX4 poweroff driver to power down") is merged.

Signed-off-by: Kevin Hao 
---
 bsp/mti-malta32/mti-malta32-common.cfg | 3 +++
 bsp/mti-malta64/mti-malta64-common.cfg | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/bsp/mti-malta32/mti-malta32-common.cfg 
b/bsp/mti-malta32/mti-malta32-common.cfg
index d30a38d0f89f..51b9bdc46586 100644
--- a/bsp/mti-malta32/mti-malta32-common.cfg
+++ b/bsp/mti-malta32/mti-malta32-common.cfg
@@ -73,3 +73,6 @@ CONFIG_SERIO=y
 CONFIG_USB_MON=y
 CONFIG_USB_OHCI_HCD=y
 
+# Board reset
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_PIIX4_POWEROFF=y
diff --git a/bsp/mti-malta64/mti-malta64-common.cfg 
b/bsp/mti-malta64/mti-malta64-common.cfg
index a6c1202c5b13..c178fd07a127 100644
--- a/bsp/mti-malta64/mti-malta64-common.cfg
+++ b/bsp/mti-malta64/mti-malta64-common.cfg
@@ -79,3 +79,6 @@ CONFIG_USB_OHCI_HCD=y
 
 # CONFIG_VGA_CONSOLE is not set
 
+# Board reset
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_PIIX4_POWEROFF=y
-- 
2.14.4

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

[yocto] [PATCH 1/2] meta-yocto-bsp: Bump to the latest stable kernel for all the BSPs

2019-04-02 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao 
---
 .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 ++--
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
index fe52a06550d2..5cf6e1f0649e 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86?= "1a0da7e50b77c82841efb501c648dbaca699eac2"
-SRCREV_machine_genericx86-64 ?= "1a0da7e50b77c82841efb501c648dbaca699eac2"
-SRCREV_machine_edgerouter ?= "1a0da7e50b77c82841efb501c648dbaca699eac2"
-SRCREV_machine_beaglebone-yocto ?= "1a0da7e50b77c82841efb501c648dbaca699eac2"
-SRCREV_machine_mpc8315e-rdb ?= "21aae3b4437eb6eec18804f1bad692030352430c"
+SRCREV_machine_genericx86?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
+SRCREV_machine_genericx86-64 ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
+SRCREV_machine_edgerouter ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
+SRCREV_machine_beaglebone-yocto ?= "3df4aae6074e94e794e27fe7f17451d9353cdf3d"
+SRCREV_machine_mpc8315e-rdb ?= "8b62af7f252af10588276802c4c6d7c502e875be"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "5.0"
-LINUX_VERSION_genericx86-64 = "5.0"
-LINUX_VERSION_edgerouter = "5.0"
-LINUX_VERSION_beaglebone-yocto = "5.0"
-LINUX_VERSION_mpc8315e-rdb = "5.0"
+LINUX_VERSION_genericx86 = "5.0.3"
+LINUX_VERSION_genericx86-64 = "5.0.3"
+LINUX_VERSION_edgerouter = "5.0.3"
+LINUX_VERSION_beaglebone-yocto = "5.0.3"
+LINUX_VERSION_mpc8315e-rdb = "5.0.3"
-- 
2.14.4

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

[yocto] [PATCH 2/2] meta-yocto-bsp: beaglebone: Enable the serial console for the WIC image

2019-04-02 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
---
 meta-yocto-bsp/wic/beaglebone-yocto.wks | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-yocto-bsp/wic/beaglebone-yocto.wks 
b/meta-yocto-bsp/wic/beaglebone-yocto.wks
index b75f238df937..97bd480a0875 100644
--- a/meta-yocto-bsp/wic/beaglebone-yocto.wks
+++ b/meta-yocto-bsp/wic/beaglebone-yocto.wks
@@ -4,3 +4,4 @@
 
 part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label 
boot --active --align 4 --size 16 --sourceparams="loader=u-boot" --use-uuid
 part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 
--use-uuid
+bootloader --append="console=ttyS0,115200"
-- 
2.14.4

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

[linux-yocto] [v4.19 rt branch] x86: Drop the duplicate define of TIF_NEED_RESCHED_LAZY

2019-03-28 Thread Kevin Hao 
The two merge commits 107b161b1cbaf ("Merge branch 'v4.19/standard/base'
into v4.19/standard/preempt-rt/base") and dc37b7080cd55 ("Merge tag
'v4.19.8' into linux-4.19.y-rt") almost have the same content, but
introduce two define of TIF_NEED_RESCHED_LAZY for x86 arch. Drop one of
them to fix the build warning.

Signed-off-by: Kevin Hao 
---
 arch/x86/include/asm/thread_info.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/arch/x86/include/asm/thread_info.h 
b/arch/x86/include/asm/thread_info.h
index 70b08abcd6d0..dc267291f131 100644
--- a/arch/x86/include/asm/thread_info.h
+++ b/arch/x86/include/asm/thread_info.h
@@ -95,7 +95,6 @@ struct thread_info {
 #define TIF_USER_RETURN_NOTIFY 11  /* notify kernel of userspace return */
 #define TIF_UPROBE 12  /* breakpointed or singlestepping */
 #define TIF_PATCH_PENDING  13  /* pending live patching update */
-#define TIF_NEED_RESCHED_LAZY  14  /* lazy rescheduling necessary */
 #define TIF_NOCPUID15  /* CPUID is not accessible in userland 
*/
 #define TIF_NOTSC  16  /* TSC is not accessible in userland */
 #define TIF_IA32   17  /* IA32 compatibility process */
@@ -126,7 +125,6 @@ struct thread_info {
 #define _TIF_USER_RETURN_NOTIFY(1 << TIF_USER_RETURN_NOTIFY)
 #define _TIF_UPROBE(1 << TIF_UPROBE)
 #define _TIF_PATCH_PENDING (1 << TIF_PATCH_PENDING)
-#define _TIF_NEED_RESCHED_LAZY (1 << TIF_NEED_RESCHED_LAZY)
 #define _TIF_NOCPUID   (1 << TIF_NOCPUID)
 #define _TIF_NOTSC (1 << TIF_NOTSC)
 #define _TIF_IA32  (1 << TIF_IA32)
-- 
2.14.4

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

[linux-yocto] [PATCH 2/3] beaglebone: Update the audio options

2019-03-06 Thread Kevin Hao 
With the commit f2055e145f29 ("ASoC: ti: Merge davinci and omap
directories"), some of the audio options are removed from the kernel.
Use the new options for the audio support.

Signed-off-by: Kevin Hao 
---
 bsp/beaglebone/beaglebone.cfg | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index 9acc07a68872..450f503ddf62 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -225,10 +225,9 @@ CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
 CONFIG_SOUND=m
 CONFIG_SND=m
 CONFIG_SND_SOC=m
-CONFIG_SND_OMAP_SOC=m
-CONFIG_SND_OMAP_SOC_MCBSP=m
-CONFIG_SND_OMAP_SOC_OMAP_TWL4030=m
-CONFIG_SND_SOC_TWL4030=m
+CONFIG_SND_SOC_OMAP3_TWL4030=m
+CONFIG_SND_SOC_DAVINCI_MCASP=m
+CONFIG_SND_SIMPLE_CARD=m
 
 #
 # I2C HID support
-- 
2.14.4

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

[linux-yocto] [PATCH 3/3] beaglebone: Switch to the 8250 omap driver

2019-03-06 Thread Kevin Hao 
In the v5.0 kernel, the SERIAL_OMAP driver doesn't work anymore.
So switch to the 8250 omap driver for the serial support.

Signed-off-by: Kevin Hao 
---
 bsp/beaglebone/beaglebone.cfg | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index 450f503ddf62..f044061032b9 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -116,10 +116,12 @@ CONFIG_INPUT_MISC=y
 CONFIG_INPUT_TWL4030_PWRBUTTON=y
 
 #
-# Non-8250 serial port support
+# 8250 serial port support
 #
-CONFIG_SERIAL_OMAP=y
-CONFIG_SERIAL_OMAP_CONSOLE=y
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_OMAP=y
+CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y
 CONFIG_I2C_CHARDEV=y
 CONFIG_I2C=y
 
-- 
2.14.4

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

[linux-yocto] [PATCH 1/3] mpc8315e-rdb: Enable the CONFIG_MTD_PHYSMAP

2019-03-06 Thread Kevin Hao 
This is needed by the CONFIG_MTD_PHYSMAP_OF.

Signed-off-by: Kevin Hao 
---
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg 
b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
index 57ebaabb6583..cb7c40d37c22 100644
--- a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
+++ b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
@@ -51,6 +51,7 @@ CONFIG_MTD_CFI_AMDSTD=y
 #
 # Mapping drivers for chip access
 #
+CONFIG_MTD_PHYSMAP=y
 CONFIG_MTD_PHYSMAP_OF=y
 
 #
-- 
2.14.4

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

[linux-yocto] [PATCH 0/3] [kernel-cache] [yocto-5.0] Enable the v5.0 kernel support for the reference BSPs

2019-03-06 Thread Kevin Hao 
Hi,

- Fix the kernel config check warnings for the new kernel.
- Fix the serial malfunction on the beaglebone board.


Kevin Hao (3):
  mpc8315e-rdb: Enable the CONFIG_MTD_PHYSMAP
  beaglebone: Update the audio options
  beaglebone: Switch to the 8250 omap driver

 bsp/beaglebone/beaglebone.cfg | 15 ---
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg |  1 +
 2 files changed, 9 insertions(+), 7 deletions(-)

-- 
2.14.4

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

[yocto] [PATCH] meta-yocto-bsp: Disable the glamor acceleration for the beaglebone

2019-02-28 Thread Kevin Hao 
In the commit ec6d61cbddc3 ("mesa: enable native and nativesdk
variants"), the gallium is enabled for the mesa. Since we use the
modesetting driver for the Xorg on the beagleboard and the glamor
acceleration method is enabled by the modesetting driver, the gallium
DRI driver will be used after this commit. But the gallium DRI driver
only support 32bpp and we choose to use 16bpp on beaglebone in commit
e7434c17b4b3 ("meta-yocto-bsp: workaround the X malfunction on
beaglebone"), the mismatch between them causes the malfunction of the
Xorg. I have hacked the kernel to enable the 32bpp for the beagllebone,
but it has the following issues:
  1. The color is abnormal.
  2. The Xorg hang occasionally.
  3. The performance of using glamor acceleration based on gallium is
 pretty bad.
So I choose to disable the glamor on this board.

Signed-off-by: Kevin Hao 
---
 .../xorg-xserver/xserver-xf86-config/beaglebone-yocto/xorg.conf  | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/meta-yocto-bsp/recipes-graphics/xorg-xserver/xserver-xf86-config/beaglebone-yocto/xorg.conf
 
b/meta-yocto-bsp/recipes-graphics/xorg-xserver/xserver-xf86-config/beaglebone-yocto/xorg.conf
index 2f40dae15710..5da15888d44b 100644
--- 
a/meta-yocto-bsp/recipes-graphics/xorg-xserver/xserver-xf86-config/beaglebone-yocto/xorg.conf
+++ 
b/meta-yocto-bsp/recipes-graphics/xorg-xserver/xserver-xf86-config/beaglebone-yocto/xorg.conf
@@ -5,6 +5,7 @@ EndSection
 Section "Device"
 Identifier  "Builtin Default fbdev Device 0"
 Driver  "modesetting"
+Option  "AccelMethod" "none"
 EndSection
 
 Section "Screen"
-- 
2.14.4

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

Re: [yocto] wic utility

2019-01-23 Thread Kevin Hao 
On Wed, Jan 23, 2019 at 04:39:07PM +, Srinivasan, Raja wrote:
> I am using wic 0.2.0 from the rocko build.
> 
>  
> 
> wic cp file wifile:part/path
> 
>  
> 
> appears to succeed (no errors reported).
> 
>  
> 
> But when I perform wic ls I don’t find the file in the target.
> 
>  
> 
> Are there any switches the I should be using?

It seems that it works fine on the master branch.
$ wic ls 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2
debugfs 1.43.5 (04-Aug-2017)
  2   40755 (2)  0  04096 23-Jan-2019 14:04 .
  2   40755 (2)  0  04096 23-Jan-2019 14:04 ..
 11   40700 (2)  0  0   16384 23-Jan-2019 14:04 lost+found
 12   40755 (2)  0  04096 23-Jan-2019 13:56 lib
456   40755 (2)  0  04096 23-Jan-2019 13:43 dev
457   40555 (2)  0  04096 23-Jan-2019 13:43 proc
458   40755 (2)  0  04096 23-Jan-2019 13:43 media
459   40755 (2)  0  04096 23-Jan-2019 14:04 boot
465   40755 (2)  0  04096 23-Jan-2019 14:03 mnt
467   40755 (2)  0  04096 23-Jan-2019 13:57 usr
   9582   40755 (2)  0  04096 23-Jan-2019 13:56 var
   9639   40555 (2)  0  04096 23-Jan-2019 13:43 sys
   9640   40755 (2)  0  04096 23-Jan-2019 14:04 etc
  10373   40755 (2)  0  04096 23-Jan-2019 14:03 sbin
  10437   40755 (2)  0  04096 23-Jan-2019 13:43 run
  10438   41777 (2)  0  04096 23-Jan-2019 13:43 tmp
  10439   40755 (2)  0  04096 23-Jan-2019 14:03 home
  10441   40755 (2)  0  04096 23-Jan-2019 14:03 bin
$ wic cp a.txt 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2
$ wic ls 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2
debugfs 1.43.5 (04-Aug-2017)
  2   40755 (2)  0  04096 23-Jan-2019 14:04 .
  2   40755 (2)  0  04096 23-Jan-2019 14:04 ..
 11   40700 (2)  0  0   16384 23-Jan-2019 14:04 lost+found
 12   40755 (2)  0  04096 23-Jan-2019 13:56 lib
456   40755 (2)  0  04096 23-Jan-2019 13:43 dev
457   40555 (2)  0  04096 23-Jan-2019 13:43 proc
458   40755 (2)  0  04096 23-Jan-2019 13:43 media
459   40755 (2)  0  04096 23-Jan-2019 14:04 boot
465   40755 (2)  0  04096 23-Jan-2019 14:03 mnt
467   40755 (2)  0  04096 23-Jan-2019 13:57 usr
   9582   40755 (2)  0  04096 23-Jan-2019 13:56 var
   9639   40555 (2)  0  04096 23-Jan-2019 13:43 sys
   9640   40755 (2)  0  04096 23-Jan-2019 14:04 etc
  10373   40755 (2)  0  04096 23-Jan-2019 14:03 sbin
  10437   40755 (2)  0  04096 23-Jan-2019 13:43 run
  10438   41777 (2)  0  04096 23-Jan-2019 13:43 tmp
  10439   40755 (2)  0  04096 23-Jan-2019 14:03 home
  10441   40755 (2)  0  04096 23-Jan-2019 14:03 bin
  10514  100644 (1)  0  0   4 24-Jan-2019 14:23 a.txt

There should be no change for the Disk.copy() function between rocko and master
branch. Anyway could you have a try on the latest master branch?

Thanks,
Kevin

> 
>  
> 
> Thanks for any pointers, srini
> 
> 
> ━━━
> 
> CONFIDENTIALITY NOTICE: This email message and any attachments are 
> confidential
> and may be privileged and are meant to be read by the intended recipient only.
> If you are not the intended recipient, please notify sender immediately and
> destroy all copies of this message and any attachments without reading or
> disclosing their contents. Thank you
> 
> 
> 

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



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

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-11-07 Thread Kevin Hao 
On Wed, Nov 07, 2018 at 08:33:51AM +0100, Heiko Schocher wrote:
> Hello Kevin, Robert,
> 
> Am 06.11.2018 um 09:10 schrieb Heiko Schocher:
> > Hello Kevin, Robert,
> > 
> > Am 05.11.2018 um 06:26 schrieb Kevin Hao:
> > > On Sun, Nov 04, 2018 at 12:10:00PM +0200, Robert Berger wrote:
> > > > Hi,
> > > > 
> > > > On 02.11.18 16:27, Khem Raj wrote:
> > > > > 
> > > > > omap serial is obsolete why does linux-yocto keeps using it.
> > > > > seondly, machine config should enable both consoles ttyO0 and ttyS0 if
> > > > > you know that at least one kernel is using ttyO0
> > > > > 
> > > > How about picking whatever works for you in the kernel conf and in 
> > > > machine
> > > > conf?
> > > > 
> > > > SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
> > > > SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
> > > > 
> > > > Like this on the first boot either ttyO0 or ttyS0 should be picked
> > > > automatically.
> > > 
> > > Yes, this is doable. Would you mind send a patch?
> > 
> > Sorry for answering so late... good hint, I missed SERIAL_CONSOLES_CHECK
> > 
> > I try this change and report, give me some time...
> 
> 
> diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> index e911e75004..def3a2ae06 100644
> --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> @@ -20,7 +20,8 @@ WKS_FILE ?= "beaglebone-yocto.wks"
>  IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
>  do_image_wic[depends] += "mtools-native:do_populate_sysroot 
> dosfstools-native:do_populate_sysroot"
> 
> -SERIAL_CONSOLES = "115200;ttyO0"
> +SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
> +SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
> 
>  PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>  PREFERRED_VERSION_linux-yocto ?= "4.18%"
> 
> and on my beagleboneblack linux kernels with 8250 serial driver enabled
> (console ttyS0) and kernel omap_serial driver enabled (console ttyO0)
> are booting.
> 
> Unfortunately it took me some time, until I realized that my settings
> in auto.conf do not work, because in beaglebone-yocto.conf
> 
> SERIAL_CONSOLES = "115200;ttyO0"
> 
> is set ... May a
> 
> SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0"
> 
> is friendlier ?

Yes, "?=" is better.

> 
> Should I send a formal patch?

Yes, please.

Thanks,
Kevin

> 
> bye,
> Heiko
> -- 
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de


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

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-11-04 Thread Kevin Hao 
On Sun, Nov 04, 2018 at 12:10:00PM +0200, Robert Berger wrote:
> Hi,
> 
> On 02.11.18 16:27, Khem Raj wrote:
> > 
> > omap serial is obsolete why does linux-yocto keeps using it.
> > seondly, machine config should enable both consoles ttyO0 and ttyS0 if
> > you know that at least one kernel is using ttyO0
> > 
> How about picking whatever works for you in the kernel conf and in machine
> conf?
> 
> SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
> SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
> 
> Like this on the first boot either ttyO0 or ttyS0 should be picked
> automatically.

Yes, this is doable. Would you mind send a patch?

Thanks,
Kevin

> 
> Regards,
> Robert


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

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-11-03 Thread Kevin Hao 
On Sat, Nov 03, 2018 at 07:38:02AM -0700, Khem Raj wrote:
> On Sat, Nov 3, 2018 at 1:38 AM Kevin Hao  wrote:
> >
> > On Fri, Nov 02, 2018 at 07:27:04AM -0700, Khem Raj wrote:
> > > On Fri, Nov 2, 2018 at 2:02 AM Kevin Hao  wrote:
> > > >
> > > > On Fri, Nov 02, 2018 at 09:01:34AM +0100, Heiko Schocher wrote:
> > > > > Hello Kevin,
> > > > >
> > > > > Am 01.11.2018 um 03:18 schrieb Kevin Hao:
> > > > > > On Wed, Oct 31, 2018 at 02:23:00PM +0100, Heiko Schocher wrote:
> > > > > > > Hello all,
> > > > > > >
> > > > > > > just builded core-image-minimal with current head of thud branch 
> > > > > > > for
> > > > > > > the beaglebone-yocto machine, with linux 4.14.x LTS "Linux 
> > > > > > > version 4.14.78",
> > > > > > > installed the resulting sd card image and boot it, and get:
> > > > > > >
> > > > > > > INIT: Id "O0" respawning too fast: disabled for
> > > > > > > 5 minutes
> > > > > > >
> > > > > > > Reason seems to be:
> > > > > > >
> > > > > > > meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> > > > > > >
> > > > > > > SERIAL_CONSOLES = "115200;ttyO0"
> > > > > > >
> > > > > > > shouldn't this be
> > > > > > >
> > > > > > > SERIAL_CONSOLES = "115200;ttyS0"
> > > > > > >
> > > > > > > With this fix, sd card image boot fine ... may I oversee seomthing
> > > > > > > obvious ?
> > > > > >
> > > > > > No, it should be 'ttyO0'. It is set by the omap serial driver. You 
> > > > > > can
> > > > > > refer the following in platform_data/serial-omap.h:
> > > > > >#define OMAP_SERIAL_NAME"ttyO"
> > > > >
> > > > > Yes, you are right, but I see with linux kernel 4.14.78 from
> > > > >
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.14.y=e7405910ca5553eae8744af4e5c03e64ee048cb1
> > > > >
> > > > > and I see:
> > > > >
> > > > > [0.00] Linux version 4.14.78 (oe-user@oe-host) (gcc version 
> > > > > 8.2.0
> > > > > (GCC)) #1 Thu Nov 1 10:51:09 UTC 2018
> > > > > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
> > > > > cr=10c5387d
> > > > > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> > > > > instruction cache
> > > > > [0.00] OF: fdt: Machine model: TI AM335x BeagleBone Black
> > > > > [...]
> > > > > [0.362878] Serial: 8250/16550 driver, 6 ports, IRQ sharing 
> > > > > disabled
> > > > > [0.365758] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, 
> > > > > base_baud = 300) is a 8250
> > > > > [1.030465] console [ttyS0] enabled
> > > > >
> > > > > So definitely a ttyS0 ...
> > > >
> > > > OK, so you don't use the linux-yocto kernel, you must not use the Yocto 
> > > > kernel
> > > > meta either.
> > >
> > > I dont think there is such a rule.
> >
> > I don't get what you mean about such a rule. I didn't say anything about 
> > that.
> 
> re-read carefully what you wrote above and hopefully you will understand

I definitely know what I mean. I just don't understand what you are talking 
about.

> 
> 
> > I just pointed out why Heiko get stuck by that issue and how to workaround 
> > it.
> >
> > > meta-yocto-bsps are meant as
> > > references and people might want to enhance them.
> >
> > Of course, that is also why we are continually working on it.
> >
> 
> your answer did not indicate that.

I apologize if I gave the expression that I don't welcome the enhancement to 
the meta-yocto-bsp.
But maybe you are the only one who get that from what I wrote.

> 
> > >
> > >  The reason that you got a ttyS0 here is that you use the
> > > > 8250_omap.c driver. But in Yocto we use the omap-serial.c driver. You 
> > > > can
> > > > workaround this issue by enabling SERIAL_8250_OMAP_TTYO_FIXUP.
> >

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-11-03 Thread Kevin Hao 
On Fri, Nov 02, 2018 at 07:27:04AM -0700, Khem Raj wrote:
> On Fri, Nov 2, 2018 at 2:02 AM Kevin Hao  wrote:
> >
> > On Fri, Nov 02, 2018 at 09:01:34AM +0100, Heiko Schocher wrote:
> > > Hello Kevin,
> > >
> > > Am 01.11.2018 um 03:18 schrieb Kevin Hao:
> > > > On Wed, Oct 31, 2018 at 02:23:00PM +0100, Heiko Schocher wrote:
> > > > > Hello all,
> > > > >
> > > > > just builded core-image-minimal with current head of thud branch for
> > > > > the beaglebone-yocto machine, with linux 4.14.x LTS "Linux version 
> > > > > 4.14.78",
> > > > > installed the resulting sd card image and boot it, and get:
> > > > >
> > > > > INIT: Id "O0" respawning too fast: disabled for
> > > > > 5 minutes
> > > > >
> > > > > Reason seems to be:
> > > > >
> > > > > meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> > > > >
> > > > > SERIAL_CONSOLES = "115200;ttyO0"
> > > > >
> > > > > shouldn't this be
> > > > >
> > > > > SERIAL_CONSOLES = "115200;ttyS0"
> > > > >
> > > > > With this fix, sd card image boot fine ... may I oversee seomthing
> > > > > obvious ?
> > > >
> > > > No, it should be 'ttyO0'. It is set by the omap serial driver. You can
> > > > refer the following in platform_data/serial-omap.h:
> > > >#define OMAP_SERIAL_NAME"ttyO"
> > >
> > > Yes, you are right, but I see with linux kernel 4.14.78 from
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.14.y=e7405910ca5553eae8744af4e5c03e64ee048cb1
> > >
> > > and I see:
> > >
> > > [0.00] Linux version 4.14.78 (oe-user@oe-host) (gcc version 8.2.0
> > > (GCC)) #1 Thu Nov 1 10:51:09 UTC 2018
> > > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
> > > cr=10c5387d
> > > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> > > instruction cache
> > > [0.00] OF: fdt: Machine model: TI AM335x BeagleBone Black
> > > [...]
> > > [0.362878] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
> > > [0.365758] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, 
> > > base_baud = 300) is a 8250
> > > [1.030465] console [ttyS0] enabled
> > >
> > > So definitely a ttyS0 ...
> >
> > OK, so you don't use the linux-yocto kernel, you must not use the Yocto 
> > kernel
> > meta either.
> 
> I dont think there is such a rule.

I don't get what you mean about such a rule. I didn't say anything about that.
I just pointed out why Heiko get stuck by that issue and how to workaround it.

> meta-yocto-bsps are meant as
> references and people might want to enhance them.

Of course, that is also why we are continually working on it.

> 
>  The reason that you got a ttyS0 here is that you use the
> > 8250_omap.c driver. But in Yocto we use the omap-serial.c driver. You can
> > workaround this issue by enabling SERIAL_8250_OMAP_TTYO_FIXUP.
> >
> 
> omap serial is obsolete why does linux-yocto keeps using it.

I guess that the original reason that we use this should be something like the
comments in the omap-serial.c:
 * Note: This driver is made separate from 8250 driver as we cannot
 * over load 8250 driver with omap platform specific configuration for
 * features like DMA, it makes easier to implement features like DMA and
 * hardware flow control and software flow control configuration with
 * this driver as required for the omap-platform.

Yes, it has been a long time since the comments were written and even before the
birth of the 8250_omap.c. But I am just not sure that the 8250_omap driver
is mature enough so we can switch to it safely and we also don't get any serial
issue so far. That is why we leave it as is. And it also seem that the 
omap-serial.c
is also enabled by default in both the multi_v7_defconfig and 
omap2plus_defconfig
in the latest kernel:
  $ git grep "CONFIG_SERIAL_OMAP" arch/arm/
  arch/arm/configs/multi_v7_defconfig:CONFIG_SERIAL_OMAP=y
  arch/arm/configs/multi_v7_defconfig:CONFIG_SERIAL_OMAP_CONSOLE=y
  arch/arm/configs/omap2plus_defconfig:CONFIG_SERIAL_OMAP=y
  arch/arm/configs/omap2plus_defconfig:CONFIG_SERIAL_OMAP_CONSOLE=y

But if you are pretty sure that the 8250_omap.c is mature enough and also
provide more functions than omap-serial.c, please send a patch and we can
definitely switch

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-11-02 Thread Kevin Hao 
On Fri, Nov 02, 2018 at 09:01:34AM +0100, Heiko Schocher wrote:
> Hello Kevin,
> 
> Am 01.11.2018 um 03:18 schrieb Kevin Hao:
> > On Wed, Oct 31, 2018 at 02:23:00PM +0100, Heiko Schocher wrote:
> > > Hello all,
> > > 
> > > just builded core-image-minimal with current head of thud branch for
> > > the beaglebone-yocto machine, with linux 4.14.x LTS "Linux version 
> > > 4.14.78",
> > > installed the resulting sd card image and boot it, and get:
> > > 
> > > INIT: Id "O0" respawning too fast: disabled for
> > > 5 minutes
> > > 
> > > Reason seems to be:
> > > 
> > > meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> > > 
> > > SERIAL_CONSOLES = "115200;ttyO0"
> > > 
> > > shouldn't this be
> > > 
> > > SERIAL_CONSOLES = "115200;ttyS0"
> > > 
> > > With this fix, sd card image boot fine ... may I oversee seomthing
> > > obvious ?
> > 
> > No, it should be 'ttyO0'. It is set by the omap serial driver. You can
> > refer the following in platform_data/serial-omap.h:
> >#define OMAP_SERIAL_NAME"ttyO"
> 
> Yes, you are right, but I see with linux kernel 4.14.78 from
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.14.y=e7405910ca5553eae8744af4e5c03e64ee048cb1
> 
> and I see:
> 
> [0.00] Linux version 4.14.78 (oe-user@oe-host) (gcc version 8.2.0
> (GCC)) #1 Thu Nov 1 10:51:09 UTC 2018
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
> [0.00] OF: fdt: Machine model: TI AM335x BeagleBone Black
> [...]
> [0.362878] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
> [0.365758] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, base_baud 
> = 300) is a 8250
> [1.030465] console [ttyS0] enabled
> 
> So definitely a ttyS0 ...

OK, so you don't use the linux-yocto kernel, you must not use the Yocto kernel
meta either. The reason that you got a ttyS0 here is that you use the
8250_omap.c driver. But in Yocto we use the omap-serial.c driver. You can
workaround this issue by enabling SERIAL_8250_OMAP_TTYO_FIXUP.

Thanks,
Kevin

> 
> bye,
> Heiko
> > 
> > Thanks,
> > Kevin
> > 
> > > 
> > > bye,
> > > Heiko
> > > -- 
> > > DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> > > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> > > Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de
> > > -- 
> > > ___
> > > yocto mailing list
> > > yocto@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/yocto
> 
> -- 
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de


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

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

2018-10-31 Thread Kevin Hao 
On Wed, Oct 31, 2018 at 02:23:00PM +0100, Heiko Schocher wrote:
> Hello all,
> 
> just builded core-image-minimal with current head of thud branch for
> the beaglebone-yocto machine, with linux 4.14.x LTS "Linux version 4.14.78",
> installed the resulting sd card image and boot it, and get:
> 
> INIT: Id "O0" respawning too fast: disabled for
> 5 minutes
> 
> Reason seems to be:
> 
> meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> 
> SERIAL_CONSOLES = "115200;ttyO0"
> 
> shouldn't this be
> 
> SERIAL_CONSOLES = "115200;ttyS0"
> 
> With this fix, sd card image boot fine ... may I oversee seomthing
> obvious ?

No, it should be 'ttyO0'. It is set by the omap serial driver. You can
refer the following in platform_data/serial-omap.h:
  #define OMAP_SERIAL_NAME"ttyO"

Thanks,
Kevin

> 
> bye,
> Heiko
> -- 
> DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

[yocto] [layerindex-web] update: Parse the layer's compatible version info

2018-10-17 Thread Kevin Hao 
We have already set the layer's compatible version info in the
layer.conf, but we lack this info in the layerindex database.
Add support to parse this info and set it in the corresponding tables.
We plan to use this to filter the layerindex results.

Signed-off-by: Kevin Hao 
---
 layerindex/update.py   |  9 +
 layerindex/update_layer.py | 23 ++-
 2 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/layerindex/update.py b/layerindex/update.py
index 0b0f4804bba5..1610ae7989da 100755
--- a/layerindex/update.py
+++ b/layerindex/update.py
@@ -127,6 +127,13 @@ def extract_value(valuename, output):
 else:
 return ''
 
+def delete_dangling_ypcompatibleversion():
+from layerindex.models import LayerBranch, YPCompatibleVersion
+
+for ypcv in YPCompatibleVersion.objects.all():
+if not LayerBranch.objects.filter(yp_compatible_version=ypcv):
+ypcv.delete()
+
 def main():
 if LooseVersion(git.__version__) < '0.3.1':
 logger.error("Version of GitPython is too old, please install 
GitPython (python-git) 0.3.1 or later in order to use this script")
@@ -574,6 +581,8 @@ def main():
 update.save()
 
 if not options.dryrun:
+delete_dangling_ypcompatibleversion()
+
 # Purge old update records
 update_purge_days = getattr(settings, 'UPDATE_PURGE_DAYS', 30)
 
Update.objects.filter(started__lte=datetime.now()-timedelta(days=update_purge_days)).delete()
diff --git a/layerindex/update_layer.py b/layerindex/update_layer.py
index 42b618ff5944..9140ec4c2ed1 100644
--- a/layerindex/update_layer.py
+++ b/layerindex/update_layer.py
@@ -292,6 +292,26 @@ def update_distro_conf_file(path, distro, d):
 else:
 distro.description = desc
 
+def get_yp_compatible_version(layer_config_data):
+vers = utils.get_layer_var(layer_config_data, 'LAYERSERIES_COMPAT', logger)
+if not vers:
+return None;
+
+vers = vers.split()
+vers.sort()
+vers = ' '.join(vers)
+
+from layerindex.models import YPCompatibleVersion
+ypcv = YPCompatibleVersion.objects.filter(name=vers)
+if ypcv:
+ypcv = ypcv[0]
+else:
+ypcv = YPCompatibleVersion()
+ypcv.name = vers
+ypcv.save()
+
+return ypcv
+
 def main():
 if LooseVersion(git.__version__) < '0.3.1':
 logger.error("Version of GitPython is too old, please install 
GitPython (python-git) 0.3.1 or later in order to use this script")
@@ -347,7 +367,7 @@ def main():
 
 utils.setup_django()
 import settings
-from layerindex.models import LayerItem, LayerBranch, Recipe, 
RecipeFileDependency, Machine, Distro, BBAppend, BBClass
+from layerindex.models import LayerItem, LayerBranch, Recipe, 
RecipeFileDependency, Machine, Distro, BBAppend, BBClass, YPCompatibleVersion
 from django.db import transaction
 
 logger.setLevel(options.loglevel)
@@ -465,6 +485,7 @@ def main():
 logger.warn('Failed to find lib/oe/recipeutils.py in 
layers - patch information will not be collected')
 skip_patches = True
 
+layerbranch.yp_compatible_version = 
get_yp_compatible_version(layer_config_data)
 utils.add_dependencies(layerbranch, layer_config_data, 
logger=logger)
 utils.add_recommends(layerbranch, layer_config_data, 
logger=logger)
 layerbranch.save()
-- 
2.14.4

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

[yocto] [layerindex-web] Add YPCompatibleVersions to the api page

2018-10-11 Thread Kevin Hao 
We plan to use this compatible flag to filter the layer index results,
so add it to the api page first.

Signed-off-by: Kevin Hao 
---
 layerindex/restviews.py | 4 
 layerindex/urls.py  | 1 +
 2 files changed, 5 insertions(+)

diff --git a/layerindex/restviews.py b/layerindex/restviews.py
index 6e0bc75b848c..b0742798ef66 100644
--- a/layerindex/restviews.py
+++ b/layerindex/restviews.py
@@ -125,6 +125,10 @@ class 
YPCompatibleVersionSerializer(serializers.ModelSerializer):
 model = YPCompatibleVersion
 fields = '__all__'
 
+class YPCompatibleVersionViewSet(ParametricSearchableModelViewSet):
+queryset = YPCompatibleVersion.objects.all()
+serializer_class = YPCompatibleVersionSerializer
+
 class LayerSerializer(serializers.ModelSerializer):
 """
 A more fleshed-out LayerBranch serializer for external applications
diff --git a/layerindex/urls.py b/layerindex/urls.py
index 0593485a4f7a..f87ef3eabbd8 100644
--- a/layerindex/urls.py
+++ b/layerindex/urls.py
@@ -26,6 +26,7 @@ router.register(r'machines', restviews.MachineViewSet)
 router.register(r'distros', restviews.DistroViewSet)
 router.register(r'classes', restviews.ClassViewSet)
 router.register(r'layers', restviews.LayerViewSet, 'layers')
+router.register(r'YPCompatibleVersions', restviews.YPCompatibleVersionViewSet)
 
 urlpatterns = [
 url(r'^$',
-- 
2.14.4

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

[linux-yocto] [PATCH 1/3] beaglebone: Drop the obsolete kernel options

2018-09-25 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
Signed-off-by: Bruce Ashfield 
---
 bsp/beaglebone/beaglebone.cfg | 37 -
 1 file changed, 37 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index a712321297c2..ab42283c645f 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -13,28 +13,8 @@ CONFIG_OMAP_RESET_CLOCKS=y
 #
 # OMAP Board Type
 #
-# CONFIG_MACH_OMAP3_BEAGLE is not set
-# CONFIG_MACH_DEVKIT8000 is not set
-# CONFIG_MACH_OMAP_LDP is not set
-# CONFIG_MACH_OMAP3530_LV_SOM is not set
-# CONFIG_MACH_OMAP3_TORPEDO is not set
-# CONFIG_MACH_OVERO is not set
-# CONFIG_MACH_OMAP3EVM is not set
 # CONFIG_MACH_OMAP3517EVM is not set
-# CONFIG_MACH_CRANEBOARD is not set
 # CONFIG_MACH_OMAP3_PANDORA is not set
-# CONFIG_MACH_TOUCHBOOK is not set
-# CONFIG_MACH_OMAP_3430SDP is not set
-# CONFIG_MACH_NOKIA_RM680 is not set
-# CONFIG_MACH_NOKIA_RX51 is not set
-# CONFIG_MACH_OMAP_ZOOM2 is not set
-# CONFIG_MACH_OMAP_ZOOM3 is not set
-# CONFIG_MACH_CM_T35 is not set
-# CONFIG_MACH_CM_T3517 is not set
-# CONFIG_MACH_IGEP0020 is not set
-# CONFIG_MACH_IGEP0030 is not set
-# CONFIG_MACH_SBC3530 is not set
-# CONFIG_MACH_OMAP_3630SDP is not set
 
 #
 # Processor Features
@@ -220,7 +200,6 @@ CONFIG_DRM_I2C_NXP_TDA998X=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_OMAP=y
 # CONFIG_VGASTATE is not set
-# CONFIG_VIDEO_OUTPUT_CONTROL is not set
 # CONFIG_FIRMWARE_EDID is not set
 # CONFIG_FB_DDC is not set
 # CONFIG_FB_BOOT_VESA_SUPPORT is not set
@@ -241,29 +220,17 @@ CONFIG_FB_TILEBLITTING=y
 # CONFIG_FB_VIRTUAL is not set
 # CONFIG_FB_METRONOME is not set
 # CONFIG_FB_BROADSHEET is not set
-# CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
 # CONFIG_FB_DA8XX is not set
-# CONFIG_FB_DA8XX_TDA998X is not set
 CONFIG_OMAP2_DSS=y
 CONFIG_OMAP2_DSS_DPI=y
 CONFIG_OMAP2_DSS_VENC=y
 # CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
-# CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
 
 #
 # OMAP Display Device Drivers (new device model)
 #
-CONFIG_DISPLAY_ENCODER_TFP410=m
-CONFIG_DISPLAY_ENCODER_TPD12S015=m
-CONFIG_DISPLAY_PANEL_DPI=y
-CONFIG_DISPLAY_CONNECTOR_DVI=y
-CONFIG_DISPLAY_CONNECTOR_HDMI=y
-# CONFIG_DISPLAY_PANEL_SHARP_LS037V7DW01 is not set
-# CONFIG_DISPLAY_PANEL_LGPHILIPS_LB035Q02 is not set
-# CONFIG_DISPLAY_PANEL_TPO_TD043MTEA1 is not set
-CONFIG_DISPLAY_PANEL_TFCS9700=y
 CONFIG_BACKLIGHT_LCD_SUPPORT=y
 CONFIG_LCD_CLASS_DEVICE=y
 CONFIG_LCD_PLATFORM=y
@@ -319,7 +286,6 @@ CONFIG_NOP_USB_XCEIV=y
 CONFIG_AM335X_CONTROL_USB=y
 CONFIG_AM335X_PHY_USB=y
 CONFIG_USB_GADGET=y
-CONFIG_OMAP_CONTROL_USB=y
 
 #
 # USB Peripheral Controller
@@ -327,7 +293,6 @@ CONFIG_OMAP_CONTROL_USB=y
 CONFIG_USB_G_NCM=m
 CONFIG_USB_MASS_STORAGE=m
 CONFIG_MMC=y
-CONFIG_MMC_UNSAFE_RESUME=y
 
 #
 # MMC/SD/SDIO Card Drivers
@@ -377,7 +342,6 @@ CONFIG_TI_CPPI41=y
 # Hardware Spinlock drivers
 #
 CONFIG_ARM_ARCH_TIMER=y
-CONFIG_CLKSRC_OF=y
 
 #
 # Rpmsg drivers
@@ -388,7 +352,6 @@ CONFIG_EXTCON=y
 # Extcon Device Drivers
 #
 CONFIG_EXTCON_PALMAS=y
-CONFIG_OF_EXTCON=y
 
 #
 # PHY Subsystem
-- 
2.14.4

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

[linux-yocto] [PATCH 3/3] beaglebone: Clean up the cfg file

2018-09-25 Thread Kevin Hao 
In general we only need to enable the kernel options we really care and
leave all other kernel options as is. That is to say we don't need to
disable any kernel options explicitly. So drop all of them.

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

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index b60c0721a22f..9acc07a68872 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -10,12 +10,6 @@ CONFIG_OMAP_32K_TIMER=y
 CONFIG_OMAP_DM_TIMER=y
 CONFIG_OMAP_RESET_CLOCKS=y
 
-#
-# OMAP Board Type
-#
-# CONFIG_MACH_OMAP3517EVM is not set
-# CONFIG_MACH_OMAP3_PANDORA is not set
-
 #
 # Processor Features
 #
@@ -46,7 +40,6 @@ CONFIG_NEON=y
 # Power management options
 #
 CONFIG_PM=y
-# CONFIG_APM_EMULATION is not set
 
 #
 # Generic Driver Options
@@ -199,26 +192,17 @@ CONFIG_DRM=y
 CONFIG_DRM_I2C_NXP_TDA998X=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_OMAP=y
-# CONFIG_FIRMWARE_EDID is not set
 CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
-# CONFIG_FB_FOREIGN_ENDIAN is not set
 CONFIG_FB_MODE_HELPERS=y
 CONFIG_FB_TILEBLITTING=y
 
 #
 # Frame buffer hardware drivers
-#
-# CONFIG_FB_S1D13XXX is not set
-# CONFIG_FB_VIRTUAL is not set
-# CONFIG_FB_METRONOME is not set
-# CONFIG_FB_BROADSHEET is not set
-# CONFIG_FB_DA8XX is not set
 CONFIG_OMAP2_DSS=y
 CONFIG_OMAP2_DSS_DPI=y
 CONFIG_OMAP2_DSS_VENC=y
-# CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
 
@@ -237,8 +221,6 @@ CONFIG_BACKLIGHT_GENERIC=y
 CONFIG_DUMMY_CONSOLE=y
 CONFIG_FRAMEBUFFER_CONSOLE=y
 CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_VGA16 is not set
 CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
 CONFIG_SOUND=m
 CONFIG_SND=m
@@ -254,12 +236,6 @@ CONFIG_SND_SOC_TWL4030=m
 CONFIG_USB=y
 CONFIG_USB_SUPPORT=y
 
-#
-# Miscellaneous USB options
-#
-# CONFIG_USB_OTG is not set
-# CONFIG_USB_OTG_WHITELIST is not set
-
 #
 # USB Host Controller Drivers
 #
-- 
2.14.4

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

[linux-yocto] [PATCH 2/3] beaglebone: Drop the needless unsetting of the kernel options

2018-09-25 Thread Kevin Hao 
These kernel options are set to 'n' by default without any prompt.
So they are not supposed to be set/unset by the users.

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

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index ab42283c645f..b60c0721a22f 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -199,17 +199,11 @@ CONFIG_DRM=y
 CONFIG_DRM_I2C_NXP_TDA998X=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_OMAP=y
-# CONFIG_VGASTATE is not set
 # CONFIG_FIRMWARE_EDID is not set
-# CONFIG_FB_DDC is not set
-# CONFIG_FB_BOOT_VESA_SUPPORT is not set
 CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
 # CONFIG_FB_FOREIGN_ENDIAN is not set
-# CONFIG_FB_SVGALIB is not set
-# CONFIG_FB_MACMODES is not set
-# CONFIG_FB_BACKLIGHT is not set
 CONFIG_FB_MODE_HELPERS=y
 CONFIG_FB_TILEBLITTING=y
 
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.14 0/3] Fix the config check warnings

2018-09-25 Thread Kevin Hao 
Cherry-pick three patches from yocto-4.18 branch to fix the config
check warnings for beaglebone boards.

Kevin Hao (3):
  beaglebone: Drop the obsolete kernel options
  beaglebone: Drop the needless unsetting of the kernel options
  beaglebone: Clean up the cfg file

 bsp/beaglebone/beaglebone.cfg | 67 ---
 1 file changed, 67 deletions(-)

-- 
2.14.4

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

[yocto] [PATCH yocto-docs] ref-manual: Introduce the --use-label partition parameter for wic

2018-09-13 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
---
 documentation/ref-manual/ref-kickstart.xml | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/documentation/ref-manual/ref-kickstart.xml 
b/documentation/ref-manual/ref-kickstart.xml
index a58f9d7c9602..dd97dd7206c7 100644
--- a/documentation/ref-manual/ref-kickstart.xml
+++ b/documentation/ref-manual/ref-kickstart.xml
@@ -198,6 +198,16 @@
 If the given label is already in use by another filesystem,
 a new label is created for the partition.
 
+
+--use-label:
+Makes wic to use the label in /etc/fstab to specify a
+partition. If the --use-label and --use-uuid are used at
+the same time, we prefer the uuid because it is less likely
+to cause name confliction. We don't support using this
+parameter on the root partition since it requires an
+initramfs to parse this value and we do not currently
+support that.
+
 
 --active:
 Marks the partition as active.
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 5/6] beaglebone: Clean up the cfg file

2018-08-23 Thread Kevin Hao 
In general we only need to enable the kernel options we really care and
leave all other kernel options as is. That is to say we don't need to
disable any kernel options explicitly. So drop all of them.

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

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index b60c0721a22f..9acc07a68872 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -10,12 +10,6 @@ CONFIG_OMAP_32K_TIMER=y
 CONFIG_OMAP_DM_TIMER=y
 CONFIG_OMAP_RESET_CLOCKS=y
 
-#
-# OMAP Board Type
-#
-# CONFIG_MACH_OMAP3517EVM is not set
-# CONFIG_MACH_OMAP3_PANDORA is not set
-
 #
 # Processor Features
 #
@@ -46,7 +40,6 @@ CONFIG_NEON=y
 # Power management options
 #
 CONFIG_PM=y
-# CONFIG_APM_EMULATION is not set
 
 #
 # Generic Driver Options
@@ -199,26 +192,17 @@ CONFIG_DRM=y
 CONFIG_DRM_I2C_NXP_TDA998X=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_OMAP=y
-# CONFIG_FIRMWARE_EDID is not set
 CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
-# CONFIG_FB_FOREIGN_ENDIAN is not set
 CONFIG_FB_MODE_HELPERS=y
 CONFIG_FB_TILEBLITTING=y
 
 #
 # Frame buffer hardware drivers
-#
-# CONFIG_FB_S1D13XXX is not set
-# CONFIG_FB_VIRTUAL is not set
-# CONFIG_FB_METRONOME is not set
-# CONFIG_FB_BROADSHEET is not set
-# CONFIG_FB_DA8XX is not set
 CONFIG_OMAP2_DSS=y
 CONFIG_OMAP2_DSS_DPI=y
 CONFIG_OMAP2_DSS_VENC=y
-# CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
 
@@ -237,8 +221,6 @@ CONFIG_BACKLIGHT_GENERIC=y
 CONFIG_DUMMY_CONSOLE=y
 CONFIG_FRAMEBUFFER_CONSOLE=y
 CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_VGA16 is not set
 CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
 CONFIG_SOUND=m
 CONFIG_SND=m
@@ -254,12 +236,6 @@ CONFIG_SND_SOC_TWL4030=m
 CONFIG_USB=y
 CONFIG_USB_SUPPORT=y
 
-#
-# Miscellaneous USB options
-#
-# CONFIG_USB_OTG is not set
-# CONFIG_USB_OTG_WHITELIST is not set
-
 #
 # USB Host Controller Drivers
 #
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 3/6] beaglebone: Drop the obsolete kernel options

2018-08-23 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
---
 bsp/beaglebone/beaglebone.cfg | 37 -
 1 file changed, 37 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index a712321297c2..ab42283c645f 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -13,28 +13,8 @@ CONFIG_OMAP_RESET_CLOCKS=y
 #
 # OMAP Board Type
 #
-# CONFIG_MACH_OMAP3_BEAGLE is not set
-# CONFIG_MACH_DEVKIT8000 is not set
-# CONFIG_MACH_OMAP_LDP is not set
-# CONFIG_MACH_OMAP3530_LV_SOM is not set
-# CONFIG_MACH_OMAP3_TORPEDO is not set
-# CONFIG_MACH_OVERO is not set
-# CONFIG_MACH_OMAP3EVM is not set
 # CONFIG_MACH_OMAP3517EVM is not set
-# CONFIG_MACH_CRANEBOARD is not set
 # CONFIG_MACH_OMAP3_PANDORA is not set
-# CONFIG_MACH_TOUCHBOOK is not set
-# CONFIG_MACH_OMAP_3430SDP is not set
-# CONFIG_MACH_NOKIA_RM680 is not set
-# CONFIG_MACH_NOKIA_RX51 is not set
-# CONFIG_MACH_OMAP_ZOOM2 is not set
-# CONFIG_MACH_OMAP_ZOOM3 is not set
-# CONFIG_MACH_CM_T35 is not set
-# CONFIG_MACH_CM_T3517 is not set
-# CONFIG_MACH_IGEP0020 is not set
-# CONFIG_MACH_IGEP0030 is not set
-# CONFIG_MACH_SBC3530 is not set
-# CONFIG_MACH_OMAP_3630SDP is not set
 
 #
 # Processor Features
@@ -220,7 +200,6 @@ CONFIG_DRM_I2C_NXP_TDA998X=y
 CONFIG_DRM_TILCDC=y
 CONFIG_DRM_OMAP=y
 # CONFIG_VGASTATE is not set
-# CONFIG_VIDEO_OUTPUT_CONTROL is not set
 # CONFIG_FIRMWARE_EDID is not set
 # CONFIG_FB_DDC is not set
 # CONFIG_FB_BOOT_VESA_SUPPORT is not set
@@ -241,29 +220,17 @@ CONFIG_FB_TILEBLITTING=y
 # CONFIG_FB_VIRTUAL is not set
 # CONFIG_FB_METRONOME is not set
 # CONFIG_FB_BROADSHEET is not set
-# CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
 # CONFIG_FB_DA8XX is not set
-# CONFIG_FB_DA8XX_TDA998X is not set
 CONFIG_OMAP2_DSS=y
 CONFIG_OMAP2_DSS_DPI=y
 CONFIG_OMAP2_DSS_VENC=y
 # CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
-# CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
 
 #
 # OMAP Display Device Drivers (new device model)
 #
-CONFIG_DISPLAY_ENCODER_TFP410=m
-CONFIG_DISPLAY_ENCODER_TPD12S015=m
-CONFIG_DISPLAY_PANEL_DPI=y
-CONFIG_DISPLAY_CONNECTOR_DVI=y
-CONFIG_DISPLAY_CONNECTOR_HDMI=y
-# CONFIG_DISPLAY_PANEL_SHARP_LS037V7DW01 is not set
-# CONFIG_DISPLAY_PANEL_LGPHILIPS_LB035Q02 is not set
-# CONFIG_DISPLAY_PANEL_TPO_TD043MTEA1 is not set
-CONFIG_DISPLAY_PANEL_TFCS9700=y
 CONFIG_BACKLIGHT_LCD_SUPPORT=y
 CONFIG_LCD_CLASS_DEVICE=y
 CONFIG_LCD_PLATFORM=y
@@ -319,7 +286,6 @@ CONFIG_NOP_USB_XCEIV=y
 CONFIG_AM335X_CONTROL_USB=y
 CONFIG_AM335X_PHY_USB=y
 CONFIG_USB_GADGET=y
-CONFIG_OMAP_CONTROL_USB=y
 
 #
 # USB Peripheral Controller
@@ -327,7 +293,6 @@ CONFIG_OMAP_CONTROL_USB=y
 CONFIG_USB_G_NCM=m
 CONFIG_USB_MASS_STORAGE=m
 CONFIG_MMC=y
-CONFIG_MMC_UNSAFE_RESUME=y
 
 #
 # MMC/SD/SDIO Card Drivers
@@ -377,7 +342,6 @@ CONFIG_TI_CPPI41=y
 # Hardware Spinlock drivers
 #
 CONFIG_ARM_ARCH_TIMER=y
-CONFIG_CLKSRC_OF=y
 
 #
 # Rpmsg drivers
@@ -388,7 +352,6 @@ CONFIG_EXTCON=y
 # Extcon Device Drivers
 #
 CONFIG_EXTCON_PALMAS=y
-CONFIG_OF_EXTCON=y
 
 #
 # PHY Subsystem
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 6/6] common-pc: Drop the x2apic feature

2018-08-23 Thread Kevin Hao 
This is a feature for x86-64 platform and can't be enabled on x86-32.

Signed-off-by: Kevin Hao 
---
 bsp/common-pc/common-pc.scc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/bsp/common-pc/common-pc.scc b/bsp/common-pc/common-pc.scc
index 4818fb939e8c..cd947b0faa9d 100644
--- a/bsp/common-pc/common-pc.scc
+++ b/bsp/common-pc/common-pc.scc
@@ -27,8 +27,6 @@ include features/iwlwifi/iwlwifi.scc
 include features/iwlegacy/iwlegacy.scc
 include features/igb/igb.scc
 
-include features/x2apic/x2apic.scc
-
 include features/i915/i915.scc
 include features/drm-gma500/drm-gma500.scc
 
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 1/6] mpc8315e-rdb: Drop the obsolete kernel options

2018-08-23 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
---
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg 
b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
index 324989c1951a..57ebaabb6583 100644
--- a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
+++ b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
@@ -11,7 +11,6 @@
 #
 #.
 CONFIG_PPC32=y
-CONFIG_PPC_OF=y
 CONFIG_PPC_UDBG_16550=y
 
 #
@@ -154,5 +153,3 @@ CONFIG_FSL_DMA=y
 
 CONFIG_MMC=y
 CONFIG_MMC_SPI=m
-
-CONFIG_USB_FSL_MPH_DR_OF=y
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 2/6] edgerouter: Drop the obsolete kernel options

2018-08-23 Thread Kevin Hao 
Signed-off-by: Kevin Hao 
---
 bsp/edgerouter/edgerouter.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/bsp/edgerouter/edgerouter.cfg b/bsp/edgerouter/edgerouter.cfg
index 54597416dde8..f100ebde3eca 100644
--- a/bsp/edgerouter/edgerouter.cfg
+++ b/bsp/edgerouter/edgerouter.cfg
@@ -52,7 +52,6 @@ CONFIG_USB_EHCI_HCD=y
 CONFIG_USB_OCTEON_EHCI=y
 CONFIG_USB_OHCI_HCD=y
 CONFIG_USB_OCTEON_OHCI=y
-CONFIG_USB_OCTEON2_COMMON=y
 
 CONFIG_MTD=y
 CONFIG_MTD_BLOCK=y
-- 
2.14.4

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

[linux-yocto] [kernel-meta v4.18 0/6] Fix the config check warnings and some minor cleanup

2018-08-23 Thread Kevin Hao 
This patch series fixes the config check warnings when switching to the
v4.18 kernel for the boards in meta-yocto-bsp layer and also do some cleanup
for the cfg file.

Kevin Hao (6):
  mpc8315e-rdb: Drop the obsolete kernel options
  edgerouter: Drop the obsolete kernel options
  beaglebone: Drop the obsolete kernel options
  beaglebone: Drop the needless unsetting of the kernel options
  beaglebone: Clean up the cfg file
  common-pc: Drop the x2apic feature

 bsp/beaglebone/beaglebone.cfg | 67 ---
 bsp/common-pc/common-pc.scc   |  2 -
 bsp/edgerouter/edgerouter.cfg |  1 -
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg |  3 --
 4 files changed, 73 deletions(-)

-- 
2.14.4

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

[linux-yocto] [PATCH 4.14&4.15] staging: octeon: Add a workaround for the issue of GCC8

2018-06-20 Thread Kevin Hao 
In function cvm_oct_xmit(), the packet length is set with code like
this:
  pko_command.s.total_bytes = skb->len;

But when building with gcc8, the pko_command.s.total_bytes doesn't
emit the right value when it is used in the following codes:
/* Send the packet to the output queue */
if (unlikely(cvmx_pko_send_packet_finish(priv->port,
 priv->queue + qos,
 pko_command, hw_buffer,
 CVMX_PKO_LOCK_NONE))) {

Adding a barrier after the assignment would generate the right codes.

Signed-off-by: Kevin Hao 
---
This fixes a Ethernet malfunction building with the gcc8.

 drivers/staging/octeon/ethernet-tx.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/staging/octeon/ethernet-tx.c 
b/drivers/staging/octeon/ethernet-tx.c
index 31f35025d19e..af9da2508e93 100644
--- a/drivers/staging/octeon/ethernet-tx.c
+++ b/drivers/staging/octeon/ethernet-tx.c
@@ -264,6 +264,9 @@ int cvm_oct_xmit(struct sk_buff *skb, struct net_device 
*dev)
pko_command.s.n2 = 1;   /* Don't pollute L2 with the outgoing packet */
pko_command.s.segs = 1;
pko_command.s.total_bytes = skb->len;
+#if GCC_VERSION >= 8
+   barrier();
+#endif
pko_command.s.size0 = CVMX_FAU_OP_SIZE_32;
pko_command.s.subone0 = 1;
 
-- 
2.14.3

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

Re: [linux-yocto] [PATCH] mips: kernel: Move cc-disable-warning assignments down to avoid being overwritten

2018-06-17 Thread Kevin Hao 
On Fri, Jun 15, 2018 at 07:12:09AM -0700, He Zhe wrote:
> cc-disable-warning assignments could be overwritten by CFLAGS_DSP and thus
> causes the follow build error with GCC 8.1.0. Move them down to the bottom.
> 
> In file included from arch/mips/kernel/signal32.c:15:
> include/linux/syscalls.h:233:18: error: 'sys_32_sigaction' alias between 
> functions of incompatible types 'long int(long int,  const struct 
> compat_sigaction *, struct compat_sigaction *)' and 'long int(long int,  long 
> int,  long int)' [-Werror=attribute-alias]
>   asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \
>   ^~~

I have sent a patch [1] to fix this issue and it has been merged into 
linux-yocto
several days ago.

[1]  https://lists.yoctoproject.org/pipermail/linux-yocto/2018-June/007140.html

Thanks,
Kevin

> 
> Signed-off-by: He Zhe 
> ---
>  arch/mips/kernel/Makefile | 9 +
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/mips/kernel/Makefile b/arch/mips/kernel/Makefile
> index 795aa4c9ef7f..0234db5e0a98 100644
> --- a/arch/mips/kernel/Makefile
> +++ b/arch/mips/kernel/Makefile
> @@ -2,10 +2,6 @@
>  #
>  # Makefile for the Linux/MIPS kernel.
>  #
> -CFLAGS_signal.o  += $(call cc-disable-warning, attribute-alias)
> -CFLAGS_syscall.o += $(call cc-disable-warning, attribute-alias)
> -CFLAGS_linux32.o += $(call cc-disable-warning, attribute-alias)
> -CFLAGS_signal32.o+= $(call cc-disable-warning, attribute-alias)
>  
>  extra-y  := head.o vmlinux.lds
>  
> @@ -135,4 +131,9 @@ CFLAGS_branch.o   = $(CFLAGS_DSP)
>  CFLAGS_ptrace.o  = $(CFLAGS_DSP)
>  endif
>  
> +CFLAGS_signal.o  += $(call cc-disable-warning, attribute-alias)
> +CFLAGS_syscall.o += $(call cc-disable-warning, attribute-alias)
> +CFLAGS_linux32.o += $(call cc-disable-warning, attribute-alias)
> +CFLAGS_signal32.o+= $(call cc-disable-warning, attribute-alias)
> +
>  CPPFLAGS_vmlinux.lds := $(KBUILD_CFLAGS)
> -- 
> 2.11.0
> 
> -- 
> ___
> linux-yocto mailing list
> linux-yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto


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

[linux-yocto] [PATCH 4.14&4.15] MIPS: Use '+=" instead of '=' to avoid the CFLAGS override

2018-06-11 Thread Kevin Hao 
We used the CFLAGS_xxx to workaround the gcc 8 build warnings
for some specific file. But CFLAGS_xxx is also used with '=' in
other places of this Makefile. This override the gcc 8 workaround,
so replace all the '=' with '+=" to fix this issue.

Signed-off-by: Kevin Hao 
---
 arch/mips/kernel/Makefile | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/arch/mips/kernel/Makefile b/arch/mips/kernel/Makefile
index f10e1e15e1c6..7a00a8e840ad 100644
--- a/arch/mips/kernel/Makefile
+++ b/arch/mips/kernel/Makefile
@@ -124,11 +124,11 @@ obj-$(CONFIG_MIPS_CPS_PM) += pm-cps.o
 ifeq ($(CONFIG_CPU_MIPSR2), y)
 CFLAGS_DSP = -DHAVE_AS_DSP
 
-CFLAGS_signal.o= $(CFLAGS_DSP)
-CFLAGS_signal32.o  = $(CFLAGS_DSP)
-CFLAGS_process.o   = $(CFLAGS_DSP)
-CFLAGS_branch.o= $(CFLAGS_DSP)
-CFLAGS_ptrace.o= $(CFLAGS_DSP)
+CFLAGS_signal.o+= $(CFLAGS_DSP)
+CFLAGS_signal32.o  += $(CFLAGS_DSP)
+CFLAGS_process.o   += $(CFLAGS_DSP)
+CFLAGS_branch.o+= $(CFLAGS_DSP)
+CFLAGS_ptrace.o+= $(CFLAGS_DSP)
 endif
 
 CPPFLAGS_vmlinux.lds   := $(KBUILD_CFLAGS)
-- 
2.14.3

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

[linux-yocto] [linux-yocto 4.15] crypto: aes-generic - fix aes-generic regression on powerpc

2018-06-07 Thread Kevin Hao 
From: Arnd Bergmann 

commit 6e36719fbe90213fbba9f50093fa2d4d69b0e93c upstream

My last bugfix added -Os on the command line, which unfortunately caused
a build regression on powerpc in some configurations.

I've done some more analysis of the original problem and found slightly
different workaround that avoids this regression and also results in
better performance on gcc-7.0: -fcode-hoisting is an optimization step
that got added in gcc-7 and that for all gcc-7 versions causes worse
performance.

This disables -fcode-hoisting on all compilers that understand the option.
For gcc-7.1 and 7.2 I found the same performance as my previous patch
(using -Os), in gcc-7.0 it was even better. On gcc-8 I could see no
change in performance from this patch. In theory, code hoisting should
not be able make things better for the AES cipher, so leaving it
disabled for gcc-8 only serves to simplify the Makefile change.

Reported-by: kbuild test robot 
Link: https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg30418.html
Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83356
Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
Fixes: 148b974deea9 ("crypto: aes-generic - build with -Os on gcc-7+")
Signed-off-by: Arnd Bergmann 
Signed-off-by: Herbert Xu 
Signed-off-by: Kevin Hao 
---

This fixes the build failure on mpc8315e-rdb board.

 crypto/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crypto/Makefile b/crypto/Makefile
index daa69360e054..cdbc03b35510 100644
--- a/crypto/Makefile
+++ b/crypto/Makefile
@@ -99,7 +99,7 @@ obj-$(CONFIG_CRYPTO_TWOFISH_COMMON) += twofish_common.o
 obj-$(CONFIG_CRYPTO_SERPENT) += serpent_generic.o
 CFLAGS_serpent_generic.o := $(call cc-option,-fsched-pressure)  # 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79149
 obj-$(CONFIG_CRYPTO_AES) += aes_generic.o
-CFLAGS_aes_generic.o := $(call cc-ifversion, -ge, 0701, -Os) # 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83356
+CFLAGS_aes_generic.o := $(call cc-option,-fno-code-hoisting) # 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83356
 obj-$(CONFIG_CRYPTO_AES_TI) += aes_ti.o
 obj-$(CONFIG_CRYPTO_CAMELLIA) += camellia_generic.o
 obj-$(CONFIG_CRYPTO_CAST_COMMON) += cast_common.o
-- 
2.14.3

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

[linux-yocto] [PATCH kernel 2/2] net: phy: realtek: Use the dummy stubs for MMD register access for rtl8211b

2018-03-21 Thread Kevin Hao 
From: Kevin Hao <haoke...@gmail.com>

The Ethernet on mpc8315erdb is broken since commit b6b5e8a69118
("gianfar: Disable EEE autoneg by default"). The reason is that
even though the rtl8211b doesn't support the MMD extended registers
access, it does return some random values if we trying to access
the MMD register via indirect method. This makes it seem that the
EEE is supported by this phy device. And the subsequent writing to
the MMD registers does cause the phy malfunction. So use the dummy
stubs for the MMD register access to fix this issue.

Fixes: b6b5e8a69118 ("gianfar: Disable EEE autoneg by default")
Signed-off-by: Kevin Hao <haoke...@gmail.com>
---
 drivers/net/phy/realtek.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/phy/realtek.c b/drivers/net/phy/realtek.c
index eda0a6e86918..68b4a7c61bab 100644
--- a/drivers/net/phy/realtek.c
+++ b/drivers/net/phy/realtek.c
@@ -183,6 +183,8 @@ static struct phy_driver realtek_drvs[] = {
.read_status= _read_status,
.ack_interrupt  = _ack_interrupt,
.config_intr= _config_intr,
+   .read_mmd   = _read_mmd_unsupported,
+   .write_mmd  = _write_mmd_unsupported,
}, {
.phy_id = 0x001cc914,
.name   = "RTL8211DN Gigabit Ethernet",
-- 
2.9.3

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

[linux-yocto] [PATCH kernel 1/2] net: phy: Add general dummy stubs for MMD register access

2018-03-21 Thread Kevin Hao 
From: Kevin Hao <haoke...@gmail.com>

For some phy devices, even though they don't support the MMD extended
register access, it does have some side effect if we are trying to
read/write the MMD registers via indirect method. So introduce general
dummy stubs for MMD register access which these devices can use to avoid
such side effect.

Fixes: b6b5e8a69118 ("gianfar: Disable EEE autoneg by default")
Signed-off-by: Kevin Hao <haoke...@gmail.com>
---
 drivers/net/phy/phy_device.c | 17 +
 include/linux/phy.h  |  4 
 2 files changed, 21 insertions(+)

diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index b15b31ca2618..6893dd2a681d 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -1626,6 +1626,23 @@ int genphy_config_init(struct phy_device *phydev)
 }
 EXPORT_SYMBOL(genphy_config_init);
 
+/* This is used for the phy device which doesn't support the MMD extended
+ * register access, but it does have side effect when we are trying to access
+ * the MMD register via indirect method.
+ */
+int genphy_read_mmd_unsupported(struct phy_device *phdev, int devad, u16 
regnum)
+{
+   return -EOPNOTSUPP;
+}
+EXPORT_SYMBOL(genphy_read_mmd_unsupported);
+
+int genphy_write_mmd_unsupported(struct phy_device *phdev, int devnum,
+u16 regnum, u16 val)
+{
+   return -EOPNOTSUPP;
+}
+EXPORT_SYMBOL(genphy_write_mmd_unsupported);
+
 int genphy_suspend(struct phy_device *phydev)
 {
int value;
diff --git a/include/linux/phy.h b/include/linux/phy.h
index dc82a07cb4fd..e6d27bc80146 100644
--- a/include/linux/phy.h
+++ b/include/linux/phy.h
@@ -880,6 +880,10 @@ static inline int genphy_no_soft_reset(struct phy_device 
*phydev)
 {
return 0;
 }
+int genphy_read_mmd_unsupported(struct phy_device *phdev, int devad,
+   u16 regnum);
+int genphy_write_mmd_unsupported(struct phy_device *phdev, int devnum,
+u16 regnum, u16 val);
 
 /* Clause 45 PHY */
 int genphy_c45_restart_aneg(struct phy_device *phydev);
-- 
2.9.3

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

[linux-yocto] [PATCH kernel-meta] mpc8315e-rdb: Enable Realtek PHY driver

2018-03-21 Thread Kevin Hao 
A Realtek RTL8211B PHY is integrated on mpc8315erdb board. It works
pretty well with the genphy driver. But now we apply a patch for the
Realtek PHY driver in order to fix an Ethernet broken issue on this
board. So enable this chip specific driver to make sure that fix can
take effect.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg 
b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
index 698efe2b7305..324989c1951a 100644
--- a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
+++ b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg
@@ -64,6 +64,7 @@ CONFIG_MTD_NAND_FSL_ELBC=y
 # Ethernet (1000 Mbit)
 #
 CONFIG_GIANFAR=y
+CONFIG_REALTEK_PHY=y
 
 #
 # Serial drivers
-- 
2.9.3

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

[linux-yocto] [PATCH linux-yocto v4.15] yaffs2: Adjust the timer callback and init functions

2018-02-22 Thread Kevin Hao 
The timer callback argument type has been changed by commit 354b46b1a0ad
("timer: Switch callback prototype to take struct timer_list *
argument") and init_timer_on_stack() is also removed by commit
9c6c273aa424 ("timer: Remove init_timer_on_stack() in favor of
timer_setup_on_stack()"). Adjust the codes in yaffs2 according to
these changes.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 26 --
 1 file changed, 16 insertions(+), 10 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index c7be4cddd1de..c99acf08a0d8 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -136,7 +136,7 @@
 #if (LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 26))
 #define Y_INIT_TIMER(a)init_timer(a)
 #else
-#define Y_INIT_TIMER(a)init_timer_on_stack(a)
+#define Y_INIT_TIMER(a)timer_setup_on_stack(a, NULL, 0)
 #endif
 
 #if (LINUX_VERSION_CODE > KERNEL_VERSION(2, 6, 27))
@@ -2065,10 +2065,16 @@ static unsigned yaffs_bg_gc_urgency(struct yaffs_dev 
*dev)
 }
 
 #ifdef YAFFS_COMPILE_BACKGROUND
+struct yaffs_timer {
+   struct timer_list timer;
+   struct task_struct *tsk;
+};
 
-void yaffs_background_waker(unsigned long data)
+void yaffs_background_waker(struct timer_list *t)
 {
-   wake_up_process((struct task_struct *)data);
+   struct yaffs_timer *yt = from_timer(yt, t, timer);
+
+   wake_up_process(yt->tsk);
 }
 
 static int yaffs_bg_thread_fn(void *data)
@@ -2082,7 +2088,7 @@ static int yaffs_bg_thread_fn(void *data)
unsigned int urgency;
 
int gc_result;
-   struct timer_list timer;
+   struct yaffs_timer yt;
 
yaffs_trace(YAFFS_TRACE_BACKGROUND,
"yaffs_background starting for dev %p", (void *)dev);
@@ -2135,15 +2141,15 @@ static int yaffs_bg_thread_fn(void *data)
if (time_before(expires, now))
expires = now + HZ;
 
-   Y_INIT_TIMER();
-   timer.expires = expires + 1;
-   timer.data = (unsigned long)current;
-   timer.function = yaffs_background_waker;
+   Y_INIT_TIMER();
+   yt.timer.function = yaffs_background_waker;
+   yt.timer.expires = expires + 1;
+   yt.tsk = current;
 
set_current_state(TASK_INTERRUPTIBLE);
-   add_timer();
+   add_timer();
schedule();
-   del_timer_sync();
+   del_timer_sync();
 #else
msleep(10);
 #endif
-- 
2.9.3

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

[linux-yocto] [PATCH linux-yocto v4.14 & v4.15] yaffs2: include rawnand.h instead of nand.h

2018-02-22 Thread Kevin Hao 
The nand.h has been renamed to rawnand.h by commit d4092d76a4a4 ("mtd:
nand: Rename nand.h into rawnand.h"), adjust the yaffs2 code according
to this change.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_mtdif.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/yaffs2/yaffs_mtdif.c b/fs/yaffs2/yaffs_mtdif.c
index fa4b99834570..03a3d9c24e4c 100644
--- a/fs/yaffs2/yaffs_mtdif.c
+++ b/fs/yaffs2/yaffs_mtdif.c
@@ -18,7 +18,7 @@
 #include "linux/mtd/mtd.h"
 #include "linux/types.h"
 #include "linux/time.h"
-#include "linux/mtd/nand.h"
+#include "linux/mtd/rawnand.h"
 #include "linux/kernel.h"
 #include "linux/version.h"
 #include "linux/types.h"
-- 
2.9.3

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

[linux-yocto] [PATCH 4.12] drm/tilcdc: Precalculate total frametime in tilcdc_crtc_set_mode()

2018-01-18 Thread Kevin Hao 
From: Jyri Sarha <jsa...@ti.com>

commit ce99f7206c9105851d97202ed08c058af6f11ac4 upstream

We need the total frame refresh time to check if we are too close to
vertical sync when updating the two framebuffer DMA registers and risk
a collision. This new method is more accurate that the previous that
based on mode's vrefresh value, which itself is inaccurate or may not
even be initialized.

Reported-by: Kevin Hao <kexin@windriver.com>
Fixes: 11abbc9f39e0 ("drm/tilcdc: Set framebuffer DMA address to HW only if 
CRTC is enabled")
Cc: <sta...@vger.kernel.org> # v4.11+
Signed-off-by: Jyri Sarha <jsa...@ti.com>
Reviewed-by: Tomi Valkeinen <tomi.valkei...@ti.com>
---
This fixes the Bug 12131 - Kernel traceback when reboot beaglebone black.
  https://bugzilla.yoctoproject.org/show_bug.cgi?id=12131

 drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 13 -
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c 
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index d524ed0d5146..9e607b914c2b 100644
--- a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
+++ b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
@@ -24,6 +24,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "tilcdc_drv.h"
 #include "tilcdc_regs.h"
@@ -48,6 +49,7 @@ struct tilcdc_crtc {
unsigned int lcd_fck_rate;
 
ktime_t last_vblank;
+   unsigned int hvtotal_us;
 
struct drm_framebuffer *curr_fb;
struct drm_framebuffer *next_fb;
@@ -292,6 +294,12 @@ static void tilcdc_crtc_set_clk(struct drm_crtc *crtc)
LCDC_V2_CORE_CLK_EN);
 }
 
+uint tilcdc_mode_hvtotal(const struct drm_display_mode *mode)
+{
+   return (uint) div_u64(1000llu * mode->htotal * mode->vtotal,
+ mode->clock);
+}
+
 static void tilcdc_crtc_set_mode(struct drm_crtc *crtc)
 {
struct tilcdc_crtc *tilcdc_crtc = to_tilcdc_crtc(crtc);
@@ -459,6 +467,9 @@ static void tilcdc_crtc_set_mode(struct drm_crtc *crtc)
drm_framebuffer_reference(fb);
 
crtc->hwmode = crtc->state->adjusted_mode;
+
+   tilcdc_crtc->hvtotal_us =
+   tilcdc_mode_hvtotal(>hwmode);
 }
 
 static void tilcdc_crtc_enable(struct drm_crtc *crtc)
@@ -636,7 +647,7 @@ int tilcdc_crtc_update_fb(struct drm_crtc *crtc,
spin_lock_irqsave(_crtc->irq_lock, flags);
 
next_vblank = ktime_add_us(tilcdc_crtc->last_vblank,
-  100 / crtc->hwmode.vrefresh);
+  tilcdc_crtc->hvtotal_us);
tdiff = ktime_to_us(ktime_sub(next_vblank, ktime_get()));
 
if (tdiff < TILCDC_VBLANK_SAFETY_THRESHOLD_US)
-- 
2.9.3

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

[linux-yocto] [Resend v4.12 PATCH 2/2] fs: yaffs2: includes the missing header file

2017-08-27 Thread Kevin Hao 
To fix the following build error:
  fs/yaffs2/yaffs_vfs.c: In function 'yaffs_mknod':
  fs/yaffs2/yaffs_vfs.c:1252:2: error: implicit declaration of function 
'current_fsuid' [-Werror=implicit-function-declaration]
uid_t uid = YCRED_FSUID();
^

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 8b2019fe3c2c..c7be4cddd1de 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -167,6 +167,7 @@ static uint32_t YCALCBLOCKS(uint64_t partition_size, 
uint32_t block_size)
 
 #include 
 #include 
+#include 
 
 #include "yportenv.h"
 #include "yaffs_trace.h"
-- 
2.9.3

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

Re: [yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

2017-06-11 Thread Kevin Hao 
On Sun, Jun 11, 2017 at 11:07:14AM +0100, Richard Purdie wrote:
> On Fri, 2017-06-09 at 09:30 +0800, Kevin Hao wrote:
> > On Thu, Jun 08, 2017 at 02:45:14PM -0400, Bruce Ashfield wrote:
> > > 
> > > The reference BSPs are lagging on their 4.1 SRCREVs, which means
> > > -stable updates, and gcc-7 build fixes are missing.
> > I have made a patch to update the SRCREVs for 4.1, 4.4, 4,9 and 4.10
> > three weeks ago,
> > but it seems not get merged. I just sent a ping for the merging.
> 
> The trouble is you and Alejandro send updates against the same file and
> one invariably fails to apply. I've fixed it up and applied it but one
> of you basing on the other would help with this.

Thanks Richard. We would avoid such kind of conflicts in the future.

Thanks,
Kevin


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

Re: [yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

2017-06-08 Thread Kevin Hao 
On Thu, Jun 08, 2017 at 02:45:14PM -0400, Bruce Ashfield wrote:
> The reference BSPs are lagging on their 4.1 SRCREVs, which means
> -stable updates, and gcc-7 build fixes are missing.

I have made a patch to update the SRCREVs for 4.1, 4.4, 4,9 and 4.10 three 
weeks ago,
but it seems not get merged. I just sent a ping for the merging.

Thanks,
Kevin

> 
> Signed-off-by: Bruce Ashfield 
> ---
>  meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
> b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> index b308c8dfa1cc..afb04c28f4d1 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
> @@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
>  
>  SRCREV_machine_genericx86?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
>  SRCREV_machine_genericx86-64 ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
> -SRCREV_machine_edgerouter ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
> -SRCREV_machine_beaglebone ?= "235de25be3f143b91dcc69479b770722c508889e"
> -SRCREV_machine_mpc8315e-rdb ?= "2ce56d130ddff67f43ec857cc51cd347666a0078"
> +SRCREV_machine_edgerouter ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
> +SRCREV_machine_beaglebone ?= "79414e2b0e0b7f5b86e358a907f841486f428079"
> +SRCREV_machine_mpc8315e-rdb ?= "398d1785c6bde0085b99f00f346e199a15fbdcef"
>  
>  COMPATIBLE_MACHINE_genericx86 = "genericx86"
>  COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
> -- 
> 2.5.0
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

Re: [linux-yocto] [linux-yocto v4.1 0/4] net: mwifiex: Enable the DRCS & MSI support

2017-03-22 Thread Kevin Hao 
On Wed, Mar 22, 2017 at 06:34:46AM +, Wan Mohamad, Wan Ahmad Zainie wrote:
> Hi Kevin.
> 
> > -Original Message-
> > From: Kevin Hao [mailto:kexin@windriver.com]
> > Sent: Monday, March 20, 2017 6:35 PM
> > To: Wan Mohamad, Wan Ahmad Zainie
> > <wan.ahmad.zainie.wan.moha...@intel.com>; Yong, Jonathan 
> > <jonathan.y...@intel.com>
> > Cc: Linux Yocto <linux-yocto@yoctoproject.org>; Ashfield, Bruce (Wind 
> > River) <bruce.ashfi...@windriver.com>
> > Subject: Re: [linux-yocto] [linux-yocto v4.1 0/4] net: mwifiex: Enable 
> > the DRCS & MSI support
> > 
> > On Wed, Mar 15, 2017 at 01:54:02PM -0400, Bruce Ashfield wrote:
> > > I need the intel maintainers of this branch to comment on the changes.
> > >
> > > I have no issues with merging them, but need their ack before I'll 
> > > do so.
> > 
> > Hi Wan & Jonathan,
> > 
> > Any comment?
> > 
> The branch standard/intel/4.1.27/leaf-hill is very specific to Leaf Hill 
> platform.
> I am OK to acknowledge, provided the patches has been tested on the
> Leaf Hill platform.

Yes, I have validated these patches with a AW Wifi module on Leaf Hill board,
it works pretty well.

Thanks,
Kevin


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 v4.1 0/4] net: mwifiex: Enable the DRCS & MSI support

2017-03-20 Thread Kevin Hao 
On Wed, Mar 15, 2017 at 01:54:02PM -0400, Bruce Ashfield wrote:
> I need the intel maintainers of this branch to comment on the changes.
> 
> I have no issues with merging them, but need their ack before I'll do
> so.

Hi Wan & Jonathan,

Any comment?

Thanks,
Kevin


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

[linux-yocto] [linux-yocto v4.1 1/4] mwifiex: enable MSI interrupt support in pcie

2017-03-14 Thread Kevin Hao 
From: Avinash Patil <pat...@marvell.com>

commit 7be0f5b5e169a566be9400481c21de32f147ccbe upstream

Newer pcie devices (8897 onwards) support MSI. This
patch enables it.

Signed-off-by: Avinash Patil <pat...@marvell.com>
Signed-off-by: Amitkumar Karwar <akar...@marvell.com>
Signed-off-by: Kalle Valo <kv...@codeaurora.org>
[Kevin: replace mwifiex_dbg() with pr_debug()]
Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 drivers/net/wireless/mwifiex/pcie.c | 32 +---
 drivers/net/wireless/mwifiex/pcie.h |  1 +
 2 files changed, 26 insertions(+), 7 deletions(-)

diff --git a/drivers/net/wireless/mwifiex/pcie.c 
b/drivers/net/wireless/mwifiex/pcie.c
index bcc7751d883c..dab899d48236 100644
--- a/drivers/net/wireless/mwifiex/pcie.c
+++ b/drivers/net/wireless/mwifiex/pcie.c
@@ -2538,6 +2538,30 @@ static void mwifiex_pcie_cleanup(struct mwifiex_adapter 
*adapter)
kfree(card);
 }
 
+static int mwifiex_pcie_request_irq(struct mwifiex_adapter *adapter)
+{
+   int ret;
+   struct pcie_service_card *card = adapter->card;
+   struct pci_dev *pdev = card->dev;
+
+   if (pci_enable_msi(pdev) != 0)
+   pci_disable_msi(pdev);
+   else
+   card->msi_enable = 1;
+
+   pr_debug("msi_enable = %d\n", card->msi_enable);
+
+   ret = request_irq(pdev->irq, mwifiex_pcie_interrupt, IRQF_SHARED,
+ "MRVL_PCIE", pdev);
+   if (ret) {
+   pr_err("request_irq failed: ret=%d\n", ret);
+   adapter->card = NULL;
+   return -1;
+   }
+
+   return 0;
+}
+
 /*
  * This function registers the PCIE device.
  *
@@ -2545,20 +2569,14 @@ static void mwifiex_pcie_cleanup(struct mwifiex_adapter 
*adapter)
  */
 static int mwifiex_register_dev(struct mwifiex_adapter *adapter)
 {
-   int ret;
struct pcie_service_card *card = adapter->card;
struct pci_dev *pdev = card->dev;
 
/* save adapter pointer in card */
card->adapter = adapter;
 
-   ret = request_irq(pdev->irq, mwifiex_pcie_interrupt, IRQF_SHARED,
- "MRVL_PCIE", pdev);
-   if (ret) {
-   pr_err("request_irq failed: ret=%d\n", ret);
-   adapter->card = NULL;
+   if (mwifiex_pcie_request_irq(adapter))
return -1;
-   }
 
adapter->dev = >dev;
adapter->tx_buf_size = card->pcie.tx_buf_size;
diff --git a/drivers/net/wireless/mwifiex/pcie.h 
b/drivers/net/wireless/mwifiex/pcie.h
index 0e7ee8b72358..78e3a0aa68ee 100644
--- a/drivers/net/wireless/mwifiex/pcie.h
+++ b/drivers/net/wireless/mwifiex/pcie.h
@@ -284,6 +284,7 @@ struct pcie_service_card {
dma_addr_t sleep_cookie_pbase;
void __iomem *pci_mmap;
void __iomem *pci_mmap1;
+   int msi_enable;
 };
 
 static inline int
-- 
2.9.3

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

[linux-yocto] [linux-yocto v4.1 3/4] mwifiex: support to set multichannel policy to FW

2017-03-14 Thread Kevin Hao 
From: Avinash Patil 

commit d5b036c403f811c6d1856b8e6891a6438cf56f61 upstream

This patch adds support for setting multichannel policy as module parameter
to FW. Value of 1 indicates Multichannel support is enabled
and value of 0 disables it.

Signed-off-by: Avinash Patil 
Signed-off-by: Kalle Valo 
---
 drivers/net/wireless/mwifiex/fw.h  |  8 
 drivers/net/wireless/mwifiex/sta_cmd.c | 31 ++
 drivers/net/wireless/mwifiex/sta_cmdresp.c |  1 +
 3 files changed, 40 insertions(+)

diff --git a/drivers/net/wireless/mwifiex/fw.h 
b/drivers/net/wireless/mwifiex/fw.h
index 59d8964dd0dc..1b3b24a3d857 100644
--- a/drivers/net/wireless/mwifiex/fw.h
+++ b/drivers/net/wireless/mwifiex/fw.h
@@ -197,6 +197,7 @@ enum MWIFIEX_802_11_PRIVACY_FILTER {
 
 #define ISSUPP_11NENABLED(FwCapInfo) (FwCapInfo & BIT(11))
 #define ISSUPP_TDLS_ENABLED(FwCapInfo) (FwCapInfo & BIT(14))
+#define ISSUPP_DRCS_ENABLED(FwCapInfo) (FwCapInfo & BIT(15))
 #define ISSUPP_SDIO_SPA_ENABLED(FwCapInfo) (FwCapInfo & BIT(16))
 
 #define MWIFIEX_DEF_HT_CAP (IEEE80211_HT_CAP_DSSSCCK40 | \
@@ -353,6 +354,7 @@ enum MWIFIEX_802_11_PRIVACY_FILTER {
 #define HostCmd_CMD_MGMT_FRAME_REG0x010c
 #define HostCmd_CMD_REMAIN_ON_CHAN0x010d
 #define HostCmd_CMD_11AC_CFG 0x0112
+#define HostCmd_CMD_MC_POLICY 0x0121
 #define HostCmd_CMD_TDLS_OPER 0x0122
 #define HostCmd_CMD_SDIO_SP_RX_AGGR_CFG   0x0223
 
@@ -1908,6 +1910,11 @@ struct host_cmd_ds_coalesce_cfg {
struct coalesce_receive_filt_rule rule[0];
 } __packed;
 
+struct host_cmd_ds_multi_chan_policy {
+   __le16 action;
+   __le16 policy;
+} __packed;
+
 struct host_cmd_ds_command {
__le16 command;
__le16 size;
@@ -1973,6 +1980,7 @@ struct host_cmd_ds_command {
struct host_cmd_ds_tdls_oper tdls_oper;
struct host_cmd_ds_chan_rpt_req chan_rpt_req;
struct host_cmd_sdio_sp_rx_aggr_cfg sdio_rx_aggr_cfg;
+   struct host_cmd_ds_multi_chan_policy mc_policy;
} params;
 } __packed;
 
diff --git a/drivers/net/wireless/mwifiex/sta_cmd.c 
b/drivers/net/wireless/mwifiex/sta_cmd.c
index 49422f2a5380..f58c5d999876 100644
--- a/drivers/net/wireless/mwifiex/sta_cmd.c
+++ b/drivers/net/wireless/mwifiex/sta_cmd.c
@@ -26,6 +26,10 @@
 #include "11n.h"
 #include "11ac.h"
 
+static bool drcs;
+module_param(drcs, bool, 0644);
+MODULE_PARM_DESC(drcs, "multi-channel operation:1, single-channel 
operation:0");
+
 static bool disable_auto_ds;
 module_param(disable_auto_ds, bool, 0);
 MODULE_PARM_DESC(disable_auto_ds,
@@ -1480,6 +1484,22 @@ static int mwifiex_cmd_cfg_data(struct mwifiex_private 
*priv,
 }
 
 static int
+mwifiex_cmd_set_mc_policy(struct mwifiex_private *priv,
+ struct host_cmd_ds_command *cmd,
+ u16 cmd_action, void *data_buf)
+{
+   struct host_cmd_ds_multi_chan_policy *mc_pol = >params.mc_policy;
+   const u16 *drcs_info = data_buf;
+
+   mc_pol->action = cpu_to_le16(cmd_action);
+   mc_pol->policy = cpu_to_le16(*drcs_info);
+   cmd->command = cpu_to_le16(HostCmd_CMD_MC_POLICY);
+   cmd->size = cpu_to_le16(sizeof(struct host_cmd_ds_multi_chan_policy) +
+   S_DS_GEN);
+   return 0;
+}
+
+static int
 mwifiex_cmd_coalesce_cfg(struct mwifiex_private *priv,
 struct host_cmd_ds_command *cmd,
 u16 cmd_action, void *data_buf)
@@ -1931,6 +1951,10 @@ int mwifiex_sta_prepare_cmd(struct mwifiex_private 
*priv, uint16_t cmd_no,
ret = mwifiex_cmd_sdio_rx_aggr_cfg(cmd_ptr, cmd_action,
   data_buf);
break;
+   case HostCmd_CMD_MC_POLICY:
+   ret = mwifiex_cmd_set_mc_policy(priv, cmd_ptr, cmd_action,
+   data_buf);
+   break;
default:
dev_err(priv->adapter->dev,
"PREP_CMD: unknown cmd- %#x\n", cmd_no);
@@ -2047,6 +2071,13 @@ int mwifiex_sta_init_cmd(struct mwifiex_private *priv, 
u8 first_sta, bool init)
if (ret)
return -1;
}
+
+   if (ISSUPP_DRCS_ENABLED(adapter->fw_cap_info))
+   ret = mwifiex_send_cmd(priv, HostCmd_CMD_MC_POLICY,
+  HostCmd_ACT_GEN_SET, 0, ,
+  true);
+   if (ret)
+   return -1;
}
 
/* get tx rate */
diff --git a/drivers/net/wireless/mwifiex/sta_cmdresp.c 
b/drivers/net/wireless/mwifiex/sta_cmdresp.c
index 88dc6b672ef4..e3b7b6adfe69 100644
--- a/drivers/net/wireless/mwifiex/sta_cmdresp.c
+++

[linux-yocto] [linux-yocto v4.1 0/4] net: mwifiex: Enable the DRCS & MSI support

2017-03-14 Thread Kevin Hao 
From: Kevin Hao <haoke...@gmail.com>

Hi,

This targets on standard/intel/4.1.27/leaf-hill branch. In order to support
concurrent AP(5G) and client(2.4G) mode, we need to enable the DRCS(Dynamic
Rapid Channel Switching) feature in the Wifi module. Pick up two patches
from mainline to enable this feature. The other two patches are for the
MSI interrupt support.

Avinash Patil (3):
  mwifiex: enable MSI interrupt support in pcie
  mwifiex: support to set multichannel policy to FW
  mwifiex: advertise multichannel support to cfg80211

Shengzhen Li (1):
  mwifiex: fix interrupt processing corner case in MSI mode

 drivers/net/wireless/mwifiex/cfg80211.c| 14 +-
 drivers/net/wireless/mwifiex/fw.h  |  8 +++
 drivers/net/wireless/mwifiex/main.h|  1 +
 drivers/net/wireless/mwifiex/pcie.c| 81 ++
 drivers/net/wireless/mwifiex/pcie.h|  1 +
 drivers/net/wireless/mwifiex/sta_cmd.c | 36 +
 drivers/net/wireless/mwifiex/sta_cmdresp.c |  1 +
 7 files changed, 130 insertions(+), 12 deletions(-)

-- 
2.9.3

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

[linux-yocto] [linux-yocto 4.9 0/3] Fix the build errors when yaffs2 is enabled

2017-01-31 Thread Kevin Hao 
All these build errors are caused by the API changes in the mainline kernel.
Adjust the codes in yaffs2 to fix these errors.

Kevin Hao (3):
  fs: yaffs2: adjust to the change of inode_change_ok()
  fs: yaffs2: switch to the generic xattr handler
  fs: yaffs2: fix the prototype of function yaffs_rename()

 fs/yaffs2/yaffs_vfs.c | 45 ++---
 1 file changed, 34 insertions(+), 11 deletions(-)

-- 
2.9.3

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

[linux-yocto] [PATCH 3/3] fs: yaffs2: fix the prototype of function yaffs_rename()

2017-01-31 Thread Kevin Hao 
The "rename2" of i_op has been renamed to "rename" in commit
2773bf00aeb9("fs: rename "rename2" i_op to "rename""). We do what we
have done in commit 1cd66c93ba8c("fs: make remaining filesystems use .rename2")
for yaffs2 according to this change.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index efcb118d2ba1..c9dea27a4a78 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1487,12 +1487,16 @@ static int yaffs_symlink(struct inode *dir, struct 
dentry *dentry,
  * NB: POSIX says you can rename an object over an old object of the same name
  */
 static int yaffs_rename(struct inode *old_dir, struct dentry *old_dentry,
-   struct inode *new_dir, struct dentry *new_dentry)
+   struct inode *new_dir, struct dentry *new_dentry,
+   unsigned int flags)
 {
struct yaffs_dev *dev;
int ret_val = YAFFS_FAIL;
struct yaffs_obj *target;
 
+   if (flags)
+   return -EINVAL;
+
yaffs_trace(YAFFS_TRACE_OS, "yaffs_rename");
dev = yaffs_inode_to_obj(old_dir)->my_dev;
 
-- 
2.9.3

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

[linux-yocto] [PATCH 1/3] fs: yaffs2: adjust to the change of inode_change_ok()

2017-01-31 Thread Kevin Hao 
In commit cb8e1eef351b ("fs: Give dentry to inode_change_ok() instead
of inode") the inode_change_ok() has been rename to setattr_prepare(),
and one of the argument was also changed from inode to dentry. We
adjust the invocation of inode_change_ok() in Yaffs2 according to
this change.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 5a9c295aecc8..e5e0c650baca 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -885,7 +885,7 @@ static int yaffs_setattr(struct dentry *dentry, struct 
iattr *attr)
 #endif
 
if (error == 0)
-   error = inode_change_ok(inode, attr);
+   error = setattr_prepare(dentry, attr);
if (error == 0) {
int result;
if (!error) {
-- 
2.9.3

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

[linux-yocto] [linux-yocto 4.1] fs/yaffs2: adjust to the change of inode_change_ok()

2017-01-25 Thread Kevin Hao 
In commit cb8e1eef351b ("fs: Give dentry to inode_change_ok() instead
of inode") the inode_change_ok() has been rename to setattr_prepare(),
and one of the argument was also changed from inode to dentry. We
adjust the invocation of inode_change_ok() in Yaffs2 according to
this change.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 16251d5dcb17..cbdea23493bb 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -885,7 +885,7 @@ static int yaffs_setattr(struct dentry *dentry, struct 
iattr *attr)
 #endif
 
if (error == 0)
-   error = inode_change_ok(inode, attr);
+   error = setattr_prepare(dentry, attr);
if (error == 0) {
int result;
if (!error) {
-- 
2.9.3

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

[linux-yocto] [PATCH] meta-yocto-bsp: linux-yocto: bump to the latest stable version for non-x86 BSPs

2016-10-26 Thread Kevin Hao 
Built and boot test for all these boards on 4.1, 4.4 and 4.8 kernels.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend |  6 +++---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 12 ++--
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | 12 ++--
 3 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index e6607c79f4fe..da6b21c6bdfe 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86?= "a38cb202738a2b055ac216b3699cc9377edea45a"
 SRCREV_machine_genericx86-64 ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
-SRCREV_machine_edgerouter ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
-SRCREV_machine_beaglebone ?= "3e064525c427e128d08ea599ea3247e2963b54a5"
-SRCREV_machine_mpc8315e-rdb ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
+SRCREV_machine_edgerouter ?= "f4d0900b2851e829e990e0f64b09ed3b8e355fae"
+SRCREV_machine_beaglebone ?= "12532e753b50997690923e03edb3ac3368817a26"
+SRCREV_machine_mpc8315e-rdb ?= "f4d0900b2851e829e990e0f64b09ed3b8e355fae"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
index 7aba74061fe0..5c75e0311636 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
 SRCREV_machine_genericx86-64 ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_edgerouter ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_beaglebone ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_mpc8315e-rdb ?= "50e000bc5fce1e04a1a3aea5ffc57c3d5fd71e72"
+SRCREV_machine_edgerouter ?= "ca6a08bd7f86ebef11f763d26f787f7d65270473"
+SRCREV_machine_beaglebone ?= "ca6a08bd7f86ebef11f763d26f787f7d65270473"
+SRCREV_machine_mpc8315e-rdb ?= "7fa42ad9a43ca4bb1e578e208ffeddae2d6150e2"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.4.22"
 LINUX_VERSION_genericx86-64 = "4.4.22"
-LINUX_VERSION_edgerouter = "4.4.22"
-LINUX_VERSION_beaglebone = "4.4.22"
-LINUX_VERSION_mpc8315e-rdb = "4.4.22"
+LINUX_VERSION_edgerouter = "4.4.26"
+LINUX_VERSION_beaglebone = "4.4.26"
+LINUX_VERSION_mpc8315e-rdb = "4.4.26"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
index 331016b13167..051e15576d03 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
 SRCREV_machine_genericx86-64 ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_edgerouter ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_beaglebone ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_mpc8315e-rdb ?= "4c9e17100b1f8ce45a60ad8984c12b00febbc685"
+SRCREV_machine_edgerouter ?= "1adf9d36338dc3c63cdbf6f98bcbdc7bba42a794"
+SRCREV_machine_beaglebone ?= "1adf9d36338dc3c63cdbf6f98bcbdc7bba42a794"
+SRCREV_machine_mpc8315e-rdb ?= "4be88b03f6648004e74b68044fa2b05e81cf9a1b"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.8"
 LINUX_VERSION_genericx86-64 = "4.8"
-LINUX_VERSION_edgerouter = "4.8"
-LINUX_VERSION_beaglebone = "4.8"
-LINUX_VERSION_mpc8315e-rdb = "4.8"
+LINUX_VERSION_edgerouter = "4.8.3"
+LINUX_VERSION_beaglebone = "4.8.3"
+LINUX_VERSION_mpc8315e-rdb = "4.8.3"
-- 
2.9.3

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

[yocto] [PATCH] meta-yocto-bsp: linux-yocto: bump to the latest stable version for non-x86 BSPs

2016-10-26 Thread Kevin Hao 
Built and boot test for all these boards on 4.1, 4.4 and 4.8 kernels.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend |  6 +++---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 12 ++--
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | 12 ++--
 3 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index e6607c79f4fe..da6b21c6bdfe 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86?= "a38cb202738a2b055ac216b3699cc9377edea45a"
 SRCREV_machine_genericx86-64 ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
-SRCREV_machine_edgerouter ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
-SRCREV_machine_beaglebone ?= "3e064525c427e128d08ea599ea3247e2963b54a5"
-SRCREV_machine_mpc8315e-rdb ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
+SRCREV_machine_edgerouter ?= "f4d0900b2851e829e990e0f64b09ed3b8e355fae"
+SRCREV_machine_beaglebone ?= "12532e753b50997690923e03edb3ac3368817a26"
+SRCREV_machine_mpc8315e-rdb ?= "f4d0900b2851e829e990e0f64b09ed3b8e355fae"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
index 7aba74061fe0..5c75e0311636 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
 SRCREV_machine_genericx86-64 ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_edgerouter ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_beaglebone ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
-SRCREV_machine_mpc8315e-rdb ?= "50e000bc5fce1e04a1a3aea5ffc57c3d5fd71e72"
+SRCREV_machine_edgerouter ?= "ca6a08bd7f86ebef11f763d26f787f7d65270473"
+SRCREV_machine_beaglebone ?= "ca6a08bd7f86ebef11f763d26f787f7d65270473"
+SRCREV_machine_mpc8315e-rdb ?= "7fa42ad9a43ca4bb1e578e208ffeddae2d6150e2"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.4.22"
 LINUX_VERSION_genericx86-64 = "4.4.22"
-LINUX_VERSION_edgerouter = "4.4.22"
-LINUX_VERSION_beaglebone = "4.4.22"
-LINUX_VERSION_mpc8315e-rdb = "4.4.22"
+LINUX_VERSION_edgerouter = "4.4.26"
+LINUX_VERSION_beaglebone = "4.4.26"
+LINUX_VERSION_mpc8315e-rdb = "4.4.26"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
index 331016b13167..051e15576d03 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
 SRCREV_machine_genericx86-64 ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_edgerouter ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_beaglebone ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_mpc8315e-rdb ?= "4c9e17100b1f8ce45a60ad8984c12b00febbc685"
+SRCREV_machine_edgerouter ?= "1adf9d36338dc3c63cdbf6f98bcbdc7bba42a794"
+SRCREV_machine_beaglebone ?= "1adf9d36338dc3c63cdbf6f98bcbdc7bba42a794"
+SRCREV_machine_mpc8315e-rdb ?= "4be88b03f6648004e74b68044fa2b05e81cf9a1b"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.8"
 LINUX_VERSION_genericx86-64 = "4.8"
-LINUX_VERSION_edgerouter = "4.8"
-LINUX_VERSION_beaglebone = "4.8"
-LINUX_VERSION_mpc8315e-rdb = "4.8"
+LINUX_VERSION_edgerouter = "4.8.3"
+LINUX_VERSION_beaglebone = "4.8.3"
+LINUX_VERSION_mpc8315e-rdb = "4.8.3"
-- 
2.9.3

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

[yocto] [PATCH 3/3] meta-yocto-bsp: linux 4.4: bump to the latest stable version for non-x86 BSPs

2016-10-08 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
index 1ff5725b8e13..34cdbaf8749c 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
 SRCREV_machine_genericx86-64 ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
-SRCREV_machine_edgerouter ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
-SRCREV_machine_beaglebone ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
-SRCREV_machine_mpc8315e-rdb ?= "2d7b24e9c0d40d8317a0b9e1b0eefb8280e50d5f"
+SRCREV_machine_edgerouter ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
+SRCREV_machine_beaglebone ?= "f4e52341c304e044dbe581a35aad6b930c9410d1"
+SRCREV_machine_mpc8315e-rdb ?= "50e000bc5fce1e04a1a3aea5ffc57c3d5fd71e72"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.4.20"
 LINUX_VERSION_genericx86-64 = "4.4.20"
-LINUX_VERSION_edgerouter = "4.4.20"
-LINUX_VERSION_beaglebone = "4.4.20"
-LINUX_VERSION_mpc8315e-rdb = "4.4.20"
+LINUX_VERSION_edgerouter = "4.4.22"
+LINUX_VERSION_beaglebone = "4.4.22"
+LINUX_VERSION_mpc8315e-rdb = "4.4.22"
-- 
2.9.3

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

[yocto] [PATCH 2/3] meta-yocto-bsp: linux 4.1: bump to the latest stable version for non-x86 BSPs

2016-10-08 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index d97641411217..0451b8172b22 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86?= "a6b3a8cc120640bf5e528c8558ce060675757fc1"
 SRCREV_machine_genericx86-64 ?= "a6b3a8cc120640bf5e528c8558ce060675757fc1"
-SRCREV_machine_edgerouter ?= "a6b3a8cc120640bf5e528c8558ce060675757fc1"
-SRCREV_machine_beaglebone ?= "2ccca89503ed8c3f37b486b29d2ec3a6699f1899"
-SRCREV_machine_mpc8315e-rdb ?= "a6b3a8cc120640bf5e528c8558ce060675757fc1"
+SRCREV_machine_edgerouter ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
+SRCREV_machine_beaglebone ?= "3e064525c427e128d08ea599ea3247e2963b54a5"
+SRCREV_machine_mpc8315e-rdb ?= "a38cb202738a2b055ac216b3699cc9377edea45a"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.1.32"
 LINUX_VERSION_genericx86-64 = "4.1.32"
-LINUX_VERSION_edgerouter = "4.1.32"
-LINUX_VERSION_beaglebone = "4.1.32"
-LINUX_VERSION_mpc8315e-rdb = "4.1.32"
+LINUX_VERSION_edgerouter = "4.1.33"
+LINUX_VERSION_beaglebone = "4.1.33"
+LINUX_VERSION_mpc8315e-rdb = "4.1.33"
-- 
2.9.3

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

[yocto] [PATCH 1/3] meta-yocto-bsp: linux 4.8: bump to the final v4.8 release for non-x86 BSPs

2016-10-08 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
index f42b274c5a35..331016b13167 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
 SRCREV_machine_genericx86-64 ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_edgerouter ?= "eb9c19c72d40a4bb8a6a3b7b949e41e5c31c0d94"
-SRCREV_machine_beaglebone ?= "eb9c19c72d40a4bb8a6a3b7b949e41e5c31c0d94"
-SRCREV_machine_mpc8315e-rdb ?= "b5c48c7a5d6473373fe7f1e2e8d7b0cf57929908"
+SRCREV_machine_edgerouter ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
+SRCREV_machine_beaglebone ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
+SRCREV_machine_mpc8315e-rdb ?= "4c9e17100b1f8ce45a60ad8984c12b00febbc685"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.8"
 LINUX_VERSION_genericx86-64 = "4.8"
-LINUX_VERSION_edgerouter = "4.8-rc7"
-LINUX_VERSION_beaglebone = "4.8-rc7"
-LINUX_VERSION_mpc8315e-rdb = "4.8-rc7"
+LINUX_VERSION_edgerouter = "4.8"
+LINUX_VERSION_beaglebone = "4.8"
+LINUX_VERSION_mpc8315e-rdb = "4.8"
-- 
2.9.3

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

[linux-yocto] [PATCH 1/3] meta-yocto-bsp: linux 4.8: bump to the final v4.8 release for non-x86 BSPs

2016-10-08 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
index f42b274c5a35..331016b13167 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
 SRCREV_machine_genericx86-64 ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
-SRCREV_machine_edgerouter ?= "eb9c19c72d40a4bb8a6a3b7b949e41e5c31c0d94"
-SRCREV_machine_beaglebone ?= "eb9c19c72d40a4bb8a6a3b7b949e41e5c31c0d94"
-SRCREV_machine_mpc8315e-rdb ?= "b5c48c7a5d6473373fe7f1e2e8d7b0cf57929908"
+SRCREV_machine_edgerouter ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
+SRCREV_machine_beaglebone ?= "67813e7efa3a4614e209c2f058d92ef9a636441a"
+SRCREV_machine_mpc8315e-rdb ?= "4c9e17100b1f8ce45a60ad8984c12b00febbc685"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,6 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.8"
 LINUX_VERSION_genericx86-64 = "4.8"
-LINUX_VERSION_edgerouter = "4.8-rc7"
-LINUX_VERSION_beaglebone = "4.8-rc7"
-LINUX_VERSION_mpc8315e-rdb = "4.8-rc7"
+LINUX_VERSION_edgerouter = "4.8"
+LINUX_VERSION_beaglebone = "4.8"
+LINUX_VERSION_mpc8315e-rdb = "4.8"
-- 
2.9.3

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

Re: [linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: remove the stale kernel options

2016-10-08 Thread Kevin Hao 
On Sat, Oct 08, 2016 at 03:36:34PM +0800, Kevin Hao wrote:
> On Tue, Sep 20, 2016 at 08:00:25PM +0800, Kevin Hao wrote:
> > The kernel_configcheck complains about these unnecessary kernel options.
> > The final .config is the same with or without them.
> 
> Hi Bruce,
> 
> It seems that you missed this patch for the linux 4.1 kernel-meta.

Sorry for the typo. Should be linux 4.4.

Thanks,
Kevin


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

Re: [linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: remove the stale kernel options

2016-10-08 Thread Kevin Hao 
On Tue, Sep 20, 2016 at 08:00:25PM +0800, Kevin Hao wrote:
> The kernel_configcheck complains about these unnecessary kernel options.
> The final .config is the same with or without them.

Hi Bruce,

It seems that you missed this patch for the linux 4.1 kernel-meta.

Thanks,
Kevin

> 
> Signed-off-by: Kevin Hao <kexin@windriver.com>
> ---
>  bsp/beaglebone/beaglebone.cfg | 8 
>  1 file changed, 8 deletions(-)
> 
> diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
> index a6fe6d33d586..4c786d0afbef 100644
> --- a/bsp/beaglebone/beaglebone.cfg
> +++ b/bsp/beaglebone/beaglebone.cfg
> @@ -229,7 +229,6 @@ CONFIG_FB_CFB_FILLRECT=y
>  CONFIG_FB_CFB_COPYAREA=y
>  CONFIG_FB_CFB_IMAGEBLIT=y
>  # CONFIG_FB_FOREIGN_ENDIAN is not set
> -# CONFIG_FB_SYS_FOPS is not set
>  # CONFIG_FB_SVGALIB is not set
>  # CONFIG_FB_MACMODES is not set
>  # CONFIG_FB_BACKLIGHT is not set
> @@ -240,26 +239,19 @@ CONFIG_FB_TILEBLITTING=y
>  # Frame buffer hardware drivers
>  #
>  # CONFIG_FB_S1D13XXX is not set
> -# CONFIG_FB_TMIO is not set
>  # CONFIG_FB_VIRTUAL is not set
>  # CONFIG_FB_METRONOME is not set
> -# CONFIG_FB_MB862XX is not set
>  # CONFIG_FB_BROADSHEET is not set
>  # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
>  # CONFIG_FB_DA8XX is not set
>  # CONFIG_FB_DA8XX_TDA998X is not set
> -CONFIG_OMAP2_VRFB=y
>  CONFIG_OMAP2_DSS=y
> -# CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set
>  CONFIG_OMAP2_DSS_DPI=y
> -# CONFIG_OMAP2_DSS_RFBI is not set
>  CONFIG_OMAP2_DSS_VENC=y
>  # CONFIG_OMAP2_DSS_SDI is not set
>  CONFIG_OMAP2_DSS_DSI=y
>  # CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
>  CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
> -CONFIG_FB_OMAP2=y
> -CONFIG_FB_OMAP2_NUM_FBS=3
>  
>  #
>  # OMAP Display Device Drivers (new device model)
> -- 
> 2.9.3
> 


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

[linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: linux-4.1: remove the stale kernel options

2016-09-20 Thread Kevin Hao 
The kernel_configcheck complains about these unnecessary kernel options.
The final .config is the same with or without them.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 bsp/beaglebone/beaglebone.cfg | 4 
 1 file changed, 4 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index 781ecfc27901..38c7c0a5390d 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -239,19 +239,15 @@ CONFIG_FB_TILEBLITTING=y
 # Frame buffer hardware drivers
 #
 # CONFIG_FB_S1D13XXX is not set
-# CONFIG_FB_TMIO is not set
 # CONFIG_FB_VIRTUAL is not set
 # CONFIG_FB_METRONOME is not set
-# CONFIG_FB_MB862XX is not set
 # CONFIG_FB_BROADSHEET is not set
 # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
 # CONFIG_FB_DA8XX is not set
 # CONFIG_FB_DA8XX_TDA998X is not set
 CONFIG_OMAP2_VRFB=y
 CONFIG_OMAP2_DSS=y
-# CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set
 CONFIG_OMAP2_DSS_DPI=y
-# CONFIG_OMAP2_DSS_RFBI is not set
 CONFIG_OMAP2_DSS_VENC=y
 # CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
-- 
2.9.3

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

[linux-yocto] [meta-yocto-bsp] meta-yocto-bsp: linux 4.1: bump to the latest stable version for the non-x86 BSPs

2016-09-20 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index 6dd173bf423f..08ee6b1aedbe 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -9,9 +9,9 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
 SRCREV_machine_genericx86-64 ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_machine_edgerouter ?= "403eda4633e9037fb715d0d1e8ae847b2bd0651a"
-SRCREV_machine_beaglebone ?= "859aecf685fcd9d30490a6da459fb76b48947075"
-SRCREV_machine_mpc8315e-rdb ?= "403eda4633e9037fb715d0d1e8ae847b2bd0651a"
+SRCREV_machine_edgerouter ?= "0ef90071ef474c4140824cfb3680321526998319"
+SRCREV_machine_beaglebone ?= "36435f6cbd7423a612127700e3ded252d3f60804"
+SRCREV_machine_mpc8315e-rdb ?= "0ef90071ef474c4140824cfb3680321526998319"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,3 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.1.30"
 LINUX_VERSION_genericx86-64 = "4.1.30"
+LINUX_VERSION_edgerouter = "4.1.32"
+LINUX_VERSION_beaglebone = "4.1.32"
+LINUX_VERSION_mpc8315e-rdb = "4.1.32"
-- 
2.9.3

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

[linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: remove the stale kernel options

2016-09-20 Thread Kevin Hao 
The kernel_configcheck complains about these unnecessary kernel options.
The final .config is the same with or without them.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 bsp/beaglebone/beaglebone.cfg | 8 
 1 file changed, 8 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index a6fe6d33d586..4c786d0afbef 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -229,7 +229,6 @@ CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
 # CONFIG_FB_FOREIGN_ENDIAN is not set
-# CONFIG_FB_SYS_FOPS is not set
 # CONFIG_FB_SVGALIB is not set
 # CONFIG_FB_MACMODES is not set
 # CONFIG_FB_BACKLIGHT is not set
@@ -240,26 +239,19 @@ CONFIG_FB_TILEBLITTING=y
 # Frame buffer hardware drivers
 #
 # CONFIG_FB_S1D13XXX is not set
-# CONFIG_FB_TMIO is not set
 # CONFIG_FB_VIRTUAL is not set
 # CONFIG_FB_METRONOME is not set
-# CONFIG_FB_MB862XX is not set
 # CONFIG_FB_BROADSHEET is not set
 # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
 # CONFIG_FB_DA8XX is not set
 # CONFIG_FB_DA8XX_TDA998X is not set
-CONFIG_OMAP2_VRFB=y
 CONFIG_OMAP2_DSS=y
-# CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set
 CONFIG_OMAP2_DSS_DPI=y
-# CONFIG_OMAP2_DSS_RFBI is not set
 CONFIG_OMAP2_DSS_VENC=y
 # CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
 # CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
-CONFIG_FB_OMAP2=y
-CONFIG_FB_OMAP2_NUM_FBS=3
 
 #
 # OMAP Display Device Drivers (new device model)
-- 
2.9.3

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

[linux-yocto] [kernel 6/6] MIPS: OCTEON: mangle-port: fix build failure with VDSO code

2016-09-20 Thread Kevin Hao 
From: Aaro Koskinen <aaro.koski...@iki.fi>

Patch got from https://patchwork.linux-mips.org/patch/14039/

Commit 1685ddbe35cd ("MIPS: Octeon: Changes to support readq()/writeq()
usage.") added bitwise shift operations that assume that unsigned long
is always 64-bits. This broke the build of VDSO code, as it gets compiled
also in "faked" 32-bit mode. Althought the failing inline functions are
never executed in 32-bit mode, they still need to pass the compilation.
Fix by using 64-bit types explicitly.

The patch fixes the following build failure:

  CC  arch/mips/vdso/gettimeofday-o32.o
In file included from los/git/devel/linux/arch/mips/include/asm/io.h:32:0,
 from los/git/devel/linux/arch/mips/include/asm/page.h:194,
 from los/git/devel/linux/arch/mips/vdso/vdso.h:26,
 from los/git/devel/linux/arch/mips/vdso/gettimeofday.c:11:
los/git/devel/linux/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h: In 
function '__should_swizzle_bits':
los/git/devel/linux/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h:19:40:
 error: right shift count >= width of type [-Werror=shift-count-overflow]
  unsigned long did = ((unsigned long)a >> 40) & 0xff;
^~

Fixes: 1685ddbe35cd ("MIPS: Octeon: Changes to support readq()/writeq() usage.")
Signed-off-by: Aaro Koskinen <aaro.koski...@iki.fi>
Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 arch/mips/include/asm/mach-cavium-octeon/mangle-port.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h 
b/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h
index 0cf5ac1f7245..8ff2cbdf2c3e 100644
--- a/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h
+++ b/arch/mips/include/asm/mach-cavium-octeon/mangle-port.h
@@ -15,8 +15,8 @@
 static inline bool __should_swizzle_bits(volatile void *a)
 {
extern const bool octeon_should_swizzle_table[];
+   u64 did = ((u64)(uintptr_t)a >> 40) & 0xff;
 
-   unsigned long did = ((unsigned long)a >> 40) & 0xff;
return octeon_should_swizzle_table[did];
 }
 
@@ -29,7 +29,7 @@ static inline bool __should_swizzle_bits(volatile void *a)
 
 #define __should_swizzle_bits(a)   false
 
-static inline bool __should_swizzle_addr(unsigned long p)
+static inline bool __should_swizzle_addr(u64 p)
 {
/* boot bus? */
return ((p >> 40) & 0xff) == 0;
-- 
2.9.3

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

[linux-yocto] [meta-yocto-bsp] meta-yocto-bsp: linux 4.4: bump to the latest stable version for the non-x86 BSPs

2016-09-20 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
index 4a7f7e25f55b..50006e409c69 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
@@ -9,9 +9,9 @@ KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "0a0c93f29c0d65c00abdd2f6d1eb89134fae9525"
 SRCREV_machine_genericx86-64 ?= "0a0c93f29c0d65c00abdd2f6d1eb89134fae9525"
-SRCREV_machine_edgerouter ?= "628bf627561c6285d99fb978e11d4c15fc29324b"
-SRCREV_machine_beaglebone ?= "628bf627561c6285d99fb978e11d4c15fc29324b"
-SRCREV_machine_mpc8315e-rdb ?= "94ac8da44990afd2d43c0ccd713420fb1cfa0792"
+SRCREV_machine_edgerouter ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_beaglebone ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_mpc8315e-rdb ?= "2d7b24e9c0d40d8317a0b9e1b0eefb8280e50d5f"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -21,3 +21,6 @@ COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.4.18"
 LINUX_VERSION_genericx86-64 = "4.4.18"
+LINUX_VERSION_edgerouter = "4.4.20"
+LINUX_VERSION_beaglebone = "4.4.20"
+LINUX_VERSION_mpc8315e-rdb = "4.4.20"
-- 
2.9.3

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

[linux-yocto] [kernel 5/6] fs: yaffs2: fix the wrong check of return value of dir_emit()

2016-09-20 Thread Kevin Hao 
Fix the following build warning:
fs/yaffs2/yaffs_vfs.c:1788:34: warning: comparison of constant '0' with boolean 
expression is always false [-Wbool-compare]
   this_inode, this_type) < 0) {

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index f3efeb0ad4e0..5a9c295aecc8 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1785,7 +1785,7 @@ static int yaffs_readdir(struct file *file, struct 
dir_context *ctx)
yaffs_gross_unlock(dev);
 
if (!dir_emit(ctx, name, strlen(name),
- this_inode, this_type) < 0) {
+ this_inode, this_type)) {
yaffs_gross_lock(dev);
goto out;
}
-- 
2.9.3

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

[linux-yocto] [kernel 4/6] fs: yaffs2: kill ->put_link()

2016-09-20 Thread Kevin Hao 
As What we have done in commit fceef393a538 ("switch ->get_link()
to delayed_call, kill ->put_link()")

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 12 ++--
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index b57d612808de..f3efeb0ad4e0 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1060,7 +1060,7 @@ static int yaffs_readlink(struct dentry *dentry, char 
__user * buffer,
 
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
 static const char *yaffs_get_link(struct dentry *dentry, struct inode *inode,
- void **cookie)
+ struct delayed_call *done)
 {
void *ret;
 #else
@@ -1086,7 +1086,7 @@ static int yaffs_follow_link(struct dentry *dentry, 
struct nameidata *nd)
goto out;
}
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
-   *cookie = alias;
+   set_delayed_call(done, kfree_link, alias);
ret = alias;
 out:
if (ret_int)
@@ -1117,18 +1117,10 @@ static void yaffs_put_inode(struct inode *inode)
 }
 #endif
 
-#if (YAFFS_NEW_FOLLOW_LINK == 1)
-void yaffs_put_link(struct inode *inode, void *cookie)
-{
-   kfree(cookie);
-}
-#endif
-
 static const struct inode_operations yaffs_symlink_inode_operations = {
.readlink = yaffs_readlink,
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
.get_link = yaffs_get_link,
-   .put_link = yaffs_put_link,
 #else
.follow_link = yaffs_follow_link,
 #endif
-- 
2.9.3

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

[linux-yocto] [kernel 3/6] fs: yaffs2: replace ->follow_link() with -->get_link()

2016-09-20 Thread Kevin Hao 
As what we done in commit 6b2553918d8b ("replace ->follow_link()
with new method that could stay in RCU mode").

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 13 ++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index cd387d7abfa2..b57d612808de 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1059,7 +1059,8 @@ static int yaffs_readlink(struct dentry *dentry, char 
__user * buffer,
 }
 
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
-static const char *yaffs_follow_link(struct dentry *dentry, void **cookie)
+static const char *yaffs_get_link(struct dentry *dentry, struct inode *inode,
+ void **cookie)
 {
void *ret;
 #else
@@ -1069,8 +1070,12 @@ static int yaffs_follow_link(struct dentry *dentry, 
struct nameidata *nd)
 #endif
unsigned char *alias;
int ret_int = 0;
-   struct yaffs_dev *dev = yaffs_dentry_to_obj(dentry)->my_dev;
+   struct yaffs_dev *dev;
+
+   if (!dentry)
+   return ERR_PTR(-ECHILD);
 
+   dev = yaffs_dentry_to_obj(dentry)->my_dev;
yaffs_gross_lock(dev);
 
alias = yaffs_get_symlink_alias(yaffs_dentry_to_obj(dentry));
@@ -1121,9 +1126,11 @@ void yaffs_put_link(struct inode *inode, void *cookie)
 
 static const struct inode_operations yaffs_symlink_inode_operations = {
.readlink = yaffs_readlink,
-   .follow_link = yaffs_follow_link,
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
+   .get_link = yaffs_get_link,
.put_link = yaffs_put_link,
+#else
+   .follow_link = yaffs_follow_link,
 #endif
.setattr = yaffs_setattr,
.setxattr = yaffs_setxattr,
-- 
2.9.3

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

[linux-yocto] [kernel 2/6] fs: yaffs2: switch to the new prototype for ->set/getxattr()

2016-09-20 Thread Kevin Hao 
Since commit 3767e255b390 ("switch ->setxattr() to passing dentry and
inode separately") and commit ce23e6401334 ("->getxattr(): pass dentry
and inode as separate arguments"), a new inode argument has been added
for these two functions. Adjust these two functions to accommodate to
this change.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 9aa007d9ded6..cd387d7abfa2 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -919,10 +919,10 @@ static int yaffs_setattr(struct dentry *dentry, struct 
iattr *attr)
return error;
 }
 
-static int yaffs_setxattr(struct dentry *dentry, const char *name,
-  const void *value, size_t size, int flags)
+static int yaffs_setxattr(struct dentry *dentry, struct inode *inode,
+ const char *name, const void *value, size_t size,
+ int flags)
 {
-   struct inode *inode = dentry->d_inode;
int error = 0;
struct yaffs_dev *dev;
struct yaffs_obj *obj = yaffs_inode_to_obj(inode);
@@ -952,10 +952,9 @@ static int yaffs_setxattr(struct dentry *dentry, const 
char *name,
return error;
 }
 
-static ssize_t yaffs_getxattr(struct dentry * dentry, const char *name,
-   void *buff, size_t size)
+static ssize_t yaffs_getxattr(struct dentry * dentry, struct inode *inode,
+ const char *name, void *buff, size_t size)
 {
-   struct inode *inode = dentry->d_inode;
int error = 0;
struct yaffs_dev *dev;
struct yaffs_obj *obj = yaffs_inode_to_obj(inode);
-- 
2.9.3

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

[linux-yocto] [kernel 1/6] fs: yaffs2: kill PAGE_CACHE_* and page_cache_{get, release} macros

2016-09-20 Thread Kevin Hao 
As what we have done in commit 09cbfeaf1a5a ("mm, fs: get rid of
PAGE_CACHE_* and page_cache_{get,release} macros").

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 38 +++---
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 1494c8f33d20..9aa007d9ded6 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -266,13 +266,13 @@ static int yaffs_readpage_nolock(struct file *f, struct 
page *pg)
struct yaffs_obj *obj;
unsigned char *pg_buf;
int ret;
-   loff_t pos = ((loff_t) pg->index) << PAGE_CACHE_SHIFT;
+   loff_t pos = ((loff_t) pg->index) << PAGE_SHIFT;
struct yaffs_dev *dev;
 
yaffs_trace(YAFFS_TRACE_OS,
"yaffs_readpage_nolock at %lld, size %08x",
(long long)pos,
-   (unsigned)PAGE_CACHE_SIZE);
+   (unsigned)PAGE_SIZE);
 
obj = yaffs_dentry_to_obj(f->f_path.dentry);
 
@@ -290,7 +290,7 @@ static int yaffs_readpage_nolock(struct file *f, struct 
page *pg)
 
yaffs_gross_lock(dev);
 
-   ret = yaffs_file_rd(obj, pg_buf, pos, PAGE_CACHE_SIZE);
+   ret = yaffs_file_rd(obj, pg_buf, pos, PAGE_SIZE);
 
yaffs_gross_unlock(dev);
 
@@ -400,22 +400,22 @@ static int yaffs_writepage(struct page *page)
BUG();
i_size = i_size_read(inode);
 
-   end_index = i_size >> PAGE_CACHE_SHIFT;
+   end_index = i_size >> PAGE_SHIFT;
 
if (page->index < end_index)
-   n_bytes = PAGE_CACHE_SIZE;
+   n_bytes = PAGE_SIZE;
else {
-   n_bytes = i_size & (PAGE_CACHE_SIZE - 1);
+   n_bytes = i_size & (PAGE_SIZE - 1);
 
if (page->index > end_index || !n_bytes) {
yaffs_trace(YAFFS_TRACE_OS,
"yaffs_writepage at %lld, inode size = %lld!!",
-   ((loff_t)page->index) << PAGE_CACHE_SHIFT,
+   ((loff_t)page->index) << PAGE_SHIFT,
inode->i_size);
yaffs_trace(YAFFS_TRACE_OS,
"-> don't care!!");
 
-   zero_user_segment(page, 0, PAGE_CACHE_SIZE);
+   zero_user_segment(page, 0, PAGE_SIZE);
set_page_writeback(page);
unlock_page(page);
end_page_writeback(page);
@@ -423,8 +423,8 @@ static int yaffs_writepage(struct page *page)
}
}
 
-   if (n_bytes != PAGE_CACHE_SIZE)
-   zero_user_segment(page, n_bytes, PAGE_CACHE_SIZE);
+   if (n_bytes != PAGE_SIZE)
+   zero_user_segment(page, n_bytes, PAGE_SIZE);
 
get_page(page);
 
@@ -436,13 +436,13 @@ static int yaffs_writepage(struct page *page)
 
yaffs_trace(YAFFS_TRACE_OS,
"yaffs_writepage at %lld, size %08x",
-   ((loff_t)page->index) << PAGE_CACHE_SHIFT, n_bytes);
+   ((loff_t)page->index) << PAGE_SHIFT, n_bytes);
yaffs_trace(YAFFS_TRACE_OS,
"writepag0: obj = %lld, ino = %lld",
obj->variant.file_variant.file_size, inode->i_size);
 
n_written = yaffs_wr_file(obj, buffer,
- ((loff_t)page->index) << PAGE_CACHE_SHIFT, 
n_bytes, 0);
+ ((loff_t)page->index) << PAGE_SHIFT, n_bytes, 
0);
 
yaffs_set_super_dirty(dev);
 
@@ -505,7 +505,7 @@ static int yaffs_write_begin(struct file *filp, struct 
address_space *mapping,
 struct page **pagep, void **fsdata)
 {
struct page *pg = NULL;
-   pgoff_t index = pos >> PAGE_CACHE_SHIFT;
+   pgoff_t index = pos >> PAGE_SHIFT;
 
int ret = 0;
int space_held = 0;
@@ -554,7 +554,7 @@ out:
yaffs_release_space(filp);
if (pg) {
unlock_page(pg);
-   page_cache_release(pg);
+   put_page(pg);
}
return ret;
 }
@@ -638,7 +638,7 @@ static int yaffs_write_end(struct file *filp, struct 
address_space *mapping,
 {
int ret = 0;
void *addr, *kva;
-   uint32_t offset_into_page = pos & (PAGE_CACHE_SIZE - 1);
+   uint32_t offset_into_page = pos & (PAGE_SIZE - 1);
 
kva = kmap(pg);
addr = kva + offset_into_page;
@@ -660,7 +660,7 @@ static int yaffs_write_end(struct file *filp, struct 
address_space *mapping,
 
yaffs_release_space(filp);
unlock_page(pg);
-   page_cache_release(pg);
+   put_page(pg);
return ret;
 }
 #else
@@ -670,7 +670,7 @@ static int yaffs_commi

[linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: remove the stale kernel options

2016-09-20 Thread Kevin Hao 
The kernel_configcheck complains about these unnecessary kernel options.
The final .config is the same with or without them.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 bsp/beaglebone/beaglebone.cfg | 8 
 1 file changed, 8 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index a6fe6d33d586..4c786d0afbef 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -229,7 +229,6 @@ CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
 # CONFIG_FB_FOREIGN_ENDIAN is not set
-# CONFIG_FB_SYS_FOPS is not set
 # CONFIG_FB_SVGALIB is not set
 # CONFIG_FB_MACMODES is not set
 # CONFIG_FB_BACKLIGHT is not set
@@ -240,26 +239,19 @@ CONFIG_FB_TILEBLITTING=y
 # Frame buffer hardware drivers
 #
 # CONFIG_FB_S1D13XXX is not set
-# CONFIG_FB_TMIO is not set
 # CONFIG_FB_VIRTUAL is not set
 # CONFIG_FB_METRONOME is not set
-# CONFIG_FB_MB862XX is not set
 # CONFIG_FB_BROADSHEET is not set
 # CONFIG_FB_OMAP_BOOTLOADER_INIT is not set
 # CONFIG_FB_DA8XX is not set
 # CONFIG_FB_DA8XX_TDA998X is not set
-CONFIG_OMAP2_VRFB=y
 CONFIG_OMAP2_DSS=y
-# CONFIG_OMAP2_DSS_COLLECT_IRQ_STATS is not set
 CONFIG_OMAP2_DSS_DPI=y
-# CONFIG_OMAP2_DSS_RFBI is not set
 CONFIG_OMAP2_DSS_VENC=y
 # CONFIG_OMAP2_DSS_SDI is not set
 CONFIG_OMAP2_DSS_DSI=y
 # CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
 CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=0
-CONFIG_FB_OMAP2=y
-CONFIG_FB_OMAP2_NUM_FBS=3
 
 #
 # OMAP Display Device Drivers (new device model)
-- 
2.9.3

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

[linux-yocto] [meta-yocto-bsp] meta-yocto-bsp: bump to linux-yocto 4.8 for the non-x86 BSPs

2016-09-20 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/conf/machine/beaglebone.conf  |  2 +-
 meta-yocto-bsp/conf/machine/edgerouter.conf  |  2 +-
 meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf|  2 +-
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend | 12 
 4 files changed, 15 insertions(+), 3 deletions(-)

diff --git a/meta-yocto-bsp/conf/machine/beaglebone.conf 
b/meta-yocto-bsp/conf/machine/beaglebone.conf
index ea50accc2d8e..1b6c2dcd57f8 100644
--- a/meta-yocto-bsp/conf/machine/beaglebone.conf
+++ b/meta-yocto-bsp/conf/machine/beaglebone.conf
@@ -22,7 +22,7 @@ EXTRA_IMAGECMD_jffs2 = "-lnp "
 SERIAL_CONSOLE = "115200 ttyO0"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "4.4%"
+PREFERRED_VERSION_linux-yocto ?= "4.8%"
 
 KERNEL_IMAGETYPE = "zImage"
 KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb"
diff --git a/meta-yocto-bsp/conf/machine/edgerouter.conf 
b/meta-yocto-bsp/conf/machine/edgerouter.conf
index 6343dfc38c6d..cf521e91d5f5 100644
--- a/meta-yocto-bsp/conf/machine/edgerouter.conf
+++ b/meta-yocto-bsp/conf/machine/edgerouter.conf
@@ -11,7 +11,7 @@ KERNEL_ALT_IMAGETYPE = "vmlinux.bin"
 KERNEL_IMAGE_STRIP_EXTRA_SECTIONS  = ".comment"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "4.4%"
+PREFERRED_VERSION_linux-yocto ?= "4.8%"
 
 SERIAL_CONSOLE = "115200 ttyS0"
 USE_VT ?= "0"
diff --git a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf 
b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
index 1e7de09a4667..a2ff07c552d6 100644
--- a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
@@ -14,7 +14,7 @@ SERIAL_CONSOLE = "115200 ttyS0"
 
 MACHINE_FEATURES = "keyboard pci ext2 ext3 serial"
 
-PREFERRED_VERSION_linux-yocto ?= "4.4%"
+PREFERRED_VERSION_linux-yocto ?= "4.8%"
 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
 
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
index efa11cb209be..4363b17aee6c 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.8.bbappend
@@ -3,12 +3,24 @@ KBRANCH_genericx86-64  = "standard/base"
 
 KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
+KBRANCH_edgerouter = "standard/edgerouter"
+KBRANCH_beaglebone = "standard/beaglebone"
+KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 SRCREV_machine_genericx86?= "a7d71794e4e38d2f861c1b1dbff761ae0b0836b3"
 SRCREV_machine_genericx86-64 ?= "a7d71794e4e38d2f861c1b1dbff761ae0b0836b3"
+SRCREV_machine_edgerouter ?= "cde1a7d656b7fdd96f82f619e4251965a4e96489"
+SRCREV_machine_beaglebone ?= "cde1a7d656b7fdd96f82f619e4251965a4e96489"
+SRCREV_machine_mpc8315e-rdb ?= "705fb8543ea6266b193a66e15fecd058c60183ea"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
+COMPATIBLE_MACHINE_edgerouter = "edgerouter"
+COMPATIBLE_MACHINE_beaglebone = "beaglebone"
+COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
 LINUX_VERSION_genericx86 = "4.8-rc4"
 LINUX_VERSION_genericx86-64 = "4.8-rc4"
+LINUX_VERSION_edgerouter = "4.8-rc7"
+LINUX_VERSION_beaglebone = "4.8-rc7"
+LINUX_VERSION_mpc8315e-rdb = "4.8-rc7"
-- 
2.9.3

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

[linux-yocto] bump to linux-yocto 4.8 for the non-x86 BSPs

2016-09-20 Thread Kevin Hao 
Hi,

This patch series fixes some build errors in linux-yocto 4.8 and bump
to 4.8 for all the non-x86 BSPs.
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] Getting USB devices to work on BeagleBoard Black

2016-07-11 Thread Kevin Hao 
On Mon, Jul 11, 2016 at 11:55:34AM +0530, shoaib md wrote:
> I've managed to build a couple of different recipes for my BeagleBoard
> (BeagleBoard Black Rev C), and also had a go at customising it.  I think
> I've tried core-image-minimal.

Could you check if the following patch is applied in your kernel-meta?

commit fca9cc2483de
Author: Kevin Hao <kexin@windriver.com>
Date:   Tue May 17 20:03:21 2016 +0800

beaglebone: builtin the usb controller drivers

In the current codes, we build the drivers for usb controller as
modules. But for some image types, such as minimal or full-cmdline,
these driver modules are not installed to the rootfs by default.
This makes the using of the usb pretty inconvenience. So make
them all builtin.

Reported-and-suggested-by: hiims <h...@101.org.il>
    Signed-off-by: Kevin Hao <kexin@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com>

Thanks,
Kevin


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

Re: [yocto] how to tftp download a newer u-boot into RAM and simply execute it?

2016-07-07 Thread Kevin Hao 
On Wed, Jul 06, 2016 at 03:37:04PM -0400, Bruce Ashfield wrote:
> > 
> >so, before i commit myself to this, who's the PPC/MPC8315E-RDB
> > expert on this list who can confirm a stock u-boot should flash to NOR
> > and just plain run?

The ramboot is not supported for this board in u-boot. There do have some
codes about ramboot in the startup code, but you can't expect it to work
without some tweaking.

Thanks,
Kevin


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

[linux-yocto] [PATCH linux-yocto 4.4] beaglebone: builtin the usb controller drivers

2016-05-17 Thread Kevin Hao 
In the current codes, we build the drivers for usb controller as
modules. But for some image types, such as minimal or full-cmdline,
these driver modules are not installed to the rootfs by default.
This makes the using of the usb pretty inconvenience. So make
them all builtin.

Reported-and-suggested-by: hiims <h...@101.org.il>
Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 bsp/beaglebone/beaglebone.cfg | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/bsp/beaglebone/beaglebone.cfg b/bsp/beaglebone/beaglebone.cfg
index 66a6361..a6fe6d3 100644
--- a/bsp/beaglebone/beaglebone.cfg
+++ b/bsp/beaglebone/beaglebone.cfg
@@ -314,10 +314,10 @@ CONFIG_USB_SUPPORT=y
 CONFIG_USB_EHCI_HCD=y
 CONFIG_USB_EHCI_TT_NEWSCHED=y
 CONFIG_USB_EHCI_HCD_OMAP=y
-CONFIG_USB_MUSB_HDRC=m
-CONFIG_USB_MUSB_OMAP2PLUS=m
-CONFIG_USB_MUSB_DSPS=m
-CONFIG_USB_MUSB_AM335X_CHILD=m
+CONFIG_USB_MUSB_HDRC=y
+CONFIG_USB_MUSB_OMAP2PLUS=y
+CONFIG_USB_MUSB_DSPS=y
+CONFIG_USB_MUSB_AM335X_CHILD=y
 CONFIG_USB_TI_CPPI41_DMA=y
 
 #
-- 
2.8.1

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

[linux-yocto] [PATCH 2/3] yaffs2: NULL ->read/->write

2016-02-23 Thread Kevin Hao 
As stated in commit 5d5d56897530 ("make new_sync_{read,write}() static"),
we shouldn't use new_sync_{read_write} for ->read/->write. We should
NULL ->read/->write with non-NULL ->{read,write}_iter will do the
right thing.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index fbbf313..0a3e9da 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -794,8 +794,6 @@ static int yaffs_sync_object(struct file *file, struct 
dentry *dentry,
 
 #if (LINUX_VERSION_CODE > KERNEL_VERSION(2, 6, 22))
 static const struct file_operations yaffs_file_operations = {
-   .read = new_sync_read,
-   .write = new_sync_write,
.read_iter = generic_file_read_iter,
.write_iter = generic_file_write_iter,
.mmap = generic_file_mmap,
-- 
1.9.1

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

[linux-yocto] [PATCH 3/3] yaffs2: using new ->follow_link() and ->put_link() calling conventions

2016-02-23 Thread Kevin Hao 
As what we did in commit 680baacbca69 ("new ->follow_link() and
->put_link() calling conventions").

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 fs/yaffs2/yaffs_vfs.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 0a3e9da..1494c8f 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -1060,7 +1060,7 @@ static int yaffs_readlink(struct dentry *dentry, char 
__user * buffer,
 }
 
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
-static void *yaffs_follow_link(struct dentry *dentry, struct nameidata *nd)
+static const char *yaffs_follow_link(struct dentry *dentry, void **cookie)
 {
void *ret;
 #else
@@ -1082,7 +1082,7 @@ static int yaffs_follow_link(struct dentry *dentry, 
struct nameidata *nd)
goto out;
}
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
-   nd_set_link(nd, alias);
+   *cookie = alias;
ret = alias;
 out:
if (ret_int)
@@ -1114,9 +1114,9 @@ static void yaffs_put_inode(struct inode *inode)
 #endif
 
 #if (YAFFS_NEW_FOLLOW_LINK == 1)
-void yaffs_put_link(struct dentry *dentry, struct nameidata *nd, void *alias)
+void yaffs_put_link(struct inode *inode, void *cookie)
 {
-   kfree(alias);
+   kfree(cookie);
 }
 #endif
 
-- 
1.9.1

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

[linux-yocto] [PATCH 1/3] yaffs2: replace f_dentry to f_path.dentry

2016-02-23 Thread Kevin Hao 
From: Yang Shi 

Upstream commit 78d28e651f97866d608d9b41f8ad291e65d47dd5 ("kill f_dentry macro")
removed f_dentry from struct file, so replace it to f_path.dentry to fix the
build failure.

Signed-off-by: Yang Shi 
Signed-off-by: Bruce Ashfield 
---
This is picked from linux-yocto 4.1.

 fs/yaffs2/yaffs_vfs.c | 26 +-
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index a84e57e..fbbf313 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -274,7 +274,7 @@ static int yaffs_readpage_nolock(struct file *f, struct 
page *pg)
(long long)pos,
(unsigned)PAGE_CACHE_SIZE);
 
-   obj = yaffs_dentry_to_obj(f->f_dentry);
+   obj = yaffs_dentry_to_obj(f->f_path.dentry);
 
dev = obj->my_dev;
 
@@ -472,7 +472,7 @@ static ssize_t yaffs_hold_space(struct file *f)
 
int n_free_chunks;
 
-   obj = yaffs_dentry_to_obj(f->f_dentry);
+   obj = yaffs_dentry_to_obj(f->f_path.dentry);
 
dev = obj->my_dev;
 
@@ -490,7 +490,7 @@ static void yaffs_release_space(struct file *f)
struct yaffs_obj *obj;
struct yaffs_dev *dev;
 
-   obj = yaffs_dentry_to_obj(f->f_dentry);
+   obj = yaffs_dentry_to_obj(f->f_path.dentry);
 
dev = obj->my_dev;
 
@@ -582,7 +582,7 @@ static ssize_t yaffs_file_write(struct file *f, const char 
*buf, size_t n,
struct inode *inode;
struct yaffs_dev *dev;
 
-   obj = yaffs_dentry_to_obj(f->f_dentry);
+   obj = yaffs_dentry_to_obj(f->f_path.dentry);
 
if (!obj) {
yaffs_trace(YAFFS_TRACE_OS,
@@ -594,7 +594,7 @@ static ssize_t yaffs_file_write(struct file *f, const char 
*buf, size_t n,
 
yaffs_gross_lock(dev);
 
-   inode = f->f_dentry->d_inode;
+   inode = f->f_path.dentry->d_inode;
 
if (!S_ISBLK(inode->i_mode) && f->f_flags & O_APPEND)
ipos = inode->i_size;
@@ -745,7 +745,7 @@ static int yaffs_file_flush(struct file *file, fl_owner_t 
id)
 static int yaffs_file_flush(struct file *file)
 #endif
 {
-   struct yaffs_obj *obj = yaffs_dentry_to_obj(file->f_dentry);
+   struct yaffs_obj *obj = yaffs_dentry_to_obj(file->f_path.dentry);
 
struct yaffs_dev *dev = obj->my_dev;
 
@@ -1712,14 +1712,14 @@ static int yaffs_readdir(struct file *file, struct 
dir_context *ctx)
struct yaffs_obj *obj;
struct yaffs_dev *dev;
struct yaffs_search_context *sc;
-   struct inode *inode = file->f_dentry->d_inode;
+   struct inode *inode = file->f_path.dentry->d_inode;
unsigned long offset, curoffs;
struct yaffs_obj *l;
int ret_val = 0;
 
char name[YAFFS_MAX_NAME_LENGTH + 1];
 
-   obj = yaffs_dentry_to_obj(file->f_dentry);
+   obj = yaffs_dentry_to_obj(file->f_path.dentry);
dev = obj->my_dev;
 
yaffs_gross_lock(dev);
@@ -1753,7 +1753,7 @@ static int yaffs_readdir(struct file *file, struct 
dir_context *ctx)
if (offset == 1) {
yaffs_trace(YAFFS_TRACE_OS,
"yaffs_readdir: entry .. ino %d",
-   (int)file->f_dentry->d_parent->d_inode->i_ino);
+   (int)file->f_path.dentry->d_parent->d_inode->i_ino);
yaffs_gross_unlock(dev);
if (!dir_emit_dotdot(file, ctx)) {
yaffs_gross_lock(dev);
@@ -1815,14 +1815,14 @@ static int yaffs_readdir(struct file *f, void *dirent, 
filldir_t filldir)
struct yaffs_obj *obj;
struct yaffs_dev *dev;
struct yaffs_search_context *sc;
-   struct inode *inode = f->f_dentry->d_inode;
+   struct inode *inode = f->f_path.dentry->d_inode;
unsigned long offset, curoffs;
struct yaffs_obj *l;
int ret_val = 0;
 
char name[YAFFS_MAX_NAME_LENGTH + 1];
 
-   obj = yaffs_dentry_to_obj(f->f_dentry);
+   obj = yaffs_dentry_to_obj(f->f_path.dentry);
dev = obj->my_dev;
 
yaffs_gross_lock(dev);
@@ -1856,10 +1856,10 @@ static int yaffs_readdir(struct file *f, void *dirent, 
filldir_t filldir)
if (offset == 1) {
yaffs_trace(YAFFS_TRACE_OS,
"yaffs_readdir: entry .. ino %d",
-   (int)f->f_dentry->d_parent->d_inode->i_ino);
+   (int)f->f_path.dentry->d_parent->d_inode->i_ino);
yaffs_gross_unlock(dev);
if (filldir(dirent, "..", 2, offset,
-   f->f_dentry->d_parent->d_inode->i_ino,
+   f->f_path.dentry->d_parent->d_inode->i_ino,
DT_DIR) < 0) {
yaffs_gross_lock(dev);
goto out;
-- 
1.9.1

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org

[linux-yocto] [PATCH 0/3] linux-yocto 4.4: fix the build errors when yaffs2 is enabled

2016-02-23 Thread Kevin Hao 
Hi,

With these patches applied, we can use a yaffs2 rootfs on mpc8315e-rdb board:
  root@mpc8315e-rdb:~# cat /proc/version 
  Linux version 4.4.1-yocto-standard (khao@pek-lpggp4) (gcc version 5.3.0 (GCC) 
) #2 PREEMPT Wed Feb 24 10:30:40 CST 2016
  root@mpc8315e-rdb:~# cat /proc/cmdline
  root=/dev/mtdblock3 rootfstype=yaffs2 console=ttyS0,115200
  root@mpc8315e-rdb:~# mount
  /dev/root on / type yaffs2 (rw,relatime)

Kevin Hao (2):
  yaffs2: NULL ->read/->write
  yaffs2: using new ->follow_link() and ->put_link() calling conventions

Yang Shi (1):
  yaffs2: replace f_dentry to f_path.dentry

 fs/yaffs2/yaffs_vfs.c | 36 +---
 1 file changed, 17 insertions(+), 19 deletions(-)

-- 
1.9.1

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

[linux-yocto] [PATCH] meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPs

2015-09-29 Thread Kevin Hao 
Boot test for all these boards.

Signed-off-by: Kevin Hao <kexin@windriver.com>
---
 meta-yocto-bsp/conf/machine/beaglebone.conf  | 2 +-
 meta-yocto-bsp/conf/machine/edgerouter.conf  | 2 +-
 meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf| 2 +-
 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 9 +
 4 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/meta-yocto-bsp/conf/machine/beaglebone.conf 
b/meta-yocto-bsp/conf/machine/beaglebone.conf
index 0daebf3..ff46fb2 100644
--- a/meta-yocto-bsp/conf/machine/beaglebone.conf
+++ b/meta-yocto-bsp/conf/machine/beaglebone.conf
@@ -22,7 +22,7 @@ EXTRA_IMAGECMD_jffs2 = "-lnp "
 SERIAL_CONSOLE = "115200 ttyO0"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "3.19%"
+PREFERRED_VERSION_linux-yocto ?= "4.1%"
 
 KERNEL_IMAGETYPE = "zImage"
 KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb"
diff --git a/meta-yocto-bsp/conf/machine/edgerouter.conf 
b/meta-yocto-bsp/conf/machine/edgerouter.conf
index 45ef237..476e690 100644
--- a/meta-yocto-bsp/conf/machine/edgerouter.conf
+++ b/meta-yocto-bsp/conf/machine/edgerouter.conf
@@ -11,7 +11,7 @@ KERNEL_ALT_IMAGETYPE = "vmlinux.bin"
 KERNEL_IMAGE_STRIP_EXTRA_SECTIONS  = ".comment"
 
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ?= "3.19%"
+PREFERRED_VERSION_linux-yocto ?= "4.1%"
 
 SERIAL_CONSOLE = "115200 ttyS0"
 USE_VT ?= "0"
diff --git a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf 
b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
index 2beef48..036b05f 100644
--- a/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf
@@ -14,7 +14,7 @@ SERIAL_CONSOLE = "115200 ttyS0"
 
 MACHINE_FEATURES = "keyboard pci ext2 ext3 serial"
 
-PREFERRED_VERSION_linux-yocto ?= "3.19%"
+PREFERRED_VERSION_linux-yocto ?= "4.1%"
 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
 
 PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
index a5fe0e6..104d250 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend
@@ -1,11 +1,20 @@
 KBRANCH_genericx86  = "standard/base"
 KBRANCH_genericx86-64  = "standard/base"
+KBRANCH_edgerouter = "standard/edgerouter"
+KBRANCH_beaglebone = "standard/beaglebone"
+KBRANCH_mpc8315e-rdb = "standard/fsl-mpc8315e-rdb"
 
 KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 
 SRCREV_machine_genericx86 ?= "4e30e64c44df9e59bd13239951bb8d2b5b276e6f"
 SRCREV_machine_genericx86-64 ?= "4e30e64c44df9e59bd13239951bb8d2b5b276e6f"
+SRCREV_machine_edgerouter ?= "79a31b9d23db126f8a6be3eb88fd683056a213f1"
+SRCREV_machine_beaglebone ?= "efb6ffb2ca96a364f916c9890ad023fc595e0e6e"
+SRCREV_machine_mpc8315e-rdb ?= "79a31b9d23db126f8a6be3eb88fd683056a213f1"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
+COMPATIBLE_MACHINE_edgerouter = "edgerouter"
+COMPATIBLE_MACHINE_beaglebone = "beaglebone"
+COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
-- 
2.0.1

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

Re: [linux-yocto] [poky] [PATCH] meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPs

2015-09-29 Thread Kevin Hao 
On Tue, Sep 29, 2015 at 10:18:00AM -0700, Khem Raj wrote:
> 
> On Sep 29, 2015, at 3:01 AM, Burton, Ross <ross.bur...@intel.com> wrote:
> 
> 
> On 29 September 2015 at 10:42, Kevin Hao <kexin@windriver.com> wrote:
> 
> Boot test for all these boards.
> 
> 
> If I build the edgerouter kernel I get this warning:
> 
> WARNING: Section not found: .comment
> 
> I've no idea if this is bad or not…
> 
> 
> functionally no harm since its the strip code which is complaining about it so
> this section was going to go away from kernel image anyway
> it seems we must have included .comment in KERNEL_IMAGE_STRIP
> 
> Now the more curious case would be if its being stripped by kernel build, we
> explicitly disabled kernel build stripping the kernel image
> and here it might be thats not happening with new kernel. That aspect could be
> investigated.

Actually the warning is a bug in the do_strip() of kernel build. The vmlinux
image does have the .comment section, but the code that checking if the
.comment section is existed is wrong. Please see the following codes in
do_strip():

for str in ${KERNEL_IMAGE_STRIP_EXTRA_SECTIONS}; do {
if [ "$headers" != *"$str"* ]; then
bbwarn "Section not found: $str";
fi

"$CROSS_COMPILE"strip -s -R $str ${KERNEL_OUTPUT}
}; done


The "*" doesn't have special meaning in the if string test. So it will return
true even the $str is a substring of $headers. How about change the test to:

if ! (echo "$headers" | grep -q "^$str$"); then

Thanks,
Kevin


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

[linux-yocto] [PATCH] meta; edgerouter: fix kernel config check errors

2015-05-27 Thread Kevin Hao 
Fix the following kernel config check errors:
  Value requested for CONFIG_HW_RANDOM_OCTEON not in final .config
  Requested value: CONFIG_HW_RANDOM_OCTEON=y
  Actual value set: CONFIG_HW_RANDOM_OCTEON=m

  Value requested for CONFIG_USB_OCTEON_EHCI not in final .config
  Requested value: CONFIG_USB_OCTEON_EHCI=y
  Actual value set: 

  Value requested for CONFIG_USB_OCTEON_OHCI not in final .config
  Requested value: CONFIG_USB_OCTEON_OHCI=y
  Actual value set: 

Signed-off-by: Kevin Hao kexin@windriver.com
---
 meta/cfg/kernel-cache/bsp/edgerouter/edgerouter.cfg | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/cfg/kernel-cache/bsp/edgerouter/edgerouter.cfg 
b/meta/cfg/kernel-cache/bsp/edgerouter/edgerouter.cfg
index 9e5a6b65faca..54597416dde8 100644
--- a/meta/cfg/kernel-cache/bsp/edgerouter/edgerouter.cfg
+++ b/meta/cfg/kernel-cache/bsp/edgerouter/edgerouter.cfg
@@ -20,6 +20,7 @@ CONFIG_PCI_MSI=y
 CONFIG_I2C=y
 CONFIG_I2C_OCTEON=y
 
+CONFIG_HW_RANDOM=y
 CONFIG_HW_RANDOM_OCTEON=y
 
 #SPI
@@ -47,7 +48,9 @@ CONFIG_BCM87XX_PHY=y
 #USB
 CONFIG_USB=y
 CONFIG_OCTEON_USB=y
+CONFIG_USB_EHCI_HCD=y
 CONFIG_USB_OCTEON_EHCI=y
+CONFIG_USB_OHCI_HCD=y
 CONFIG_USB_OCTEON_OHCI=y
 CONFIG_USB_OCTEON2_COMMON=y
 
-- 
2.1.0

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

  1   2   >