[yocto] [meta-security][PATCH 1/2] tpm2-tss-engine: update 1.1.0
LIC_FILES_CHKSUM hash changed between branches.
Signed-off-by: Armin Kuster
---
.../{tpm2-tss-engine_1.0.1.bb => tpm2-tss-engine_1.1.0.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta-tpm/recipes-tpm2/tpm2-tss-engine/{tpm2-tss-engine_1.0.1.bb =>
tpm2-tss-engine_1.1.0.bb} (88%)
diff --git a/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb
b/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.1.0.bb
similarity index 88%
rename from meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb
rename to meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.1.0.bb
index ebd6d53..5395695 100644
--- a/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.0.1.bb
+++ b/meta-tpm/recipes-tpm2/tpm2-tss-engine/tpm2-tss-engine_1.1.0.bb
@@ -2,14 +2,14 @@ SUMMARY = "The tpm2-tss-engine project implements a
cryptographic engine for Ope
DESCRIPTION = "The tpm2-tss-engine project implements a cryptographic engine
for OpenSSL for Trusted Platform Module (TPM 2.0) using the tpm2-tss software
stack that follows the Trusted Computing Groups (TCG) TPM Software Stack (TSS
2.0). It uses the Enhanced System API (ESAPI) interface of the TSS 2.0 for
downwards communication. It supports RSA decryption and signatures as well as
ECDSA signatures."
LICENSE = "BSD-3-Clause"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=3fb0047fd29391478a71e8e6101c76eb"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=7b3ab643b9ce041de515d1ed092a36d4"
SECTION = "security/tpm"
DEPENDS = "autoconf-archive-native bash-completion libtss2 libgcrypt openssl"
-SRCREV = "24f1383cc6befde44d6f01a51ea653304d844ffd"
-SRC_URI = "git://github.com/tpm2-software/tpm2-tss-engine.git;branch=v1.0.x"
+SRCREV = "6f387a4efe2049f1b4833e8f621c77231bc1eef4"
+SRC_URI = "git://github.com/tpm2-software/tpm2-tss-engine.git;branch=v1.1.x"
inherit autotools-brokensep pkgconfig systemd
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52778): https://lists.yoctoproject.org/g/yocto/message/52778
Mute This Topic: https://lists.yoctoproject.org/mt/81465579/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-security][PATCH 2/2] swtpm: update to 0.5.2
Add python package
Signed-off-by: Armin Kuster
---
.../swtpm/{swtpm_0.2.0.bb => swtpm_0.5.2.bb}| 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
rename meta-tpm/recipes-tpm/swtpm/{swtpm_0.2.0.bb => swtpm_0.5.2.bb} (78%)
diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
b/meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb
similarity index 78%
rename from meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
rename to meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb
index 35c77c8..b7ff2ad 100644
--- a/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
+++ b/meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb
@@ -3,22 +3,21 @@ LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENSE;md5=fe8092c832b71ef20dfe4c6d3decb3a8"
SECTION = "apps"
-DEPENDS = "libtasn1 expect socat glib-2.0 net-tools-native libtpm
libtpm-native"
+DEPENDS = "libtasn1 coreutils-native expect socat glib-2.0 net-tools-native
libtpm libtpm-native"
# configure checks for the tools already during compilation and
# then swtpm_setup needs them at runtime
DEPENDS += "tpm-tools-native expect-native socat-native"
-SRCREV = "39673a0139b0ee14a0109aba50a0635592c672c4"
-SRC_URI = "git://github.com/stefanberger/swtpm.git;branch=stable-${PV} \
- file://fix_fcntl_h.patch \
+SRCREV = "e59c0c1a7b4c8d652dbb280fd6126895a7057464"
+SRC_URI = "git://github.com/stefanberger/swtpm.git;branch=stable-0.5 \
file://ioctl_h.patch \
"
PE = "1"
S = "${WORKDIR}/git"
-inherit autotools pkgconfig
+inherit autotools pkgconfig python3-dir
PARALLEL_MAKE = ""
TSS_USER="tss"
@@ -35,18 +34,20 @@ PACKAGECONFIG[seccomp] = "--with-seccomp,
--without-seccomp, libseccomp"
EXTRA_OECONF += "--with-tss-user=${TSS_USER} --with-tss-group=${TSS_GROUP}"
-export SEARCH_DIR = "${STAGING_LIBDIR_NATIVE}"
-
USERADD_PACKAGES = "${PN}"
GROUPADD_PARAM_${PN} = "--system ${TSS_USER}"
USERADD_PARAM_${PN} = "--system -g ${TSS_GROUP} --home-dir \
--no-create-home --shell /bin/false ${BPN}"
+
+PACKAGES =+ "${PN}-python"
+FILES_${PN}-python = "${nonarch_libdir}/${PYTHON_PN}/dist-packages/* "
+
PACKAGE_BEFORE_PN = "${PN}-cuse"
FILES_${PN}-cuse = "${bindir}/swtpm_cuse"
INSANE_SKIP_${PN} += "dev-so"
-RDEPENDS_${PN} = "libtpm expect socat bash tpm-tools"
+RDEPENDS_${PN} = "libtpm expect socat bash tpm-tools python3
python3-cryptography python3-twisted"
BBCLASSEXTEND = "native nativesdk"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52779): https://lists.yoctoproject.org/g/yocto/message/52779
Mute This Topic: https://lists.yoctoproject.org/mt/81465580/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?
On Fri, 19 Mar 2021, Mike Looijmans wrote: > > Met vriendelijke groet / kind regards, > > Mike Looijmans > System Expert > > > TOPIC Embedded Products B.V. > Materiaalweg 4, 5681 RJ Best > The Netherlands > > T: +31 (0) 499 33 69 69 > E: mike.looijm...@topicproducts.com > W: www.topic.nl > > Please consider the environment before printing this e-mail > On 19-03-2021 11:45, Robert P. J. Day via lists.yoctoproject.org wrote: > > On Fri, 19 Mar 2021, Nicolas Dechesne wrote: > > > >> On Fri, Mar 19, 2021 at 10:47 AM Robert P. J. Day > >> wrote: > >>> > >>>testing building qemuarm64 core-image-minimal from scratch, and > >>> noticed it fetching for docbook-xml and docbook-xsl stuff ... is there > >>> something that still needs docbook support? i'm about to take a quick > >>> look to see what's demanding that, does anyone know? > >> It's not related to yp-docs at least. most likely some recipes that > >> use docbook for their docs/man pages, no? > >most likely, but as i'm explicitly not installing any documentation, > > i'm now poking around to see what insists on building that for no > > apparent reason. > > > My favorite method for that is to just remove the recipe that provides it and > then see where it breaks... it appears (after a *very* cursory investigation) that shared-mime-info-native is included, which drags in xmlto-native, which then drags in docbook stuff. i'll confirm that later. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52777): https://lists.yoctoproject.org/g/yocto/message/52777 Mute This Topic: https://lists.yoctoproject.org/mt/81451648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v5.10] kernel code for marvell cn96xx
In message: [linux-yocto][linux-yocto v5.10] kernel code for marvell cn96xx on 19/03/2021 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge code into our linux-yocto repo. > > repo: > linux-yocto > > branch: > v5.10/standard/cn-sdkv4.18/cn96xx > > Thanks, > Ruiqiang > > The following changes since commit 6741d44a28fc9650e6f7563956395307bce68ea7: > > Merge branch 'v5.10/standard/base' into v5.10/standard/cn-sdkv4.18/cn96xx > (2021-03-15 10:52:03 -0400) > > are available in the Git repository at: > > https://github.com/cythe/linux.git > linux-yocto/v5.10/standard/cn-sdkv4.18/cn96xx merged. Bruce > > for you to fetch changes up to 6890bf451c594d2d0965b2e70f27b3ddf134cb61: > > octeontx2: Re-enable FLR and MBOX interrupts (2021-03-18 03:33:32 +) > > > Geetha sowjanya (3): > octeontx2-af: Rename LOKI model name as 95XXN > octeontx2-af: Reset MSIX config space in FLR > octeontx2-pf: Clear RSS enable flag on interace down > > Hariprasad Kelam (11): > net: thunderx: Modify BGX driver probe > octeontx2-af: clean up changes for FEC configuration > octeontx2-af: backport FEC configuration changes > octeontx2-pf: clean up changes for FEC configuration > octeontx2-pf: backport FEC configuration changes > octeontx2-af: code clean up for Physical link setttings > octeontx2-af: modify index in ethtool modes mapping > octeontx2-pf: Backport physical link status changes > octeontx2-pf: Backport physical link settings > Revert "octeontx2-pf: Add LIO3 link modes to ethtool's list of > supported modes" > octeontx2-af: Backport ethtool link modes > > Naveen Mamindlapalli (1): > octeontx2-pf: Add ip tos and ip proto icmp/icmpv6 flow offload support > > Subbaraya Sundeep (1): > octeontx2: Re-enable FLR and MBOX interrupts > > drivers/net/ethernet/cavium/thunder/nic_main.c | 5 +- > drivers/net/ethernet/cavium/thunder/thunder_bgx.c | 49 +- > drivers/net/ethernet/cavium/thunder/thunder_bgx.h | 1 + > drivers/net/ethernet/marvell/octeontx2/af/cgx.c| 193 > drivers/net/ethernet/marvell/octeontx2/af/cgx.h| 10 +- > .../net/ethernet/marvell/octeontx2/af/cgx_fw_if.h | 1 + > drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 60 +-- > drivers/net/ethernet/marvell/octeontx2/af/npc.h| 2 + > drivers/net/ethernet/marvell/octeontx2/af/ptp.c| 4 +- > drivers/net/ethernet/marvell/octeontx2/af/rvu.c| 26 ++ > drivers/net/ethernet/marvell/octeontx2/af/rvu.h| 5 +- > .../net/ethernet/marvell/octeontx2/af/rvu_cgx.c| 140 +++--- > .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 17 +- > .../ethernet/marvell/octeontx2/nic/otx2_common.c | 11 +- > .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 498 > ++--- > .../ethernet/marvell/octeontx2/nic/otx2_flows.c| 42 +- > .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 11 + > drivers/soc/marvell/octeontx2-rm/otx2_rm.c | 9 + > 18 files changed, 595 insertions(+), 489 deletions(-) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9583): https://lists.yoctoproject.org/g/linux-yocto/message/9583 Mute This Topic: https://lists.yoctoproject.org/mt/81451270/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?
Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijm...@topicproducts.com W: www.topic.nl Please consider the environment before printing this e-mail On 19-03-2021 11:45, Robert P. J. Day via lists.yoctoproject.org wrote: On Fri, 19 Mar 2021, Nicolas Dechesne wrote: On Fri, Mar 19, 2021 at 10:47 AM Robert P. J. Day wrote: testing building qemuarm64 core-image-minimal from scratch, and noticed it fetching for docbook-xml and docbook-xsl stuff ... is there something that still needs docbook support? i'm about to take a quick look to see what's demanding that, does anyone know? It's not related to yp-docs at least. most likely some recipes that use docbook for their docs/man pages, no? most likely, but as i'm explicitly not installing any documentation, i'm now poking around to see what insists on building that for no apparent reason. My favorite method for that is to just remove the recipe that provides it and then see where it breaks... -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52776): https://lists.yoctoproject.org/g/yocto/message/52776 Mute This Topic: https://lists.yoctoproject.org/mt/81451648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto v5.4/standard/nxp-s32g2xx]: mtd: spi-nor: change the performance info print to dev_dbg
In message: [linux-yocto] [linux-yocto v5.4/standard/nxp-s32g2xx]: mtd: spi-nor: change the performance info print to dev_dbg on 19/03/2021 Zhantao Tang wrote: > > Hi Bruce, > > > In v5.4/standard/nxp-s32g2xx branch, the s32gen1 qspi introduced a performance > indicator, it will print a performce info in every read operation, > but it is no much help for the flash function and may cause some flash test > fail due to the tons of infos. And the following patch is to fix this issue. > > Would you please help to merge this patch into linux-ycoto kernel, v5.4, > branch is v5.4/standard/nxp-s32g2xx? merged. Bruce > > > > Thanks, > Zhantao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9582): https://lists.yoctoproject.org/g/linux-yocto/message/9582 Mute This Topic: https://lists.yoctoproject.org/mt/81451076/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v5.10/standard/ti-sdk-5.4/ti-j72xx][PATCH] ti-j72xx kernel part for linux-yocto kernel v5.10
In message: [linux-yocto][linux-yocto
v5.10/standard/ti-sdk-5.4/ti-j72xx][PATCH] ti-j72xx kernel part for linux-yocto
kernel v5.10
on 19/03/2021 Xulin Sun wrote:
> Hi Bruce,
>
> Could you please help to create a new kernel branch
> "v5.10/standard/ti-sdk-5.4/ti-j72xx"
> based on "v5.10/standard/base" for newly added bsp ti-j72xx on kernel 5.10 ?
>
> And merge below patches to the new branch
> "v5.10/standard/ti-sdk-5.4/ti-j72xx".
created and merged.
Thanks for the changes!
Bruce
>
>
> The following changes since commit 04a11eb4aec4efe3064f27b207e8a41c28bb08cd:
>
> Merge tag 'v5.10.23' into v5.10/standard/base (2021-03-15 10:51:55 -0400)
>
> are available in the Git repository at:
>
> https://github.com/xulinsun/ti-j72x v5.10/standard/base
>
> for you to fetch changes up to a55369ce499aa2b54424d73532ce3968db88f542:
>
> dmabuf: revert the removed functions for adapting out-of-tree gpu
> ti-img-rogue-driver (2021-03-19 13:24:33 +0800)
>
>
> Anand Balagopalakrishnan (1):
> arm64: dts: ti: k3-j721e-main: Add GPU node
>
> Andrew F. Davis (16):
> dt-bindings: gpu: Add binding for TI SGX
> arm64: dts: ti: k3-am654-main: Add device tree entry for SGX
> HACK: dt-bindings: misc: Add ti,dma_buf_phys binding doc
> HACK: misc: Add dma-buf to physical address exporter
> dt-bindings: soc: ti: Add TI PAT bindings
> arm64: dts: ti: k3-j721e-main: Add MAIN domain PAT nodes
> soc: ti: Add Support for the TI Page-based Address Translator (PAT)
> HACK: misc: dma-buf-phys: Allow this driver to be built as a module
> soc: ti: pruss: add pruss_{request,release}_mem_region() API
> dt-bindings: net: Add TI-PRUeth bindings
> dma-buf: heaps: Initialize during core instead of subsys
> dma-buf: heaps: Add Carveout heap to dmabuf heaps
> misc: sram: Add dma-heap-export reserved SRAM area type
> misc: sram: dma-heap-export: Fix memory leak in dma-buf attach
> misc: sram: DMA-Heaps exporter depends on DMA-Heaps framework
> HACK: dma-buf: heaps: carveout: Add support for cached carveout heaps
>
> Angela Stegmaier (1):
> rpmsg: fix lockdep warnings in virtio rpmsg bus driver
>
> Arnaud Pouliquen (1):
> rpmsg: core: add API to get MTU
>
> Aswath Govindraju (1):
> phy: keystone: fix unused variable build warning
>
> Benoit Parrot (26):
> drm/omap: Add ability to check if requested plane modes can be
> supported
> drm/omap: Add ovl checking funcs to dispc_ops
> drm/omap: introduce omap_hw_overlay
> drm/omap: omap_plane: subclass drm_plane_state
> drm/omap: Add global state as a private atomic object
> drm/omap: dynamically assign hw overlays to planes
> drm/omap: add plane_atomic_print_state support
> drm/omap: Add a 'right overlay' to plane state
> drm/atomic: integrate private objects with suspend/resume helpers
> drm/omap: add omap_plane_reserve/release_wb
> drm/omap: add WB support
> HACK: Input: goodix: fix driver auto-loading
> dt-bindings: media: Document OmniVision OV1063x driver
> HACK: UAPI: Increasing VIDEO_MAX_FRAME/VB2_MAX_FRAME to 128
> dt-binbings: media: ti-vpe: Document the VIP driver
> media: ti-vpe: Add the VIP driver
> drm/tidss: add has_writeback flag
> drm/tidss: add WB to io resource map
> drm/tidss: add WB specific register offsets
> drm/tidss: add WB irq enable/status accessor
> drm/tidss: Add RGB to YUV color conversion support
> drm/tidss: Add WB config/setup helper
> drm/tidss: add tidss_plane_reserve/release_wb
> drm/tidss: add WB M2M driver
> media: ti-vpe: vip: fix asd allocation scheme
> arm64: dts: Add HDMI video to
> k3-j721e-common-proc-board-infotainment.dtso
>
> Bin Liu (9):
> dt-bindings: serial: add binding documentation for TI PRU software
> UART
> serial: add pru software uart (pru_suart) driver
> dt-bindings: pwm: add binding documentation for TI PRUSS PWM
> pwm: core: populate the sysfs device into pwmchip
> pwm: add pruss iep-based pwm driver
> arm64: dts: add k3-am654-evm-prupwm.dtso
> dt-bindings: serial: add binding documentation for TI PRUSS UART
> serial: 8250: add pruss uart driver
> serial: 8250: pruss: fix overflow in conversion build warning
>
> Dave Gerlach (6):
> dt-bindings: wkup_m3_ipc: Add vtt toggling bindings
> wkup_m3_ipc: Add support for toggling VTT regulator
> dt-bindings: wkup_m3_ipc: Add ti,io-isolation property
> wkup_m3_ipc: Add support for IO Isolation
> soc: ti: wkup_m3_ipc: Add support for i2c voltage scaling
> soc: ti: wkup_m3_ipc: Add debug option to halt m3 in suspend
>
> Faiz Abbas (15):
> arm64: dts: ti: k3-j721e-main: Add SDHCI nodes
> can: m_can: m_can_platform: Add support for enabling transceiver
>
Re: [linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support gpio on FPGA side
In message: [linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support gpio on FPGA side on 19/03/2021 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > Based on FPGA ghrd(golden hardware reference design) hw design > that includes gpio feature, I created a patch to add corresponding dts file > to enable > FPGA sw3, FPGA buttion and FPGA led. > > Could you please help tomerge this patch into linux-ycoto kernel repo, branch > v5.10/standard/intel-sdk-5.10/intel-socfpga? merged. Bruce > > > diffstat info as below: > > Makefile |2 - > socfpga_stratix10_socdk_ghrd.dts | 78 > +++ > 2 files changed, 79 insertions(+), 1 deletion(-) > > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9580): https://lists.yoctoproject.org/g/linux-yocto/message/9580 Mute This Topic: https://lists.yoctoproject.org/mt/81448980/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support sgmii ethernet on FPGA side
merged. Bruce In message: [linux-yocto]: [kernel v5.10/standard/intel-sdk-5.10/intel-socfpga]: arch: arm64: altera: add dts file to support sgmii ethernet on FPGA side on 19/03/2021 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > Based on FPGA hw design that includes sgmii ethernet feature, I created a > patch > to add corresponding dts file to enable 2 ethernet ports on stratix10 board. > > Could you please help tomerge this patch into linux-ycoto kernel repo, branch > v5.10/standard/intel-sdk-5.10/intel-socfpga? > > > diffstat info as below: > > Makefile |2 > socfpga_stratix10_socdk_sgmii.dts | 87 > ++ > 2 files changed, 88 insertions(+), 1 deletion(-) > > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9579): https://lists.yoctoproject.org/g/linux-yocto/message/9579 Mute This Topic: https://lists.yoctoproject.org/mt/81446683/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-5.10][PATCH] ti-j72xx: add kernel-cache configuration files for BSP ti-j72xx
In message: [linux-yocto][yocto-kernel-cache][yocto-5.10][PATCH] ti-j72xx: add kernel-cache configuration files for BSP ti-j72xx on 18/03/2021 Xulin Sun wrote: > This adds the cfg & scc files to support the TI J721E soc. merged. Bruce > > Signed-off-by: Xulin Sun > --- > bsp/ti-j72xx/ti-j72xx-remoteproc.cfg | 21 ++ > bsp/ti-j72xx/ti-j72xx-remoteproc.scc | 1 + > bsp/ti-j72xx/ti-j72xx-standard.scc | 8 + > bsp/ti-j72xx/ti-j72xx.cfg| 344 +++ > bsp/ti-j72xx/ti-j72xx.scc| 8 + > 5 files changed, 382 insertions(+) > create mode 100644 bsp/ti-j72xx/ti-j72xx-remoteproc.cfg > create mode 100644 bsp/ti-j72xx/ti-j72xx-remoteproc.scc > create mode 100644 bsp/ti-j72xx/ti-j72xx-standard.scc > create mode 100755 bsp/ti-j72xx/ti-j72xx.cfg > create mode 100644 bsp/ti-j72xx/ti-j72xx.scc > > diff --git a/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg > b/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg > new file mode 100644 > index ..a6eb3538 > --- /dev/null > +++ b/bsp/ti-j72xx/ti-j72xx-remoteproc.cfg > @@ -0,0 +1,21 @@ > +# > +# Remoteproc drivers > +# > +CONFIG_REMOTEPROC=y > +CONFIG_PRU_REMOTEPROC=m > +CONFIG_TI_K3_R5_REMOTEPROC=m > +CONFIG_TI_K3_DSP_REMOTEPROC=m > + > +# > +# Rpmsg virtual device drivers > +# > +CONFIG_RPMSG_KDRV=y > +CONFIG_RPMSG_KDRV_ETH_SWITCH=m > +CONFIG_TI_RDEV_ETH_SWITCH_VIRT_EMAC=m > +CONFIG_RPMSG_VIRTIO=m > +CONFIG_RPMSG_CHAR=m > +CONFIG_RPMSG_PRU=m > +CONFIG_SAMPLES=y > +CONFIG_SAMPLE_RPMSG_CLIENT=m > +CONFIG_RPMSG_KDRV_DISPLAY=y > +CONFIG_RPMSG_PROTO=m > diff --git a/bsp/ti-j72xx/ti-j72xx-remoteproc.scc > b/bsp/ti-j72xx/ti-j72xx-remoteproc.scc > new file mode 100644 > index ..1848f96b > --- /dev/null > +++ b/bsp/ti-j72xx/ti-j72xx-remoteproc.scc > @@ -0,0 +1 @@ > +kconf hardware ti-j72xx-remoteproc.cfg > diff --git a/bsp/ti-j72xx/ti-j72xx-standard.scc > b/bsp/ti-j72xx/ti-j72xx-standard.scc > new file mode 100644 > index ..650c3377 > --- /dev/null > +++ b/bsp/ti-j72xx/ti-j72xx-standard.scc > @@ -0,0 +1,8 @@ > +# SPDX-License-Identifier: MIT > +define KMACHINE ti-j72xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard/standard.scc > + > +include ti-j72xx.scc > diff --git a/bsp/ti-j72xx/ti-j72xx.cfg b/bsp/ti-j72xx/ti-j72xx.cfg > new file mode 100755 > index ..318fb808 > --- /dev/null > +++ b/bsp/ti-j72xx/ti-j72xx.cfg > @@ -0,0 +1,344 @@ > +# > +#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. > +# > +#. > + > +# > +# > +# Platform selection > +# > +CONFIG_ARM64=y > +CONFIG_ARCH_K3=y > + > +CONFIG_ARCH_K3_J721E_SOC=y > +CONFIG_ARM_SMMU=y > +CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT=y > +CONFIG_ARM_SMMU_V3=y > +CONFIG_TI_PAT=y > +CONFIG_TI_PRUSS=m > +CONFIG_ARCH_K3_AM6_SOC=y > +CONFIG_CMA=y > +CONFIG_DMA_CMA=y > + > +CONFIG_EXPERT=y > +CONFIG_ARM64_64K_PAGES=y > +CONFIG_TRANSPARENT_HUGEPAGE=y > +CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y > + > +# > +# DesignWare PCI Core Support > +# > + > +CONFIG_PCI=y > +CONFIG_PCI_MSI=y > +CONFIG_PCI_MSI_IRQ_DOMAIN=y > +CONFIG_PCI_KEYSTONE=y > +CONFIG_PCI_KEYSTONE_HOST=y > +CONFIG_PCI_J721E_HOST=y > +CONFIG_PCI_J721E_EP=y > +CONFIG_PCI_ENDPOINT=y > +CONFIG_PCI_J721E=y > +CONFIG_SOCIONEXT_SYNQUACER_PREITS=y > +CONFIG_PCIE_CADENCE=y > +CONFIG_PCIE_CADENCE_HOST=y > +CONFIG_PCIE_CADENCE_EP=y > +CONFIG_PCI_EPF_NTB=y > +CONFIG_PCIEPORTBUS=y > +CONFIG_PCI_KEYSTONE_EP=y > +CONFIG_PHY_CADENCE_TORRENT=y > +CONFIG_PHY_CADENCE_SIERRA=y > +CONFIG_BLK_DEV_NVME=y > + > +# > +# MMC/SD/SDIO Host Controller Drivers > +# > +CONFIG_MMC=y > +CONFIG_MMC_SPI=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_AM654=y > + > +# > +# Power management options > +# > +CONFIG_PM_SLEEP=y > +CONFIG_PM_SLEEP_SMP=y > +CONFIG_PM=y > +CONFIG_PM_CLK=y > +CONFIG_CPU_PM=y > + > +# > +# CPU Frequency scaling > +# > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_GOV_ATTR_SET=y > +CONFIG_CPU_FREQ_GOV_COMMON=y > +CONFIG_CPU_FREQ_STAT=y > +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y > +CONFIG_CPU_FREQ_GOV_PERFORMANCE=y > +CONFIG_CPU_FREQ_GOV_USERSPACE=y > +CONFIG_CPU_FREQ_GOV_ONDEMAND=y > +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y > + > +# > +# CPU frequency scaling drivers > +# > +CONFIG_CPUFREQ_DT=y > +CONFIG_CPUFREQ_DT_PLATDEV=y > + > +# > +# Bus devices > +# > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_OF_PARTS=y > +CONFIG_MTD_BLKDEVS=y > +CONFIG_MTD_BLOCK=y > + > +# > +# SCSI
Re: [linux-yocto]: [kernel v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx]: nxp-s32g2xx: update kernel patches from vendor sdk-bsp28
In message: [linux-yocto]: [kernel v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx]: nxp-s32g2xx: update kernel patches from vendor sdk-bsp28 on 17/03/2021 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > NXP had relesed sdk-bsp28 for nxp s32g2xx platform. > > I got the latest BSP related patches from nxp-s32g sdk kernel repo > https://source.codeaurora.org/external/autobsps32/linux, > and want to merge them into linux-yocto-v5.10. There are 88 patches. > > Could you please help to merge these patches into linux-ycoto kernel repo, > branch v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx? merged. Bruce > > The 88 patches are in my public repo > https://github.com/limeng-linux/linux-yocto-5.10.git, branch > v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx > > > diffstat info as below: > > arch/arm64/boot/dts/freescale/fsl-s32v344-simulator.dts| > 529 --- > b/Documentation/devicetree/bindings/arm/fsl.yaml | >5 > b/Documentation/devicetree/bindings/clock/s32gen1-clocking.txt | >2 > b/Documentation/devicetree/bindings/fsl-pfeng.txt | > 110 > b/Documentation/devicetree/bindings/gpio/gpio-s32v.txt | >2 > b/Documentation/devicetree/bindings/mailbox/nxp,s32g274a-llce-mailbox.yaml | > 135 > b/Documentation/devicetree/bindings/mfd/nxp,s32g274a-llce-core.yaml| > 128 > b/Documentation/devicetree/bindings/net/can/nxp,s32g274a-llce-can.yaml | > 92 > b/Documentation/devicetree/bindings/pinctrl/nxp,s32gen1-siul2-pinctrl.txt | >2 > b/Documentation/devicetree/bindings/sram/sram.yaml | >1 > b/arch/arm64/boot/dts/freescale/Makefile | >1 > b/arch/arm64/boot/dts/freescale/fsl-s32-gen1.dtsi | > 68 > b/arch/arm64/boot/dts/freescale/fsl-s32g274-simulator.dts | > 35 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a-bluebox3.dts | > 126 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a-emu.dts | > 10 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a-evb.dts | > 107 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a-rdb.dtsi | > 83 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a-rdb2.dts | > 39 > b/arch/arm64/boot/dts/freescale/fsl-s32g274a.dtsi | > 574 +++ > b/arch/arm64/boot/dts/freescale/fsl-s32r45-evb.dts | > 48 > b/arch/arm64/boot/dts/freescale/fsl-s32r45.dtsi| > 26 > b/arch/arm64/boot/dts/freescale/fsl-s32v234.dtsi | >3 > b/drivers/base/regmap/regmap-debugfs.c | >1 > b/drivers/clk/s32/s32-gen1/clk-plldig.c| >8 > b/drivers/clk/s32/s32-gen1/clk.c | > 503 +- > b/drivers/clk/s32/s32-gen1/pll.h | >7 > b/drivers/clk/s32/s32v234/clk-plldig.c | > 88 > b/drivers/clk/s32/s32v234/pll.h| >9 > b/drivers/clocksource/Makefile | >3 > b/drivers/clocksource/timer-fsl-stm.c | >1 > b/drivers/crypto/hse/Kconfig | > 21 > b/drivers/crypto/hse/Makefile | >3 > b/drivers/crypto/hse/hse-core.c| > 43 > b/drivers/crypto/hse/hse-core.h| >8 > b/drivers/crypto/hse/hse-uio.c | > 226 + > b/drivers/dma/fsl-edma-common.h| >4 > b/drivers/dma/fsl-edma.c | >6 > b/drivers/gpio/gpio-siul2-s32gen1.c| > 344 + > b/drivers/mailbox/Kconfig | >9 > b/drivers/mailbox/Makefile | >2 > b/drivers/mailbox/llce-mailbox.c | > 1737 +- > b/drivers/mfd/Kconfig | > 10 > b/drivers/mfd/Makefile | >1 > b/drivers/mfd/llce-core.c | > 530 ++- > b/drivers/misc/sram.c | > 60 > b/drivers/mmc/host/sdhci-esdhc-imx.c | > 10 > b/drivers/mtd/spi-nor/controllers/fsl-quadspi.c| >
Re: [linux-yocto] [yocto-kernel-cache]: nxp-s32g2xx: add regulator kernel config
merged. Bruce In message: [yocto-kernel-cache]: nxp-s32g2xx: add regulator kernel config on 17/03/2021 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > at803x phy config depends on regulator config, > so enable CONFIG_REGULATOR. > > Could you please help to merge this patch into yocto-kernel-cache, branch is > yocto-5.10? > > diffstat info ad below: > > nxp-s32g2xx.cfg |3 +++ > 1 file changed, 3 insertions(+) > > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9576): https://lists.yoctoproject.org/g/linux-yocto/message/9576 Mute This Topic: https://lists.yoctoproject.org/mt/81397093/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache yocto-5.10][PATCH] nxp-imx8: add kernel-cache configuration files for BSP nxp-imx8
In message: [linux-yocto] [kernel-cache yocto-5.10][PATCH] nxp-imx8: add kernel-cache configuration files for BSP nxp-imx8 on 17/03/2021 Xiaolei Wang wrote: > This adds the cfg & scc files to support the nxp-imx8 merged. Bruce > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx8/nxp-imx8-standard.scc | 8 + > bsp/nxp-imx8/nxp-imx8.cfg | 514 + > bsp/nxp-imx8/nxp-imx8.scc | 10 + > 3 files changed, 532 insertions(+) > create mode 100644 bsp/nxp-imx8/nxp-imx8-standard.scc > create mode 100644 bsp/nxp-imx8/nxp-imx8.cfg > create mode 100644 bsp/nxp-imx8/nxp-imx8.scc > > diff --git a/bsp/nxp-imx8/nxp-imx8-standard.scc > b/bsp/nxp-imx8/nxp-imx8-standard.scc > new file mode 100644 > index ..222cbeac > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE nxp-imx8 > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > +branch nxp-imx8 > + > +include nxp-imx8.scc > diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg > new file mode 100644 > index ..56f1cf17 > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8.cfg > @@ -0,0 +1,514 @@ > +CONFIG_PROFILING=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_ARCH_MXC=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_SCHED_MC=y > +CONFIG_CLK_IMX8QXP=y > + > +# > +## Kernel Features > +# > +CONFIG_KEXEC=y > +CONFIG_TRANSPARENT_HUGEPAGE=y > + > +# > +# CPU idle > +CONFIG_ARM_CPUIDLE=y > +CONFIG_ARM_PSCI_CPUIDLE=y > + > +#CAN > +CONFIG_CAN=m > +CONFIG_CAN_FLEXCAN=m > + > +#SATA > +CONFIG_ATA=y > +CONFIG_MFD_SYSCON=y > +CONFIG_AHCI_IMX=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > + > +# > +## PCI > +# > +CONFIG_PCI=y > +CONFIG_PCI_MSI=y > +CONFIG_PCI_IMX6_HOST=y > +CONFIG_PCI_HISI=y > + > +# > +## mipi_dsim and LCDIF core driver > +# > +CONFIG_DRM_IMX_SEC_DSIM=y > +CONFIG_IMX_LCDIF_CORE=y > + > +# > +## USB > +# > +CONFIG_USB_OTG=y > +CONFIG_USB_OTG_WHITELIST=y > +CONFIG_USB_XHCI_HCD=y > +CONFIG_USB_GADGET=y > +CONFIG_USB_EHCI_HCD=y > +CONFIG_USB_EHCI_HCD_PLATFORM=y > +CONFIG_USB_OHCI_HCD=y > +CONFIG_USB_OHCI_HCD_PLATFORM=y > +CONFIG_USB_HCD_TEST_MODE=y > +CONFIG_USB_ACM=m > +CONFIG_USB_STORAGE=y > +CONFIG_USB_UAS=y > +CONFIG_USB_CDNS3=y > +CONFIG_USB_CDNS3_GADGET=y > +CONFIG_USB_CDNS3_HOST=y > +CONFIG_USB_PHY=y > +CONFIG_NOP_USB_XCEIV=y > +CONFIG_USB_MXS_PHY=y > +CONFIG_USB_ULPI=y > +CONFIG_USB_ULPI_VIEWPORT=y > +CONFIG_USB_SNP_CORE=y > +CONFIG_USB_SNP_UDC_PLAT=y > +CONFIG_USB_CHIPIDEA=y > +CONFIG_USB_CHIPIDEA_UDC=y > +CONFIG_USB_CHIPIDEA_HOST=y > + > +# > +## Random Number Generation > +# > +CONFIG_CRYPTO_USER=y > +CONFIG_CRYPTO_TEST=m > +CONFIG_CRYPTO_CHACHA20POLY1305=m > +CONFIG_CRYPTO_ECHAINIV=y > +CONFIG_CRYPTO_TLS=m > +CONFIG_CRYPTO_CBC=m > +CONFIG_CRYPTO_CFB=m > +CONFIG_CRYPTO_CTS=m > +CONFIG_CRYPTO_LRW=m > +CONFIG_CRYPTO_OFB=m > +CONFIG_CRYPTO_XTS=m > +CONFIG_CRYPTO_MD4=m > +CONFIG_CRYPTO_MD5=m > +CONFIG_CRYPTO_RMD128=m > +CONFIG_CRYPTO_RMD160=m > +CONFIG_CRYPTO_RMD256=m > +CONFIG_CRYPTO_RMD320=m > +CONFIG_CRYPTO_SHA512=m > +CONFIG_CRYPTO_TGR192=m > +CONFIG_CRYPTO_WP512=m > +CONFIG_CRYPTO_BLOWFISH=m > +CONFIG_CRYPTO_CAMELLIA=m > +CONFIG_CRYPTO_CAST5=m > +CONFIG_CRYPTO_CAST6=m > +CONFIG_CRYPTO_SERPENT=m > +CONFIG_CRYPTO_TWOFISH=m > +CONFIG_CRYPTO_ANSI_CPRNG=y > +CONFIG_CRYPTO_DEV_FSL_CAAM=y > +CONFIG_CRYPTO_DEV_FSL_CAAM_SM=y > +CONFIG_CRYPTO_DEV_FSL_CAAM_SM_TEST=m > +CONFIG_CRYPTO_DEV_FSL_CAAM_SECVIO=y > +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y > +CONFIG_CRYPTO_PCBC=m > +CONFIG_CRYPTO_XCBC=m > +CONFIG_CRYPTO_VMAC=m > +CONFIG_CRYPTO_SM3=m > +CONFIG_CRYPTO_STREEBOG=m > +CONFIG_CRYPTO_ANUBIS=m > +CONFIG_CRYPTO_DES=m > +CONFIG_CRYPTO_FCRYPT=m > +CONFIG_CRYPTO_KHAZAD=m > +CONFIG_CRYPTO_SALSA20=m > +CONFIG_CRYPTO_SEED=m > +CONFIG_CRYPTO_SM4=m > +CONFIG_CRYPTO_TEA=m > + > +# > +## Input device support > +# > +CONFIG_MMC=y > +CONFIG_MMC_BLOCK_MINORS=32 > +CONFIG_MMC_ARMMMCI=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_ACPI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_OF_ARASAN=y > +CONFIG_MMC_SDHCI_OF_ESDHC=y > +CONFIG_MMC_SDHCI_CADENCE=y > +CONFIG_MMC_SDHCI_ESDHC_IMX=y > + > +# > +## Input device support > +# > +CONFIG_INPUT_EVDEV=y > +CONFIG_KEYBOARD_ADC=m > +CONFIG_KEYBOARD_GPIO=y > +CONFIG_KEYBOARD_SNVS_PWRKEY=y > +CONFIG_KEYBOARD_IMX_SC_PWRKEY=y > +CONFIG_KEYBOARD_CROS_EC=y > +CONFIG_INPUT_TOUCHSCREEN=y > +CONFIG_TOUCHSCREEN_ATMEL_MXT=m > +CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C=m > +CONFIG_INPUT_MISC=y > +CONFIG_INPUT_MPL3115=y > +CONFIG_INPUT_ISL29023=y > + > +# > +## Pin controllers > +# > +CONFIG_PINCTRL=y > +CONFIG_PINCTRL_IMX8QM=y > +CONFIG_GPIOLIB=y > +CONFIG_GPIO_SYSFS=y > +CONFIG_GPIO_DWAPB=y > +CONFIG_GPIO_MB86S7X=y > +CONFIG_GPIO_MPC8XXX=y > +CONFIG_GPIO_PL061=y > +CONFIG_GPIO_XGENE=y > +CONFIG_GPIO_MAX732X=y > +CONFIG_GPIO_PCA953X=y > +CONFIG_GPIO_PCA953X_IRQ=y > +CONFIG_GPIO_MAX77620=y > + > +# > +## Regulator Driver > +# > +CONFIG_REGULATOR=y > +CONFIG_REGULATOR_FIXED_VOLTAGE=y > +CONFIG_REGULATOR_AXP20X=y >
Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?
On Fri, 19 Mar 2021, Nicolas Dechesne wrote: > On Fri, Mar 19, 2021 at 10:47 AM Robert P. J. Day > wrote: > > > > > > testing building qemuarm64 core-image-minimal from scratch, and > > noticed it fetching for docbook-xml and docbook-xsl stuff ... is there > > something that still needs docbook support? i'm about to take a quick > > look to see what's demanding that, does anyone know? > > It's not related to yp-docs at least. most likely some recipes that > use docbook for their docs/man pages, no? most likely, but as i'm explicitly not installing any documentation, i'm now poking around to see what insists on building that for no apparent reason. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52775): https://lists.yoctoproject.org/g/yocto/message/52775 Mute This Topic: https://lists.yoctoproject.org/mt/81451648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?
On Fri, Mar 19, 2021 at 10:47 AM Robert P. J. Day wrote: > > > testing building qemuarm64 core-image-minimal from scratch, and > noticed it fetching for docbook-xml and docbook-xsl stuff ... is there > something that still needs docbook support? i'm about to take a quick > look to see what's demanding that, does anyone know? It's not related to yp-docs at least. most likely some recipes that use docbook for their docs/man pages, no? > > rday > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52774): https://lists.yoctoproject.org/g/yocto/message/52774 Mute This Topic: https://lists.yoctoproject.org/mt/81451648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] is there a recent explanation of tricks you can play with MACHINEOVERRIDES?
years ago, i asked about how to support a small set of closely-related targets using MACHINEOVERRIDES to define how to apply patches in a (somewhat) hierarchical fashion: https://www.yoctoproject.org/pipermail/yocto/2016-March/028922.html is there any current BSP that does something like that? and is this sort of thing worth expanding on and adding to one of the manuals? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca LinkedIn: http://ca.linkedin.com/in/rpjday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52773): https://lists.yoctoproject.org/g/yocto/message/52773 Mute This Topic: https://lists.yoctoproject.org/mt/81451700/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] does current bitbaking of core-image-minimal still need docbook stuff?
testing building qemuarm64 core-image-minimal from scratch, and noticed it fetching for docbook-xml and docbook-xsl stuff ... is there something that still needs docbook support? i'm about to take a quick look to see what's demanding that, does anyone know? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52772): https://lists.yoctoproject.org/g/yocto/message/52772 Mute This Topic: https://lists.yoctoproject.org/mt/81451648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Avahi in yocto #yocto
Hello Guys i have installed *avahi-0.8* version using gatesgarth version, its compiled successfully but i am facing an *issue* with *TriggeredBy: [[0;1;32m●[[0m avahi-daemon.socket, when i restart my service. [[0;1;32m●[[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [[0;1;32mactive (running)[[0m since Wed 2021-03-17 09:39:36 UTC; 3min 16s ago TriggeredBy: [[0;1;32m●[[0m avahi-daemon.socket Main PID: 15022 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 9561) Memory: 928.0K CGroup: /system.slice/avahi-daemon.service ├─15022 avahi-daemon: running [robot.local] └─15023 avahi-daemon: chroot helper Mar 17 09:39:36 robot systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Mar 17 09:39:36 robot avahi-daemon[15022]: Process 14994 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid) Mar 17 09:39:36 robot systemd[1]: Started Avahi mDNS/DNS-SD Stack.* if something is missing, please update me sothat i can modify. T lavkhush -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52771): https://lists.yoctoproject.org/g/yocto/message/52771 Mute This Topic: https://lists.yoctoproject.org/mt/81451518/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.10] kernel code for marvell cn96xx[rt]
Hi Bruce, Please help to merge code into our linux-yocto repo. repo: linux-yocto branch: linux-yocto/v5.10/standard/preempt-rt/cn-sdkv4.18/cn96xx Thanks, Ruiqiang The following changes since commit e542832db0aade6755103a3fb37229b82b0c5057: Merge branch 'v5.10/standard/base' into v5.10/standard/preempt-rt/cn-sdkv4.18/cn96xx (2021-03-15 10:52:16 -0400) are available in the Git repository at: https://github.com/cythe/linux.git linux-yocto/v5.10/standard/preempt-rt/cn-sdkv4.18/cn96xx for you to fetch changes up to d258872cfb166198778b7277002f10b2d96435ce: octeontx2: Re-enable FLR and MBOX interrupts (2021-03-18 03:35:10 +) Geetha sowjanya (3): octeontx2-af: Rename LOKI model name as 95XXN octeontx2-af: Reset MSIX config space in FLR octeontx2-pf: Clear RSS enable flag on interace down Hariprasad Kelam (11): net: thunderx: Modify BGX driver probe octeontx2-af: clean up changes for FEC configuration octeontx2-af: backport FEC configuration changes octeontx2-pf: clean up changes for FEC configuration octeontx2-pf: backport FEC configuration changes octeontx2-af: code clean up for Physical link setttings octeontx2-af: modify index in ethtool modes mapping octeontx2-pf: Backport physical link status changes octeontx2-pf: Backport physical link settings Revert "octeontx2-pf: Add LIO3 link modes to ethtool's list of supported modes" octeontx2-af: Backport ethtool link modes Naveen Mamindlapalli (1): octeontx2-pf: Add ip tos and ip proto icmp/icmpv6 flow offload support Subbaraya Sundeep (1): octeontx2: Re-enable FLR and MBOX interrupts drivers/net/ethernet/cavium/thunder/nic_main.c | 5 +- drivers/net/ethernet/cavium/thunder/thunder_bgx.c | 49 +- drivers/net/ethernet/cavium/thunder/thunder_bgx.h | 1 + drivers/net/ethernet/marvell/octeontx2/af/cgx.c| 193 drivers/net/ethernet/marvell/octeontx2/af/cgx.h| 10 +- .../net/ethernet/marvell/octeontx2/af/cgx_fw_if.h | 1 + drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 60 +-- drivers/net/ethernet/marvell/octeontx2/af/npc.h| 2 + drivers/net/ethernet/marvell/octeontx2/af/ptp.c| 4 +- drivers/net/ethernet/marvell/octeontx2/af/rvu.c| 26 ++ drivers/net/ethernet/marvell/octeontx2/af/rvu.h| 5 +- .../net/ethernet/marvell/octeontx2/af/rvu_cgx.c| 140 +++--- .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 17 +- .../ethernet/marvell/octeontx2/nic/otx2_common.c | 11 +- .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 498 ++--- .../ethernet/marvell/octeontx2/nic/otx2_flows.c| 42 +- .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 11 + drivers/soc/marvell/octeontx2-rm/otx2_rm.c | 9 + 18 files changed, 595 insertions(+), 489 deletions(-) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9573): https://lists.yoctoproject.org/g/linux-yocto/message/9573 Mute This Topic: https://lists.yoctoproject.org/mt/81451271/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.10] kernel code for marvell cn96xx
Hi Bruce, Please help to merge code into our linux-yocto repo. repo: linux-yocto branch: v5.10/standard/cn-sdkv4.18/cn96xx Thanks, Ruiqiang The following changes since commit 6741d44a28fc9650e6f7563956395307bce68ea7: Merge branch 'v5.10/standard/base' into v5.10/standard/cn-sdkv4.18/cn96xx (2021-03-15 10:52:03 -0400) are available in the Git repository at: https://github.com/cythe/linux.git linux-yocto/v5.10/standard/cn-sdkv4.18/cn96xx for you to fetch changes up to 6890bf451c594d2d0965b2e70f27b3ddf134cb61: octeontx2: Re-enable FLR and MBOX interrupts (2021-03-18 03:33:32 +) Geetha sowjanya (3): octeontx2-af: Rename LOKI model name as 95XXN octeontx2-af: Reset MSIX config space in FLR octeontx2-pf: Clear RSS enable flag on interace down Hariprasad Kelam (11): net: thunderx: Modify BGX driver probe octeontx2-af: clean up changes for FEC configuration octeontx2-af: backport FEC configuration changes octeontx2-pf: clean up changes for FEC configuration octeontx2-pf: backport FEC configuration changes octeontx2-af: code clean up for Physical link setttings octeontx2-af: modify index in ethtool modes mapping octeontx2-pf: Backport physical link status changes octeontx2-pf: Backport physical link settings Revert "octeontx2-pf: Add LIO3 link modes to ethtool's list of supported modes" octeontx2-af: Backport ethtool link modes Naveen Mamindlapalli (1): octeontx2-pf: Add ip tos and ip proto icmp/icmpv6 flow offload support Subbaraya Sundeep (1): octeontx2: Re-enable FLR and MBOX interrupts drivers/net/ethernet/cavium/thunder/nic_main.c | 5 +- drivers/net/ethernet/cavium/thunder/thunder_bgx.c | 49 +- drivers/net/ethernet/cavium/thunder/thunder_bgx.h | 1 + drivers/net/ethernet/marvell/octeontx2/af/cgx.c| 193 drivers/net/ethernet/marvell/octeontx2/af/cgx.h| 10 +- .../net/ethernet/marvell/octeontx2/af/cgx_fw_if.h | 1 + drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 60 +-- drivers/net/ethernet/marvell/octeontx2/af/npc.h| 2 + drivers/net/ethernet/marvell/octeontx2/af/ptp.c| 4 +- drivers/net/ethernet/marvell/octeontx2/af/rvu.c| 26 ++ drivers/net/ethernet/marvell/octeontx2/af/rvu.h| 5 +- .../net/ethernet/marvell/octeontx2/af/rvu_cgx.c| 140 +++--- .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 17 +- .../ethernet/marvell/octeontx2/nic/otx2_common.c | 11 +- .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 498 ++--- .../ethernet/marvell/octeontx2/nic/otx2_flows.c| 42 +- .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 11 + drivers/soc/marvell/octeontx2-rm/otx2_rm.c | 9 + 18 files changed, 595 insertions(+), 489 deletions(-) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9572): https://lists.yoctoproject.org/g/linux-yocto/message/9572 Mute This Topic: https://lists.yoctoproject.org/mt/81451270/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] mtd: spi-nor: change the performance info print to dev_dbg
In commit e952a9418b16 ("s32gen1: qspi: Improve QSPI read performance"),
it introduced a performance indicators when performing a QSPI read
operation, while it is no much help for the flash function and
may cause some flash test fail due to the tons of infos. So downgrade
dev_info to dev_dbg to fix it.
Signed-off-by: Zhantao Tang
---
drivers/mtd/spi-nor/s32gen1_qspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/s32gen1_qspi.c
b/drivers/mtd/spi-nor/s32gen1_qspi.c
index 5af7086425b1..88a0f47d0cc5 100644
--- a/drivers/mtd/spi-nor/s32gen1_qspi.c
+++ b/drivers/mtd/spi-nor/s32gen1_qspi.c
@@ -973,7 +973,7 @@ int qspi_read_mem(struct fsl_qspi *q,
if (us_passed > 0) {
mb_int = div_u64_rem(op->data.nbytes, us_passed, );
mb_frac = div64_u64(rem * 1000, us_passed);
- dev_info(q->dev, "%u bytes read in %u us (%llu.%llu MB/s)\n",
+ dev_dbg(q->dev, "%u bytes read in %u us (%llu.%llu MB/s)\n",
op->data.nbytes, us_passed, mb_int, mb_frac);
}
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9571):
https://lists.yoctoproject.org/g/linux-yocto/message/9571
Mute This Topic: https://lists.yoctoproject.org/mt/81451077/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [linux-yocto v5.4/standard/nxp-s32g2xx]: mtd: spi-nor: change the performance info print to dev_dbg
Hi Bruce, In v5.4/standard/nxp-s32g2xx branch, the s32gen1 qspi introduced a performance indicator, it will print a performce info in every read operation, but it is no much help for the flash function and may cause some flash test fail due to the tons of infos. And the following patch is to fix this issue. Would you please help to merge this patch into linux-ycoto kernel, v5.4, branch is v5.4/standard/nxp-s32g2xx? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9570): https://lists.yoctoproject.org/g/linux-yocto/message/9570 Mute This Topic: https://lists.yoctoproject.org/mt/81451076/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.10/standard/ti-sdk-5.4/ti-j72xx][PATCH] ti-j72xx kernel part for linux-yocto kernel v5.10
Hi Bruce,
Could you please help to create a new kernel branch
"v5.10/standard/ti-sdk-5.4/ti-j72xx"
based on "v5.10/standard/base" for newly added bsp ti-j72xx on kernel
5.10 ?
And merge below patches to the new branch
"v5.10/standard/ti-sdk-5.4/ti-j72xx".
The following changes since commit 04a11eb4aec4efe3064f27b207e8a41c28bb08cd:
Merge tag 'v5.10.23' into v5.10/standard/base (2021-03-15 10:51:55 -0400)
are available in the Git repository at:
https://github.com/xulinsun/ti-j72x v5.10/standard/base
for you to fetch changes up to a55369ce499aa2b54424d73532ce3968db88f542:
dmabuf: revert the removed functions for adapting out-of-tree gpu
ti-img-rogue-driver (2021-03-19 13:24:33 +0800)
Anand Balagopalakrishnan (1):
arm64: dts: ti: k3-j721e-main: Add GPU node
Andrew F. Davis (16):
dt-bindings: gpu: Add binding for TI SGX
arm64: dts: ti: k3-am654-main: Add device tree entry for SGX
HACK: dt-bindings: misc: Add ti,dma_buf_phys binding doc
HACK: misc: Add dma-buf to physical address exporter
dt-bindings: soc: ti: Add TI PAT bindings
arm64: dts: ti: k3-j721e-main: Add MAIN domain PAT nodes
soc: ti: Add Support for the TI Page-based Address Translator (PAT)
HACK: misc: dma-buf-phys: Allow this driver to be built as a module
soc: ti: pruss: add pruss_{request,release}_mem_region() API
dt-bindings: net: Add TI-PRUeth bindings
dma-buf: heaps: Initialize during core instead of subsys
dma-buf: heaps: Add Carveout heap to dmabuf heaps
misc: sram: Add dma-heap-export reserved SRAM area type
misc: sram: dma-heap-export: Fix memory leak in dma-buf attach
misc: sram: DMA-Heaps exporter depends on DMA-Heaps framework
HACK: dma-buf: heaps: carveout: Add support for cached carveout heaps
Angela Stegmaier (1):
rpmsg: fix lockdep warnings in virtio rpmsg bus driver
Arnaud Pouliquen (1):
rpmsg: core: add API to get MTU
Aswath Govindraju (1):
phy: keystone: fix unused variable build warning
Benoit Parrot (26):
drm/omap: Add ability to check if requested plane modes can be
supported
drm/omap: Add ovl checking funcs to dispc_ops
drm/omap: introduce omap_hw_overlay
drm/omap: omap_plane: subclass drm_plane_state
drm/omap: Add global state as a private atomic object
drm/omap: dynamically assign hw overlays to planes
drm/omap: add plane_atomic_print_state support
drm/omap: Add a 'right overlay' to plane state
drm/atomic: integrate private objects with suspend/resume helpers
drm/omap: add omap_plane_reserve/release_wb
drm/omap: add WB support
HACK: Input: goodix: fix driver auto-loading
dt-bindings: media: Document OmniVision OV1063x driver
HACK: UAPI: Increasing VIDEO_MAX_FRAME/VB2_MAX_FRAME to 128
dt-binbings: media: ti-vpe: Document the VIP driver
media: ti-vpe: Add the VIP driver
drm/tidss: add has_writeback flag
drm/tidss: add WB to io resource map
drm/tidss: add WB specific register offsets
drm/tidss: add WB irq enable/status accessor
drm/tidss: Add RGB to YUV color conversion support
drm/tidss: Add WB config/setup helper
drm/tidss: add tidss_plane_reserve/release_wb
drm/tidss: add WB M2M driver
media: ti-vpe: vip: fix asd allocation scheme
arm64: dts: Add HDMI video to
k3-j721e-common-proc-board-infotainment.dtso
Bin Liu (9):
dt-bindings: serial: add binding documentation for TI PRU
software UART
serial: add pru software uart (pru_suart) driver
dt-bindings: pwm: add binding documentation for TI PRUSS PWM
pwm: core: populate the sysfs device into pwmchip
pwm: add pruss iep-based pwm driver
arm64: dts: add k3-am654-evm-prupwm.dtso
dt-bindings: serial: add binding documentation for TI PRUSS UART
serial: 8250: add pruss uart driver
serial: 8250: pruss: fix overflow in conversion build warning
Dave Gerlach (6):
dt-bindings: wkup_m3_ipc: Add vtt toggling bindings
wkup_m3_ipc: Add support for toggling VTT regulator
dt-bindings: wkup_m3_ipc: Add ti,io-isolation property
wkup_m3_ipc: Add support for IO Isolation
soc: ti: wkup_m3_ipc: Add support for i2c voltage scaling
soc: ti: wkup_m3_ipc: Add debug option to halt m3 in suspend
Faiz Abbas (15):
arm64: dts: ti: k3-j721e-main: Add SDHCI nodes
can: m_can: m_can_platform: Add support for enabling transceiver
through the STB line
arm64: dts: ti: k3-am65-mcu: Add Support for MCAN
arm64: dts: k3-am654-idk: Add Support for MCAN
arm64: dts: ti: k3-am65-main: Add Support for UHS modes
phy: ti: j721e-wiz: Don't configure wiz if its already configured
phy: cadence: cadence-sierra: Don't configure if any plls are
already locked
arm64: dts: k3-am654-base-board-sr1: Disable UHS modes in SR1.0
Re: [yocto] spidev.c ?
Hello John,
It seems that your target is configured correctly. Since you have all
the components you should and must have as SPI framework.
Namely I was looking for /sys/bus (since you must have an SPI bus
driver), and then /sys/class (since as my best understanding is that
SPI is a master/slave device), you must have class/). Others are
assumed, you added debug directories.
> When I separately build spidev.c as an .ko and try
> loading it, I get: "Device or resource busy"
This is understandable, since you already have included spidev.ko as
menuconfig value Y, so it is already present in the kernel, but as a
built-in part of the kernel (my best guess).
> root@arria10:~# lsmod
> Module Size Used by
> spi_altera 16384 0
> spidev 20480 0
I see that you did change the menuconfig, and made spidev to be M.
What I also see is that there are no dependencies between spidev and
spi_altera. This is what you really wanted?
> But there are NO udev files for the SPI devices
> defined in the DTSI file.
Could you, please, better explain this sentence? In more details (as
much as you can)?
Thank you,
Zee
___
On Thu, Mar 18, 2021 at 10:07 PM jchludzinski wrote:
>
> root@arria10:~# find /sys/ -name 'spi*'
>
> /sys/kernel/debug/clk/spi_m_clk
> /sys/kernel/debug/tracing/events/spi
> /sys/kernel/debug/tracing/events/spi/spi_controller_idle
> /sys/kernel/debug/tracing/events/spi/spi_controller_busy
> /sys/kernel/debug/tracing/events/spi/spi_message_submit
> /sys/kernel/debug/tracing/events/spi/spi_message_start
> /sys/kernel/debug/tracing/events/spi/spi_message_done
> /sys/kernel/debug/tracing/events/spi/spi_transfer_start
> /sys/kernel/debug/tracing/events/spi/spi_transfer_stop
> /sys/kernel/debug/regmap/spi0.0
> /sys/devices/platform/soc/ffda5000.spi/spi_master
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_async
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/spi0.0/statistics/spi_sync_immediate
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_async
> /sys/devices/platform/soc/ffda5000.spi/spi_master/spi0/statistics/spi_sync_immediate
> /sys/class/spidev
> /sys/class/spi_master
> /sys/class/spi_master/spi0
> /sys/firmware/devicetree/base/__symbols__/spi2
> /sys/firmware/devicetree/base/__symbols__/spi0
> /sys/firmware/devicetree/base/__symbols__/spin_ctrl_1
> /sys/firmware/devicetree/base/__symbols__/spi_m_clk
> /sys/firmware/devicetree/base/__symbols__/spi1
> /sys/firmware/devicetree/base/__symbols__/spin_ctrl_2
> /sys/firmware/devicetree/base/soc/spi@ff809000
> /sys/firmware/devicetree/base/soc/spi@ffda5000
> /sys/firmware/devicetree/base/soc/spi@ffda5000/resource-manager@0/spi-max-frequency
> /sys/firmware/devicetree/base/soc/clkmgr@ffd04000/clocks/spi_m_clk
> /sys/firmware/devicetree/base/soc/spi@ffda4000
> /sys/firmware/devicetree/base/spi@0xc00c0800
> /sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0
> /sys/firmware/devicetree/base/spi@0xc00c0800/spidev@0/spi-max-frequency
> /sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-controller
> /sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@200/spin-rph
> /sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller
> /sys/firmware/devicetree/base/testcase-data-2/fairway-1/ride@100/spin-controller-names
> /sys/firmware/devicetree/base/testcase-data-2/substation@100/motor-1/spin
> /sys/bus/platform/drivers/spi_altera
> /sys/bus/spi
> /sys/bus/spi/devices/spi0.0
> /sys/bus/spi/drivers/spi-nor
> /sys/bus/spi/drivers/altr_a10sr/spi0.0
> /sys/bus/spi/drivers/spidev
> /sys/module/spidev
> /sys/module/spidev/drivers/spi:spidev
> /sys/module/spi_altera
>
>
>
>
> On 2021-03-18 03:44, Zoran wrote:
>
> I am guessing here But what do you have while executing the
> following command being in /sys
> as root?
>
> root@arm:/sys# find . -name spi*
>
> Zee
> ___
>
> On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
> lists.yoctoproject.org
> wrote:
>
>
> In the YOCTO/Linux source tree there's drivers/spi/ which has all the source
> for SPI drivers. There's only 1 file, spidev.c, which has:
>
> static int __init spidev_init(void)
> {
> int status;
>
> /* Claim our 256 reserved device numbers. Then register a class
> * that will key udev/mdev to add/remove /dev nodes. Last, register
> * the driver which manages those device numbers.
> */
> BUILD_BUG_ON(N_SPI_MINORS > 256);
> status = register_chrdev(SPIDEV_MAJOR, "spi", _fops);
> if (status < 0)
> return status;
>
> spidev_class = class_create(THIS_MODULE, "spidev");
> if
