[linux-yocto] [kernel v5.10/standard/nxp-sdk-5.4/nxp-imx8][PATCH] PCI: imx: Update the method of obtaining PCI bridge resources to correctly identify the pci device
The PCI bridge resources are stored in pci_host_bridge.windows,
mem_base under pcie_port has been removed, so update the resources
interface to correctly identify pcie device
Signed-off-by: Xiaolei Wang
---
drivers/pci/controller/dwc/pci-imx6.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/controller/dwc/pci-imx6.c
b/drivers/pci/controller/dwc/pci-imx6.c
index 2bb46bc02c1b..1afae9d4b7c0 100644
--- a/drivers/pci/controller/dwc/pci-imx6.c
+++ b/drivers/pci/controller/dwc/pci-imx6.c
@@ -1987,10 +1987,13 @@ static u64 imx6_pcie_cpu_addr_fixup(struct dw_pcie
*pcie, u64 cpu_addr)
struct dw_pcie_ep *ep = >ep;
struct pcie_port *pp = >pp;
struct imx6_pcie *imx6_pcie = to_imx6_pcie(pcie);
+ struct resource_entry *entry;
- if (imx6_pcie->drvdata->mode == DW_PCIE_RC_TYPE)
- offset = pp->mem_base;
- else
+ if (imx6_pcie->drvdata->mode == DW_PCIE_RC_TYPE) {
+ entry = resource_list_first_type(>bridge->windows,
+IORESOURCE_MEM);
+ offset = entry->res->start;
+ } else
offset = ep->phys_base;
if (imx6_pcie->drvdata->flags & IMX6_PCIE_FLAG_IMX6_CPU_ADDR_FIXUP)
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9597):
https://lists.yoctoproject.org/g/linux-yocto/message/9597
Mute This Topic: https://lists.yoctoproject.org/mt/81517591/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
On Sun, Mar 21, 2021 at 9:57 PM Khem Raj wrote: > > On Sun, Mar 21, 2021 at 6:43 PM Bruce Ashfield > wrote: > > > > On Sun, Mar 21, 2021 at 9:42 PM Khem Raj wrote: > > > > > > All warnings seems to fixed !! its on to do_compile now, so all seem to > > > work > > > > > > > Mine seemed to work as well, so I sent the SRCREV bump to OE core just > > now. There's no > > need to wait on it, since we know it is definitely better :D > > > > If there are compile or boot issues, we can tweak the config more in > > follow up patches. > > Just booted an extensive wayland/weston/musl image and it all comes up fine > with graphics working so we are good > > > root@qemuppc64:~# uname -a > Linux qemuppc64 5.10.23-yocto-standard #1 SMP PREEMPT Mon Mar 22 > 01:40:26 UTC 2021 ppc64le ppc64le ppc64le GNU/Linux > Awesome! Bruce > > > > > Bruce > > > > > On Sun, Mar 21, 2021 at 6:39 PM Khem Raj wrote: > > > > > > > > you changes are more complete then mine, thanks for taking care of > > > > this. I am testing latest tip now > > > > > > > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > > b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > > index 9c122832f4..ae4eea0096 100644 > > > > --- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > > @@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= > > > > "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > > SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > > SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b" > > > > SRCREV_machine ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > > -SRCREV_meta ?= "f5babefa399359d7a5f880342c03ced78dbd48d2" > > > > +SRCREV_meta ?= "c0cfc016a512f4b2922e15e43e3d4b421cdceb97" > > > > > > > > # remap qemuarm to qemuarma15 for the 5.8 kernel > > > > # KMACHINE_qemuarm ?= "qemuarma15" > > > > > > > > lets see what I see > > > > > > > > On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield > > > > wrote: > > > > > > > > > > Heh. > > > > > > > > > > If you check the kernel-cache, I just made the same changes (with one > > > > > additional): > > > > > > > > > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > > > > > > > > > So we are in sync! > > > > > > > > > > Bruce > > > > > > > > > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > > > > > > > > > These options end up with 'n' in qemuppc64 anyway > > > > > > > > > > > > Signed-off-by: Khem Raj > > > > > > Cc: Bruce Ashfield > > > > > > --- > > > > > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > > > > > 1 file changed, 2 deletions(-) > > > > > > > > > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > > b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > > index 68912490..402b04ec 100644 > > > > > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > > > > > CONFIG_NR_CPUS=2 > > > > > > CONFIG_NR_IRQS=512 > > > > > > CONFIG_PPC=y > > > > > > -CONFIG_SYSVIPC_COMPAT=y > > > > > > CONFIG_GENERIC_BUG=y > > > > > > CONFIG_EPAPR_BOOT=y > > > > > > CONFIG_PPC_PSERIES=y > > > > > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > > > > > CONFIG_IBMVETH=y > > > > > > CONFIG_NET_VENDOR_INTEL=y > > > > > > CONFIG_E1000=y > > > > > > -CONFIG_VMXNET3=y > > > > > > CONFIG_TTY=y > > > > > > CONFIG_VT=y > > > > > > CONFIG_VT_HW_CONSOLE_BINDING=y > > > > > > -- > > > > > > 2.31.0 > > > > > > > > > > > > > > > > > > > > > -- > > > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > > > thee at its end > > > > > - "Use the force Harry" - Gandalf, Star Trek II > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9596): https://lists.yoctoproject.org/g/linux-yocto/message/9596 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
On Sun, Mar 21, 2021 at 6:43 PM Bruce Ashfield wrote: > > On Sun, Mar 21, 2021 at 9:42 PM Khem Raj wrote: > > > > All warnings seems to fixed !! its on to do_compile now, so all seem to work > > > > Mine seemed to work as well, so I sent the SRCREV bump to OE core just > now. There's no > need to wait on it, since we know it is definitely better :D > > If there are compile or boot issues, we can tweak the config more in > follow up patches. Just booted an extensive wayland/weston/musl image and it all comes up fine with graphics working so we are good root@qemuppc64:~# uname -a Linux qemuppc64 5.10.23-yocto-standard #1 SMP PREEMPT Mon Mar 22 01:40:26 UTC 2021 ppc64le ppc64le ppc64le GNU/Linux > > Bruce > > > On Sun, Mar 21, 2021 at 6:39 PM Khem Raj wrote: > > > > > > you changes are more complete then mine, thanks for taking care of > > > this. I am testing latest tip now > > > > > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > index 9c122832f4..ae4eea0096 100644 > > > --- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > > @@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= > > > "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b" > > > SRCREV_machine ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > > -SRCREV_meta ?= "f5babefa399359d7a5f880342c03ced78dbd48d2" > > > +SRCREV_meta ?= "c0cfc016a512f4b2922e15e43e3d4b421cdceb97" > > > > > > # remap qemuarm to qemuarma15 for the 5.8 kernel > > > # KMACHINE_qemuarm ?= "qemuarma15" > > > > > > lets see what I see > > > > > > On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield > > > wrote: > > > > > > > > Heh. > > > > > > > > If you check the kernel-cache, I just made the same changes (with one > > > > additional): > > > > > > > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > > > > > > > So we are in sync! > > > > > > > > Bruce > > > > > > > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > > > > > > > These options end up with 'n' in qemuppc64 anyway > > > > > > > > > > Signed-off-by: Khem Raj > > > > > Cc: Bruce Ashfield > > > > > --- > > > > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > > > > 1 file changed, 2 deletions(-) > > > > > > > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > index 68912490..402b04ec 100644 > > > > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > > > > CONFIG_NR_CPUS=2 > > > > > CONFIG_NR_IRQS=512 > > > > > CONFIG_PPC=y > > > > > -CONFIG_SYSVIPC_COMPAT=y > > > > > CONFIG_GENERIC_BUG=y > > > > > CONFIG_EPAPR_BOOT=y > > > > > CONFIG_PPC_PSERIES=y > > > > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > > > > CONFIG_IBMVETH=y > > > > > CONFIG_NET_VENDOR_INTEL=y > > > > > CONFIG_E1000=y > > > > > -CONFIG_VMXNET3=y > > > > > CONFIG_TTY=y > > > > > CONFIG_VT=y > > > > > CONFIG_VT_HW_CONSOLE_BINDING=y > > > > > -- > > > > > 2.31.0 > > > > > > > > > > > > > > > > > -- > > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > > thee at its end > > > > - "Use the force Harry" - Gandalf, Star Trek II > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9595): https://lists.yoctoproject.org/g/linux-yocto/message/9595 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
On Sun, Mar 21, 2021 at 9:42 PM Khem Raj wrote: > > All warnings seems to fixed !! its on to do_compile now, so all seem to work > Mine seemed to work as well, so I sent the SRCREV bump to OE core just now. There's no need to wait on it, since we know it is definitely better :D If there are compile or boot issues, we can tweak the config more in follow up patches. Bruce > On Sun, Mar 21, 2021 at 6:39 PM Khem Raj wrote: > > > > you changes are more complete then mine, thanks for taking care of > > this. I am testing latest tip now > > > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > index 9c122832f4..ae4eea0096 100644 > > --- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > +++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > > @@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= > > "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b" > > SRCREV_machine ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > > -SRCREV_meta ?= "f5babefa399359d7a5f880342c03ced78dbd48d2" > > +SRCREV_meta ?= "c0cfc016a512f4b2922e15e43e3d4b421cdceb97" > > > > # remap qemuarm to qemuarma15 for the 5.8 kernel > > # KMACHINE_qemuarm ?= "qemuarma15" > > > > lets see what I see > > > > On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield > > wrote: > > > > > > Heh. > > > > > > If you check the kernel-cache, I just made the same changes (with one > > > additional): > > > > > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > > > > > So we are in sync! > > > > > > Bruce > > > > > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > > > > > These options end up with 'n' in qemuppc64 anyway > > > > > > > > Signed-off-by: Khem Raj > > > > Cc: Bruce Ashfield > > > > --- > > > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > > > 1 file changed, 2 deletions(-) > > > > > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > index 68912490..402b04ec 100644 > > > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > > > CONFIG_NR_CPUS=2 > > > > CONFIG_NR_IRQS=512 > > > > CONFIG_PPC=y > > > > -CONFIG_SYSVIPC_COMPAT=y > > > > CONFIG_GENERIC_BUG=y > > > > CONFIG_EPAPR_BOOT=y > > > > CONFIG_PPC_PSERIES=y > > > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > > > CONFIG_IBMVETH=y > > > > CONFIG_NET_VENDOR_INTEL=y > > > > CONFIG_E1000=y > > > > -CONFIG_VMXNET3=y > > > > CONFIG_TTY=y > > > > CONFIG_VT=y > > > > CONFIG_VT_HW_CONSOLE_BINDING=y > > > > -- > > > > 2.31.0 > > > > > > > > > > > > > -- > > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > > thee at its end > > > - "Use the force Harry" - Gandalf, Star Trek II -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9594): https://lists.yoctoproject.org/g/linux-yocto/message/9594 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
All warnings seems to fixed !! its on to do_compile now, so all seem to work On Sun, Mar 21, 2021 at 6:39 PM Khem Raj wrote: > > you changes are more complete then mine, thanks for taking care of > this. I am testing latest tip now > > diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > index 9c122832f4..ae4eea0096 100644 > --- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb > +++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb > @@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= > "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b" > SRCREV_machine ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" > -SRCREV_meta ?= "f5babefa399359d7a5f880342c03ced78dbd48d2" > +SRCREV_meta ?= "c0cfc016a512f4b2922e15e43e3d4b421cdceb97" > > # remap qemuarm to qemuarma15 for the 5.8 kernel > # KMACHINE_qemuarm ?= "qemuarma15" > > lets see what I see > > On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield > wrote: > > > > Heh. > > > > If you check the kernel-cache, I just made the same changes (with one > > additional): > > > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > > > So we are in sync! > > > > Bruce > > > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > > > These options end up with 'n' in qemuppc64 anyway > > > > > > Signed-off-by: Khem Raj > > > Cc: Bruce Ashfield > > > --- > > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > > 1 file changed, 2 deletions(-) > > > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > index 68912490..402b04ec 100644 > > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > > CONFIG_NR_CPUS=2 > > > CONFIG_NR_IRQS=512 > > > CONFIG_PPC=y > > > -CONFIG_SYSVIPC_COMPAT=y > > > CONFIG_GENERIC_BUG=y > > > CONFIG_EPAPR_BOOT=y > > > CONFIG_PPC_PSERIES=y > > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > > CONFIG_IBMVETH=y > > > CONFIG_NET_VENDOR_INTEL=y > > > CONFIG_E1000=y > > > -CONFIG_VMXNET3=y > > > CONFIG_TTY=y > > > CONFIG_VT=y > > > CONFIG_VT_HW_CONSOLE_BINDING=y > > > -- > > > 2.31.0 > > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9593): https://lists.yoctoproject.org/g/linux-yocto/message/9593 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
you changes are more complete then mine, thanks for taking care of this. I am testing latest tip now diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb b/meta/recipes-kernel/linux/linux-yocto_5.10.bb index 9c122832f4..ae4eea0096 100644 --- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb +++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb @@ -23,7 +23,7 @@ SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b" SRCREV_machine ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" -SRCREV_meta ?= "f5babefa399359d7a5f880342c03ced78dbd48d2" +SRCREV_meta ?= "c0cfc016a512f4b2922e15e43e3d4b421cdceb97" # remap qemuarm to qemuarma15 for the 5.8 kernel # KMACHINE_qemuarm ?= "qemuarma15" lets see what I see On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield wrote: > > Heh. > > If you check the kernel-cache, I just made the same changes (with one > additional): > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > So we are in sync! > > Bruce > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > These options end up with 'n' in qemuppc64 anyway > > > > Signed-off-by: Khem Raj > > Cc: Bruce Ashfield > > --- > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > 1 file changed, 2 deletions(-) > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg > > index 68912490..402b04ec 100644 > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > CONFIG_NR_CPUS=2 > > CONFIG_NR_IRQS=512 > > CONFIG_PPC=y > > -CONFIG_SYSVIPC_COMPAT=y > > CONFIG_GENERIC_BUG=y > > CONFIG_EPAPR_BOOT=y > > CONFIG_PPC_PSERIES=y > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > CONFIG_IBMVETH=y > > CONFIG_NET_VENDOR_INTEL=y > > CONFIG_E1000=y > > -CONFIG_VMXNET3=y > > CONFIG_TTY=y > > CONFIG_VT=y > > CONFIG_VT_HW_CONSOLE_BINDING=y > > -- > > 2.31.0 > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9592): https://lists.yoctoproject.org/g/linux-yocto/message/9592 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
oh cool thanks :) On Sun, Mar 21, 2021 at 6:34 PM Bruce Ashfield wrote: > > Heh. > > If you check the kernel-cache, I just made the same changes (with one > additional): > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c > > So we are in sync! > > Bruce > > On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > > > These options end up with 'n' in qemuppc64 anyway > > > > Signed-off-by: Khem Raj > > Cc: Bruce Ashfield > > --- > > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > > 1 file changed, 2 deletions(-) > > > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg > > index 68912490..402b04ec 100644 > > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > > @@ -6,7 +6,6 @@ CONFIG_SMP=y > > CONFIG_NR_CPUS=2 > > CONFIG_NR_IRQS=512 > > CONFIG_PPC=y > > -CONFIG_SYSVIPC_COMPAT=y > > CONFIG_GENERIC_BUG=y > > CONFIG_EPAPR_BOOT=y > > CONFIG_PPC_PSERIES=y > > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > > CONFIG_IBMVETH=y > > CONFIG_NET_VENDOR_INTEL=y > > CONFIG_E1000=y > > -CONFIG_VMXNET3=y > > CONFIG_TTY=y > > CONFIG_VT=y > > CONFIG_VT_HW_CONSOLE_BINDING=y > > -- > > 2.31.0 > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9591): https://lists.yoctoproject.org/g/linux-yocto/message/9591 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
Heh. If you check the kernel-cache, I just made the same changes (with one additional): https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?id=3f21857300e44105375dafefaa0a6c4be657560c So we are in sync! Bruce On Sun, Mar 21, 2021 at 9:31 PM Khem Raj wrote: > > These options end up with 'n' in qemuppc64 anyway > > Signed-off-by: Khem Raj > Cc: Bruce Ashfield > --- > bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg > index 68912490..402b04ec 100644 > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > @@ -6,7 +6,6 @@ CONFIG_SMP=y > CONFIG_NR_CPUS=2 > CONFIG_NR_IRQS=512 > CONFIG_PPC=y > -CONFIG_SYSVIPC_COMPAT=y > CONFIG_GENERIC_BUG=y > CONFIG_EPAPR_BOOT=y > CONFIG_PPC_PSERIES=y > @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y > CONFIG_IBMVETH=y > CONFIG_NET_VENDOR_INTEL=y > CONFIG_E1000=y > -CONFIG_VMXNET3=y > CONFIG_TTY=y > CONFIG_VT=y > CONFIG_VT_HW_CONSOLE_BINDING=y > -- > 2.31.0 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9590): https://lists.yoctoproject.org/g/linux-yocto/message/9590 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [kernel-cache][master/yocto-5.10][PATCH] qemu-ppc64: Remove SYSVIPC_COMPAT and VMXNET3
These options end up with 'n' in qemuppc64 anyway Signed-off-by: Khem Raj Cc: Bruce Ashfield --- bsp/qemu-ppc64/qemu-ppc64.cfg | 2 -- 1 file changed, 2 deletions(-) diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg index 68912490..402b04ec 100644 --- a/bsp/qemu-ppc64/qemu-ppc64.cfg +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -6,7 +6,6 @@ CONFIG_SMP=y CONFIG_NR_CPUS=2 CONFIG_NR_IRQS=512 CONFIG_PPC=y -CONFIG_SYSVIPC_COMPAT=y CONFIG_GENERIC_BUG=y CONFIG_EPAPR_BOOT=y CONFIG_PPC_PSERIES=y @@ -26,7 +25,6 @@ CONFIG_NET_VENDOR_IBM=y CONFIG_IBMVETH=y CONFIG_NET_VENDOR_INTEL=y CONFIG_E1000=y -CONFIG_VMXNET3=y CONFIG_TTY=y CONFIG_VT=y CONFIG_VT_HW_CONSOLE_BINDING=y -- 2.31.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9589): https://lists.yoctoproject.org/g/linux-yocto/message/9589 Mute This Topic: https://lists.yoctoproject.org/mt/81515060/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][PATCH] qemu-ppc64.cfg: Do not set CONFIG_POWER4
Applied. The tools are also picking up some other warnings in my local testing (with fixes that aren't yet sent for merging). You saw this due to a bug in my proposed patch, but the issue is valid (along with the other ones I found). I've fixed them all and will send them in my next pull request (coming probably Monday). Bruce On Sun, Mar 21, 2021 at 5:34 PM Khem Raj wrote: > > This is disabled in final defconfig anyway > > Signed-off-by: Khem Raj > Cc: Bruce Ashfield > --- > bsp/qemu-ppc64/qemu-ppc64.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg > index 2bf1684d..f48a0136 100644 > --- a/bsp/qemu-ppc64/qemu-ppc64.cfg > +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg > @@ -2,7 +2,6 @@ > CONFIG_PPC64=y > CONFIG_PPC_BOOK3S_64=y > CONFIG_GENERIC_CPU=y > -CONFIG_POWER4=y > CONFIG_SMP=y > CONFIG_NR_CPUS=2 > CONFIG_CPU_BIG_ENDIAN=y > -- > 2.31.0 > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9588): https://lists.yoctoproject.org/g/linux-yocto/message/9588 Mute This Topic: https://lists.yoctoproject.org/mt/81510394/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [kernel-cache][master/yocto-5.10][PATCH] qemu-ppc64: Remove duplicated CONFIG_CPU_BIG_ENDIAN
Default qemuppc64 is LE now a days Signed-off-by: Khem Raj Cc: Bruce Ashfield --- bsp/qemu-ppc64/qemu-ppc64.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg index f48a0136..68912490 100644 --- a/bsp/qemu-ppc64/qemu-ppc64.cfg +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -4,7 +4,6 @@ CONFIG_PPC_BOOK3S_64=y CONFIG_GENERIC_CPU=y CONFIG_SMP=y CONFIG_NR_CPUS=2 -CONFIG_CPU_BIG_ENDIAN=y CONFIG_NR_IRQS=512 CONFIG_PPC=y CONFIG_SYSVIPC_COMPAT=y -- 2.31.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9587): https://lists.yoctoproject.org/g/linux-yocto/message/9587 Mute This Topic: https://lists.yoctoproject.org/mt/81514936/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [kernel-cache][yocto-5.10][PATCH] qemu-ppc64.cfg: Do not set CONFIG_POWER4
This is disabled in final defconfig anyway Signed-off-by: Khem Raj Cc: Bruce Ashfield --- bsp/qemu-ppc64/qemu-ppc64.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg index 2bf1684d..f48a0136 100644 --- a/bsp/qemu-ppc64/qemu-ppc64.cfg +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -2,7 +2,6 @@ CONFIG_PPC64=y CONFIG_PPC_BOOK3S_64=y CONFIG_GENERIC_CPU=y -CONFIG_POWER4=y CONFIG_SMP=y CONFIG_NR_CPUS=2 CONFIG_CPU_BIG_ENDIAN=y -- 2.31.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9586): https://lists.yoctoproject.org/g/linux-yocto/message/9586 Mute This Topic: https://lists.yoctoproject.org/mt/81510422/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [kernel-cache][PATCH] qemu-ppc64.cfg: Do not set CONFIG_POWER4
This is disabled in final defconfig anyway Signed-off-by: Khem Raj Cc: Bruce Ashfield --- bsp/qemu-ppc64/qemu-ppc64.cfg | 1 - 1 file changed, 1 deletion(-) diff --git a/bsp/qemu-ppc64/qemu-ppc64.cfg b/bsp/qemu-ppc64/qemu-ppc64.cfg index 2bf1684d..f48a0136 100644 --- a/bsp/qemu-ppc64/qemu-ppc64.cfg +++ b/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -2,7 +2,6 @@ CONFIG_PPC64=y CONFIG_PPC_BOOK3S_64=y CONFIG_GENERIC_CPU=y -CONFIG_POWER4=y CONFIG_SMP=y CONFIG_NR_CPUS=2 CONFIG_CPU_BIG_ENDIAN=y -- 2.31.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9585): https://lists.yoctoproject.org/g/linux-yocto/message/9585 Mute This Topic: https://lists.yoctoproject.org/mt/81510394/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] spidev.c ?
> // interrupt-parent = <>;
> // interrupts = <0 24 IRQ_TYPE_EDGE_FALLING>;
Not sure if you did represent these values correctly?!
I have for enc28j60:something like this:
interrupt-parent = <>;
interrupts = <1 IRQ_TYPE_EDGE_FALLING>;
Where <> is gpio chip name (the gpio port 2),
and <1 IRQ_TYPE_EDGE_FALLING>;is pin 1 of port 2 (32 pins for ports
from port 0).
<> should be an INT controller.
Since <0 24 IRQ_TYPE_EDGE_FALLING>; you are trying to represent 0 as
port #, 24 as pin #...
I have no idea how many pins you have per gpio port? 16? 32?
You should carefully analyse and try to understand if you wrote this
device tree sequence correctly.
But I am just guessing now...
Zee
___
On Sat, Mar 20, 2021 at 11:02 PM jchludzinski wrote:
>
> Using 'make nconfig' I selected the following options:
> (Keep in mind I using an Altera/Intel Arria 10 SoC which uses DesignWare hard
> SPI controllers. BUT the SPI controllers I'm concerned with now are soft
> controllers defined in the FPGA code).
>
> .config - Linux/arm 5.4.74 Kernel Configuration
> ┌── SPI support
> ─┐
> │
> │
> │--- SPI support
> │
> │[*] Debug support for SPI drivers
> │
> │-*- SPI memory extension
> │
> │ *** SPI Master Controller Drivers ***
> │
> │ Altera SPI Controller
>
> ...
>
> │<*> Utilities for Bitbanging SPI masters
> │
> │< > Cadence SPI controller
> │
> │< > CLPS711X host SPI controller
> │
> │<*> DesignWare SPI controller core support
> │
> │<*> PCI interface driver for DW SPI core
> │
> │<*> Memory-mapped io interface driver for
> DW SPI core │
>
> ...
>
> │ *** SPI Protocol Masters ***
> │
> │ User mode SPI device driver support
> │
> │ spi loopback test framework support
> │
> │< > Infineon TLE62X0 (for power switching)
> │
> │[*] SPI slave protocol handlers
> │
> │ SPI slave handler reporting boot up
> time│
> │ SPI slave handler controlling system
> state │
>
> This got the SPI nodes to show up in /sys/firmware/devicetree/ but there were
> no udev files (/dev/spidevXX). So I commented out the 'interrupts' in the
> DTSI file and the udev files appeared?
>
> spi2: spi@0xc00c0800 { // hps_spi_1553_int
>address-cells = <0x1>;
>#size-cells = <0x0>;
>reg = <0xc00c0800 0x20>;
>// interrupt-parent = <>;
>// interrupts = <0 24 IRQ_TYPE_EDGE_FALLING>;
>num-cs = <0x1>;
>status = "okay";
>
>spidev@0 {
> compatible = "rohm,dh2228fv";
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> reg = <0x0>;
> spi-max-frequency = <0x1f400>;
> // enable-dma = <0x1>;
>};
> };
>
> BUT I need those interrupts. Thoughts and/or suggestions?
>
> ---John
>
>
>
> On 2021-03-19 01:10, Zoran wrote:
>
> 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
Re: [yocto] How is it possible to build a loadable module from spi-altera.c ...?
My problem is I have an 1553 chip (an avionic data bus) connected to the
HPS master (an ARM processor) via an FPGA (soft) SPI controller. This is
where the spi-altera.c comes in. It provides the driver/interface to the
soft SPI controller on the Arria 10 SoC.
I need an interface now to communicate between the SPI slave (the 1553
chip) and the SPI master (the Arria 10 HPS/ARM).
When I load _spi-altera.ko_ I get the _udev_ files (_/dev/spidevXX_) but
not when I load _spidev.ko._ Why? _spi-altera.c _doesn't have an _init_
routine and consequently no call to _register_chrdev_(..) but _spidev.c_
does. What's the relationship between _spi-altera_ and _spidev_? What's
the purpose of _spi.c_?
On 2021-03-20 18:14, jchludzinski wrote:
How is it possible to build a loadable module from _spi-altera.c_ when
it has no code for creating _udev_ files (i.e., _/dev/spidevXX_); it
has no:
static int __init spidev_init(void)
{
int status;
printk(KERN_ALERT "DEBUG: Passed %s %d \n", __FUNCTION__,
__LINE__);
/* 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);
printk(KERN_ALERT "DEBUG: Passed %s %d \n", __FUNCTION__,
__LINE__);
if (status < 0)
return status;
printk(KERN_ALERT "DEBUG: Passed %s %d \n", __FUNCTION__,
__LINE__);
spidev_class = class_create(THIS_MODULE, "spidev");
if (IS_ERR(spidev_class)) {
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
return PTR_ERR(spidev_class);
}
printk(KERN_ALERT "DEBUG: Passed %s %d \n", __FUNCTION__,
__LINE__);
status = spi_register_driver(_spi_driver);
if (status < 0) {
class_destroy(spidev_class);
unregister_chrdev(SPIDEV_MAJOR,
spidev_spi_driver.driver.name);
}
printk(KERN_ALERT "DEBUG: Passed %s %d \n", __FUNCTION__,
__LINE__);
return status;
}
module_init(spidev_init);
The _printk_'s are of course mine.
---John
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52784): https://lists.yoctoproject.org/g/yocto/message/52784
Mute This Topic: https://lists.yoctoproject.org/mt/81489140/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
