[PATCH] bsps/zynqmp: Use correct include path

The existing include path only works from inside the RTEMS build. This fixes the include path to work both in the RTEMS build and with builds of external apps since this file gets installed with the BSP. --- bsps/aarch64/xilinx-zynqmp/include/bsp/jffs2_xqspipsu.h | 2 +- 1 file changed, 1 insertio

[PATCH 4/4] bsps/zynqmp: Add JFFS2 NAND adapter

This adds the glue code necessary to allow JFFS2 to operate on top of NAND memory hosted by the XNandPsu peripheral/driver. --- .../include/bsp/jffs2_xnandpsu.h | 56 +++ bsps/aarch64/xilinx-zynqmp/jffs2_xnandpsu.c | 326 ++ .../bsps/aarch64/xilinx-zynqmp/grp_zu3eg.

[PATCH 2/4] cpukit/jffs2: Import wbuf.c from upstream

This pulls in wbuf.c from the upstream Linux repository at the state specified in VERSION. --- cpukit/libfs/src/jffs2/VERSION|1 + cpukit/libfs/src/jffs2/src/wbuf.c | 1350 + 2 files changed, 1351 insertions(+) create mode 100644 cpukit/libfs/src/jffs2/src/wbuf

[PATCH 3/4] cpukit/jffs2: Add support for NAND under JFFS2

This adds write buffer and bad block support required for JFFS2 operation on NAND devices. This also adds the minor modifications necessary for RTEMS support in the Linux header stubs and in wbuf.c. Memory and NOR backed applications should experience no difference in operation since they do not ex

[PATCH 0/4] JFFS2 NAND Support

This patch set adds NAND support for flash up to just under 4GB in size by way of write buffer support and an example adapter for ZynqMP systems using the XNandPsu peripheral. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinf

[PATCH 1/4] cpukit/jffs2: Initialize and lock mutexes

Mutexes must be locked before they can be unlocked. JFFS2 doesn't currently see this as an issue because all mutex operations are no-ops. --- cpukit/libfs/src/jffs2/src/dir-rtems.c | 2 ++ cpukit/libfs/src/jffs2/src/fs-rtems.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/cpukit/libfs/sr

[PATCH] bsps/xnandpsu: Allow use of both chip selects

By default, the Xilinx NAND driver does not probe the second chip select. This alteration allows the second half of chips to be detected when present. --- bsps/include/dev/nand/xnandpsu.h | 4 1 file changed, 4 insertions(+) diff --git a/bsps/include/dev/nand/xnandpsu.h b/bsps/include/dev/na

Re: [lwip 2/2] Move and rename sys_arch_data_sync_barier()

On Thu, Mar 9, 2023 at 7:48 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 09.03.23 14:46, Kinsey Moore wrote: > > Normally with rtems-lwip I would complain that this doesn't follow the > > convention of using #ifdef __rtems__ to modify files from

Re: [lwip 1/2] Fix build for arm/tms570 BSPs

The changes to TI sources for dp83848h should use the #ifdef __rtems__ convention since they will not be fully integrated into the rtemslwip directory. Kinsey On Thu, Mar 9, 2023 at 6:13 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > --- > defs/bsps/arm/tms570_base.json

Re: [lwip 2/2] Move and rename sys_arch_data_sync_barier()

Normally with rtems-lwip I would complain that this doesn't follow the convention of using #ifdef __rtems__ to modify files from upstream sources (each root directory except rtemslwip has an upstream source), but the uLan authors have given permission to fully integrate this code into the rtemslwip

Re: [PATCH rtems-docs v2] c-user/chains: Correct iteration example code

On Thu, Mar 9, 2023 at 1:01 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > > On 09.03.23 03:33, Kinsey Moore wrote: > > Casting the node returned by rtems_chain_head is incorrect. That node is > > owned by the control structure and use of it post-

[PATCH rtems-docs v2] c-user/chains: Correct iteration example code

Casting the node returned by rtems_chain_head is incorrect. That node is owned by the control structure and use of it post-cast could cause memory corruption. --- c-user/chains.rst | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/c-user/chains.rst b/c-user/chains.rst index

Re: [PATCH rtems-docs] c-user/chains: Correct iteration example code

On Wed, Mar 8, 2023 at 3:47 PM Chris Johns wrote: > > > On 9/3/2023 5:40 am, Kinsey Moore wrote: > > Casting the node returned by rtems_chain_head is incorrect. That node is > > owned by the control structure and use of it post-cast could cause > > memory corr

[PATCH rtems-docs] c-user/chains: Correct iteration example code

Casting the node returned by rtems_chain_head is incorrect. That node is owned by the control structure and use of it post-cast could cause memory corruption. --- c-user/chains.rst | 4 1 file changed, 4 insertions(+) diff --git a/c-user/chains.rst b/c-user/chains.rst index f518ef4..e791d10

Re: [PATCH] build: Print item UID in case of errors

Looks good. A welcome improvement for anyone working on the build system. Kinsey On Mon, Mar 6, 2023 at 9:40 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > This helps to identify issues in build items. > --- > wscript | 14 -- > 1 file changed, 12 insertions(+), 2

Re: [PATCH rtems-libbsd v2 0/2] Update the CGEM driver

On Sat, Mar 4, 2023 at 3:21 AM Karel Gardas wrote: > > One remark as an random observer here. > "branch 6-freebsd-12" has caught my eyes. Let me ask shouldn't > development patches go into the master branch from which they may be > later cherry-picked if needed and pushed into 6-freebsd-12 branch

Re: [PATCH rtems-libbsd v2 0/2] Update the CGEM driver

These patches look good to me. Thanks for this contribution! Kinsey On Fri, Mar 3, 2023 at 9:54 AM Padmarao Begari < padmarao.beg...@microchip.com> wrote: > Update the CGEM driver with adding the phy address and > the clock to read it from the device tree. > > The patches are based upon latest

Re: RTEMS LwIP licensing and organization cleanup proposal

Hello Pavel, As discussed on discord, I have created a ticket to resolve this issue: https://devel.rtems.org/ticket/4867 Please see the ticket for further details and further constraining the desired solution. Kinsey On Fri, Mar 3, 2023 at 7:32 AM Pavel Pisa wrote: > Dear Premek and other deve

[PATCH rtems-lwip 3/3] rtemslwip: Use interrupt server for ISRs

- /dev/null +++ b/rtemslwip/common/netstart_shared.c @@ -0,0 +1,40 @@ +/* + * Copyright (C) 2023 On-Line Applications Research Corporation (OAR) + * Written by Kinsey Moore + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the fol

[PATCH rtems-lwip 1/3] lwip/sockets.h: Avoid duplication of system struct

Excise another portion of lwIP's headers that redefine structures available from toolchain headers. --- lwip/src/include/lwip/sockets.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/lwip/src/include/lwip/sockets.h b/lwip/src/include/lwip/sockets.h index 705ae46..3f7ee32 100

[PATCH rtems-lwip 2/3] lwip/api: Notify about dropped packets

The receive UDP and raw mailboxes will silently drop packets once the mailbox is full. This provides a debug message if debugging is enabled when this is the case to direct the user toward a solution. --- lwip/src/api/api_msg.c | 8 1 file changed, 8 insertions(+) diff --git a/lwip/src/a

Re: [PATCH rtems-source-builder 2/2] 6/rtems-default.bset: Update binutils version to 2.40

On Thu, Mar 2, 2023 at 8:07 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Joel, > > it seems that the update to Binutils 2.40 causes some issues on aarch64: > > 15:06:49 runner ['/opt/rtems/6-test/bin/aarch64-rtems6-gcc', > 'testsuites/sptests/spconfig01/init.c.682.o', >

[PATCH] bsps/aarch64: Disable interrupts during MMU remap

Interrupts must be disabled during MMU remapping since the majority of RTEMS including interrupts expects normal memory mapping semantics such as unaligned accesses. --- bsps/aarch64/shared/mmu/vmsav8-64.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/bsps/aarch64/shared/mmu/vmsav8-64.

[PATCH rtems-release] rtems-notes-6.1.md: Add AArch64 and MicroBlaze

Add the AArch64 and MicroBlaze architectures to the 6.1 release notes along with the BSPs that have been added for them. --- notes/rtems-notes-6.1.md | 14 ++ 1 file changed, 14 insertions(+) diff --git a/notes/rtems-notes-6.1.md b/notes/rtems-notes-6.1.md index 7197def..9b289a1 10064

[PATCH 2/2] bsps/aarch64: Fix off-by-one cache bug

The whole cache invalidation and flushing functions only ended up flusing the first N-1 levels of cache due to an off by one error. This resovles that issue and makes consistent the usage of levels as they relate to caching. --- bsps/aarch64/shared/cache/cache.c | 32 +++---

[PATCH 1/2] bsps/aarch64: Flush cache before disabling MMU

To ensure data consistency, the cache much be flushed before disabling the MMU. When the MMU is disabled, all accesses are treated as non-cachced and thus will bypass the cache. --- bsps/aarch64/include/bsp/aarch64-mmu.h | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/bs

[PATCH rtems-docs v2] eng: Add ObjectsItem details

This adds a section on adding ObjectsItems. --- eng/build-system.rst | 29 + 1 file changed, 29 insertions(+) diff --git a/eng/build-system.rst b/eng/build-system.rst index 6974aa8..9ccd582 100644 --- a/eng/build-system.rst +++ b/eng/build-system.rst @@ -489,3 +489,32

[PATCH rtems-central] spec/build-objects: Add details about duplicates

Add a comment warning against duplicate ObjectsItem inclusions and why that can cause problems. --- spec/spec/build-objects.yml | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/spec/spec/build-objects.yml b/spec/spec/build-objects.yml index 0453619d..695ab69f 100644 --- a/sp

[PATCH rtems-docs] eng: Add ObjectsItem details

This adds a section on adding ObjectsItems and some details to the definition regarding multiple inclusions. --- eng/build-system.rst | 28 eng/req/items.rst| 8 ++-- 2 files changed, 34 insertions(+), 2 deletions(-) diff --git a/eng/build-system.rst b/eng/bu

Re: [PATCH] spec/bsps: Deduplicate objxilinxsupport

On 2/6/2023 4:09 PM, Gedare Bloom wrote: ok. I'm not sure, maybe we need a note about this in https://docs.rtems.org/branches/master/eng/build-system.html I'll see if I can find an appropriate place for it to go in that document. Some parts of it are aspirational and apply to any build system

[PATCH] spec/bsps: Deduplicate objxilinxsupport

The objxilinxsupport build object was accidentally included twice in some of the ZynqMP BSPs by two different drivers that required it. This commit manually deduplicates the inclusions by moving that inclusion to the BSP. Duplication of object inclusions is considered a bug and can cause race condi

Re: [PATCH] wscript: Deduplicate installed files

: >> On 03.02.23 19:45, Kinsey Moore wrote: >>> This is my first stab at solving this duplicate install     problem. I could >>> manually solve the problem by deduplicating the object includes     and moving it >>> up to the BSP, but that is less int

Re: [PATCH] wscript: Deduplicate installed files

code together with any drivers that depend on it in a single obj*.yml. Kinsey On 2/3/2023 1:11 PM, Sebastian Huber wrote: On 03.02.23 19:45, Kinsey Moore wrote: This is my first stab at solving this duplicate install problem. I could manually solve the problem by deduplicating the object inc

Re: [PATCH] wscript: Deduplicate installed files

insey On 2/3/2023 12:36 PM, Kinsey Moore wrote: The addition of the NAND and NOR drivers both depending on the Xilinx support code independently has introduced the possibility of duplicate installed headers. This duplication results in multiple header install attempts which can conflict sinc

[PATCH] wscript: Deduplicate installed files

The addition of the NAND and NOR drivers both depending on the Xilinx support code independently has introduced the possibility of duplicate installed headers. This duplication results in multiple header install attempts which can conflict since the installs can run on multiple CPUs. This change to

[PATCH rtems-lwip 3/3] rtemslwip/xil_shims: Improve error messages

The error message produced in the case of MMU mapping failures was insufficient to track down the cause. This improves the out to assist the user in tracking down the issue. --- rtemslwip/zynqmp/xil_shims.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/rtemslwip/zynq

[PATCH rtems-lwip 1/3] rtemslwip: Remove sleep.h since RTEMS provides it

/sleep.h diff --git a/rtemslwip/xilinx/sleep.h b/rtemslwip/xilinx/sleep.h deleted file mode 100644 index 4a4fbdf..000 --- a/rtemslwip/xilinx/sleep.h +++ /dev/null @@ -1,34 +0,0 @@ -/* - * Copyright (C) 2022 On-Line Applications Research Corporation (OAR) - * Written by Kinsey Moore

[PATCH rtems-lwip 2/3] rtemslwip: Resolve conflicts involving xparameters

000 --- a/rtemslwip/zynqmp/xparameters.h +++ /dev/null @@ -1,113 +0,0 @@ -/* - * Copyright (C) 2022 On-Line Applications Research Corporation (OAR) - * Written by Kinsey Moore - * - * Redistribution and use in source and binary forms, with or without - * modification, are permitted provided that the fo

[PATCH 2/2] bsps/xil: Import full xil_exception.h

This imports the full xil_exception.h instead of an empty stub. This is required for some Xilinx drivers. The imported files adhere to the current VERSION file. --- .../xil/arm/ARMv8/32bit/xil_exception.h | 408 ++ .../xil/arm/ARMv8/64bit/xil_exception.h | 408 +

[PATCH 1/2] bsps/xil: Make sleep.h a stub

This makes xil/sleep.h a stub to prevent multiple differing definitions of sleep functions from toolchain and local headers. The non-standard sleep definitions were not in use and can be added later if needed. --- bsps/include/xil/sleep.h | 100 +-- 1 file chang

Re: [PATCH rtems-source-builder] Revert github tarball hash changes

some time. On Tue, Jan 31, 2023 at 8:58 AM Kinsey Moore wrote: GitHub has reverted the change that caused all these tarball hashes to change and so we follow suit. --- bare/config/devel/capstone-4.0.1-1.cfg| 2 +- bare/config/devel/gcc-12-newlib-head.cfg | 4 ++-- bare/c

[PATCH rtems-source-builder] Revert github tarball hash changes

GitHub has reverted the change that caused all these tarball hashes to change and so we follow suit. --- bare/config/devel/capstone-4.0.1-1.cfg| 2 +- bare/config/devel/gcc-12-newlib-head.cfg | 4 ++-- bare/config/devel/qemu-couverture-git-1.cfg | 2 +- bare/config/devel

Re: [PATCH rtems-source-builder] dtc: Add patch to build for ticket 4783

Sorry, I'll make sure to avoid this going forward. Kinsey On Mon, Jan 30, 2023 at 5:41 PM Chris Johns wrote: > On 31/1/2023 10:23 am, Kinsey Moore wrote: > > On 1/30/2023 5:13 PM, Chris Johns wrote: > >> Can the subject please be: > >> > >>

Re: [PATCH rtems-source-builder] dtc: Add patch to build for ticket 4783

On 1/30/2023 5:13 PM, Chris Johns wrote: Can the subject please be: dtc: Add patch to build for cygwin builds ? Unfortunately, Joel pushed this and a tools hash bump along with the other two patches, so that would require rewriting history. Kinsey _

[PATCH rtems-source-builder] devel/gnu-default-tools: Use correct include path

Include paths must use the full file name with extension. This was causing errors because it couldn't resolve the include. --- bare/config/devel/gnu-default-tools.bset | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bare/config/devel/gnu-default-tools.bset b/bare/config/devel/

[PATCH rtems-source-builder] Update hashes for github-sourced tarballs

Github has changed the way it generates on-the-fly tarball requests which has changed the hashes of the resulting tarballs. This adjusts the affected tarball hashes as a stop-gap until a more permanent solution can be devised. --- bare/config/devel/capstone-4.0.1-1.cfg| 2 +- bare/conf

[PATCH rtems-source-builder] dtc: Add patch to build for ticket 4783

This patch resolves a build error with dtc on cygwin until upstream adopts a fix. --- bare/config/devel/dtc-1.6.1-1.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bare/config/devel/dtc-1.6.1-1.cfg b/bare/config/devel/dtc-1.6.1-1.cfg index 54aed09..acf2cd8 100644 --- a/bare/config/deve

[PATCH 2/2] bsps/nand: Update Xilinx NAND driver

This resovles gcc warnings by updating to the latest Xilinx NAND controller driver. --- bsps/include/dev/nand/xnandpsu.h | 4 +++- bsps/include/dev/nand/xnandpsu_bbm.h | 2 +- bsps/include/dev/nand/xnandpsu_hw.h | 2 +- bsps/include/dev/nand/xnandpsu_onfi.h | 2 +- bsps/shared/dev/nand

[PATCH 1/2] cpukit/dev/can: Resolve warnings in 64bit builds

This resolves various gcc warnings in AArch64 LP64 builds of the CAN framework. --- cpukit/dev/can/can.c | 16 +--- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/cpukit/dev/can/can.c b/cpukit/dev/can/can.c index 2e6d5df65b..9f3fe0db98 100644 --- a/cpukit/dev/can/can.c +

Re: [PATCH v1 4/4] testsuites/libtest/dl11: Add DL test for TLS

On 1/19/2023 6:16 PM, Chris Johns wrote: On 20/1/2023 8:40 am, Kinsey Moore wrote: On 1/15/2023 6:07 PM, Chris Johns wrote: On 13/1/2023 12:51 pm, Kinsey Moore wrote: On Thu, Jan 12, 2023 at 5:11 PM Joel Sherrill mailto:j...@rtems.org>> wrote: Will this need to be added as an ex

[PATCH] spec: Install NandPsu headers correctly

These headers were mistakenly placed in the root of the installed BSP include directory. They should be in dev/nand. --- spec/build/bsps/objnandpsu.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/build/bsps/objnandpsu.yml b/spec/build/bsps/objnandpsu.yml index 0258417b

Re: [PATCH v1 4/4] testsuites/libtest/dl11: Add DL test for TLS

On 1/15/2023 6:07 PM, Chris Johns wrote: On 13/1/2023 12:51 pm, Kinsey Moore wrote: On Thu, Jan 12, 2023 at 5:11 PM Joel Sherrill mailto:j...@rtems.org>> wrote: Will this need to be added as an expected fail on other architectures? Just wondering how many bsp test configu

Re: [PATCH v2 1/2] bsps: Import Xilinx support code

I will update these. Thanks, Kinsey On Tue, Jan 17, 2023 at 2:45 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 22.12.22 19:56, Kinsey Moore wrote: > > +++ b/spec/build/bsps/objxilinxsupport.yml > > @@ -0,0 +1,45 @@ > > +SPDX-License-Identi

Re: [PATCH v1 4/4] testsuites/libtest/dl11: Add DL test for TLS

On Thu, Jan 12, 2023 at 5:11 PM Joel Sherrill wrote: > Will this need to be added as an expected fail on other architectures? > > Just wondering how many bsp test configuration files need touching > I suppose I could set it to enabled for only AArch64 for now. It would definitely fail on other a

Re: [PATCH v1 1/4] cpukit/libdl: Use correct mask for reloc type

On 1/12/2023 4:54 PM, Kinsey Moore wrote: The mask 0xff is used by ELF32 while ELF64 uses 0x. These are automatically selected based on the build type when using ELF_R_TYPE(). --- cpukit/libdl/rtl-rap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/libdl

[PATCH v1 4/4] testsuites/libtest/dl11: Add DL test for TLS

This adds a test verifying basic TLS functionality in loadable modules now that at least one architecture supports it. --- spec/build/testsuites/libtests/dl11.yml | 38 +++ spec/build/testsuites/libtests/grp.yml | 2 + testsuites/libtests/dl11/dl-load.c | 142

[PATCH v1 1/4] cpukit/libdl: Use correct mask for reloc type

The mask 0xff is used by ELF32 while ELF64 uses 0x. These are automatically selected based on the build type when using ELF_R_TYPE(). --- cpukit/libdl/rtl-rap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/libdl/rtl-rap.c b/cpukit/libdl/rtl-rap.c index 64ee294

[PATCH v1 2/4] cpukit/libdl: Print the missing AArch64 reloc type

This prints the relocation type that was found to be missing in addition to its address to aid in bug reports. --- cpukit/libdl/rtl-mdreloc-aarch64.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cpukit/libdl/rtl-mdreloc-aarch64.c b/cpukit/libdl/rtl-mdreloc-aarch64.c ind

[PATCH v1 3/4] cpukit/libdl: Add AArch64 TLS reloc support

This adds basic TLS relocation support for AArch64 to libdl. This lets loadable modules use TLS symbols hosted in the main binary. This does not allow loadable modules to host their own TLS symbols. --- cpukit/libdl/rtl-mdreloc-aarch64.c | 38 ++ 1 file changed, 38 inse

[PATCH rtems-tools] linkers/rtems-syms: Generate TLS symbols

When generating the symbol table for loadable modules, include TLS symbols so that the modules can reference them. --- linkers/rtems-syms.cpp | 5 + rtemstoolkit/rld-elf.cpp | 1 + rtemstoolkit/rld-symbols.cpp | 3 +++ 3 files changed, 9 insertions(+) diff --git a/linkers/rtems-syms

Re: [PATCH 1/3] build: Format build items

On 1/12/2023 10:38 AM, Sebastian Huber wrote: On 12.01.23 16:52, Kinsey Moore wrote: Annotation of expected test states with a description could get quite repetitive, but I suppose that's better than losing the information. I'm fine with this going in for now with a ticket to ad

[PATCH] bsps/xil: Use the LP64 header for ILP32

Xilinx's upstream ILP32 xil_cache.h header is out of date and broken. This provides a copy of the LP64 header in place of the ILP32 header since the LP64 header includes all the correct types to work with either data model. --- bsps/include/xil/arm/ARMv8/32bit/xil_cache.h | 35 ++--

[PATCH] bsps: Move ZynqMP-specific info into the BSP

The address of the nandpsu peripheral is specific to the ZynqMP SoC and not relevant to other devices that might have one or more instances of this peripheral. --- bsps/aarch64/xilinx-zynqmp/include/bsp.h | 2 + bsps/shared/dev/nand/xnandpsu_g.c | 47 --- bsps/shared/dev/na

Re: [PATCH 1/2] bsps: Import xilinx support code

On Thu, Dec 22, 2022 at 12:58 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 21/12/2022 21:54, Kinsey Moore wrote: > > +includes: > > +- bsps/include/xilinx_support/ > > +- bsps/include/xilinx_support/${XIL_SUPPORT_PATH}/ > > Is the xilinx_

Re: [PATCH] bsps/zynqmp: Fix and update device trees

On 12/5/2022 9:48 PM, Chris Johns wrote: I am still seeing issues with this change. The interface is `cgem0` and not `cgem3`. I have confirmed I have the same RTEMS hash in the build. Is there anything I need to set up to have the FDT be seem by libbsd? Seeing the first interface to come up as

[PATCH] bsps/zynqmp: Fix and update device trees

Add ref-clock-num identifiers to the device tree to ensure that interfaces use the correct clocks even when some are not used due to unconnected MII busses. This also adjusts the default ZynqMP PHY attachment to RGMII-ID which was the default before device trees were introduced. --- bsps/aarch64/x

[PATCH] spec/beagle: Add missing spi.h install

The beagle SPI functions are unusable by applications unless this file is installed with the BSP. This ensures that the file is installed properly. --- spec/build/bsps/arm/beagle/obj.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/spec/build/bsps/arm/beagle/obj.yml b/spec/build/bsps/arm/b

[PATCH] cpukit/rtems-fdt: Avoid use of malloc/errno

Use of malloc implies errno which adds TLS dependencies and prevents use of this FDT wrapper library in BSP initialization code. This change makes use of rtems_malloc and rtems_calloc which avoid TLS dependencies. --- cpukit/libmisc/rtems-fdt/rtems-fdt.c | 13 ++--- 1 file changed, 6 inser

Re: Use of rtems_fdt_* and sp01

On Fri, Nov 18, 2022 at 12:44 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 18/11/2022 06:32, Kinsey Moore wrote: > > On Thu, Nov 17, 2022 at 4:49 PM Chris Johns > <mailto:chr...@rtems.org>> wrote: > > > > On 18/11/2022 2:

Re: Use of rtems_fdt_* and sp01

On Thu, Nov 17, 2022 at 4:49 PM Chris Johns wrote: > On 18/11/2022 2:39 am, Kinsey Moore wrote: > > I recently added FDT support to the AArch64 ZynqMP BSPs to support an > optional > > management console and managing ethernet parameters for LibBSD. Use of > the > > rt

[PATCH] bsps/zynqmp: Use direct fdt_* calls

This changes the ZynqMP device tree parsing over to direct libfdt calls to avoid inclusion of malloc() in the base BSP which currently causes sp01 to fail due to unexpected use of TLS space. --- bsps/aarch64/xilinx-zynqmp/console/console.c | 32 ++-- 1 file changed, 10 insertions(+

Use of rtems_fdt_* and sp01

I recently added FDT support to the AArch64 ZynqMP BSPs to support an optional management console and managing ethernet parameters for LibBSD. Use of the rtems_fdt_* functions implies use of malloc which adds 4 bytes in the TLS space. The sp01 test uses rtems_task_construct and specifies a maxim

[PATCH] aarch64/mmu: Prevent block descriptors at level -1

In the original implementation, level -1 was unused and all levels could have block-like descriptors (level 2 block descriptors are called page descriptors). When support for level -1 page tables was added the constraint on level -1 block descriptors was not honored. This prevents block descriptors

[PATCH rtems-lwip] wscript: Allow deeper lwIP configuration

This adds a basic configuration mechanism in config.ini to control which BSPs are enabled and to alter lwIP's define/macro-based configuration directives. Existing builds using --rtems-bsps are unaffected if config.ini is not used. --- README | 14 ++ wscript | 60

Re: [PATCH rtems-lwip] rtemslwip: Add note to intentionally blank files

This should be covered by COPYING.rtemslwip. I would say it isn't worth putting it in the intentionally empty files. On Thu, Nov 10, 2022 at 2:22 PM Vijay Kumar Banerjee wrote: > Looks good to me. > > Do we need copyright statements for these files? > > On Wed, Nov 9, 20

[PATCH rtems-lwip] zynqmp: Add support for the CFC-400X BSP

wip/zynqmp_cfc400x/lwipbspopts.h new file mode 100644 index 000..27eb6a9 --- /dev/null +++ b/rtemslwip/zynqmp_cfc400x/lwipbspopts.h @@ -0,0 +1,33 @@ +/* + * Copyright (C) 2022 On-Line Applications Research Corporation (OAR) + * Written by Kinsey Moore + * + * Redistribution and use in sourc

Re: [PATCH v2] zynqmp: Add support for the CFC-400X

inx- > > zynqmp/bspcfc400xlp64.yml > > create mode 100644 spec/build/bsps/aarch64/xilinx- > > zynqmp/objfdtcfc400x.yml > > create mode 100644 spec/build/bsps/aarch64/xilinx- > > zynqmp/objfdtzynqmp.yml > > > > diff --git a/bsps/aarch64/xilinx

Re: [PATCH v2] spec/pkgconfig: Allow builds to override headers

workaround ready to go in once this is ok'd. This issue was just hit again on rtems-lwip. Kinsey On Tue, Oct 25, 2022 at 2:03 PM Kinsey Moore wrote: > This allows any builds targeting an installed RTEMS BSP to override > headers in the installed BSP reliably, including headers pr

[PATCH rtems-lwip] rtemslwip: Add note to intentionally blank files

--- rtemslwip/bsd_compat_include/arpa/nameser.h | 1 + rtemslwip/bsd_compat_include/machine/rtems-bsd-kernel-space.h | 1 + rtemslwip/bsd_compat_include/machine/rtems-bsd-user-space.h | 1 + rtemslwip/bsd_compat_include/net/if_var.h | 1 + rtemslwip/bsd_comp

[PATCH rtems-lwip v2] lwip.py: Move bsp-specific information out

This moves all BSP-specific information out of lwip.py and into JSON descriptions of the files required to compile the drivers for each BSP. Note that file-import.json is kept separate because it is used to manage updating from upstream. --- COPYING.defs | 23 +++

[PATCH rtems-lwip] lwip.py: Move bsp-specific information out

This moves all BSP-specific information out of lwip.py and into JSON descriptions of the files required to compile the drivers for each BSP. Note that file-import.json is kept separate because it is used to manage updating from upstream. --- COPYING.defs | 23 +++

[PATCH] cpukit/fdt: Fix typos and clarify params

--- cpukit/include/rtems/rtems-fdt.h | 24 +++- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/cpukit/include/rtems/rtems-fdt.h b/cpukit/include/rtems/rtems-fdt.h index 3919593582..18e04352aa 100644 --- a/cpukit/include/rtems/rtems-fdt.h +++ b/cpukit/include/rte

[PATCH rtems-libbsd v2 3/3] freebsd/cgem: Add SGMII support

This adds support to the CGEM driver for selection of SGMII PHY interfaces specified via device tree parameters. --- freebsd/sys/dev/cadence/if_cgem.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/freebsd/sys/dev/cadence/if_cgem.c b/freebsd/sys/dev/cadence/if_cgem.c index 047d91

[PATCH rtems-libbsd v2 2/3] freebsd/cgem: Add device tree support

This reintroduces device tree support to the CGEM driver while preserving the ability to statically define CGEM interfaces. --- freebsd/sys/dev/cadence/if_cgem.c | 42 +-- 1 file changed, 29 insertions(+), 13 deletions(-) diff --git a/freebsd/sys/dev/cadence/if_cgem.c

[PATCH rtems-libbsd v2 0/3] CFC400X support

In this revised patch set, SGMII support has been reworked to use device trees while preserving existing static instantiation used by Zynq and Versal BSPs. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[PATCH rtems-libbsd v2 1/3] nexus/zynqmp: Use device trees for CGEM

This moves the ZynqMP BSPs over to using device trees for CGEM instantiation now that all BSP variants provide appropriate device trees. --- rtemsbsd/include/bsp/nexus-devices.h | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/rtemsbsd/include/bsp/nexus-devices.h b

[PATCH v2] zynqmp: Add support for the CFC-400X

Research Corporation (OAR) * Written by Kinsey Moore * * Redistribution and use in source and binary forms, with or without @@ -36,13 +36,165 @@ #include #include +#include +#include #include +#include +#include #include + #include #include +#include + +uint32_t

[PATCH v2 0/1] Changes from v1

The management interface is now dynamically detected via the device tree. The device tree also contains information pertinent to LibBSD's ethernet configuration for all ZynqMP BSPs. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/li

Re: [PATCH rtems-docs] eng: show how to set local default subject-prefix

Looks good to me! I use this on all of the repos I send mail from. Kinsey On Thu, Nov 3, 2022 at 11:33 AM Gedare Bloom wrote: > --- > eng/vc-users.rst | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/eng/vc-users.rst b/eng/vc-users.rst > index 64c2624..680c004 100644 > --- a/eng/

Re: [PATCH rtems-libbsd] freebsd/cgem: Use SGMII when necessary

On Tue, Nov 1, 2022 at 9:22 PM Chris Johns wrote: > > > On 2/11/2022 1:18 pm, Kinsey Moore wrote: > > On Tue, Nov 1, 2022 at 5:49 PM Chris Johns > <mailto:chr...@rtems.org>> wrote: > > > > On 2/11/2022 8:56 am, Kinsey Moore wrote: > >

Re: [PATCH rtems-libbsd] freebsd/cgem: Use SGMII when necessary

On Tue, Nov 1, 2022 at 5:49 PM Chris Johns wrote: > On 2/11/2022 8:56 am, Kinsey Moore wrote: > > On Tue, Nov 1, 2022 at 4:14 PM Chris Johns > <mailto:chr...@rtems.org>> wrote: > > On 2/11/2022 5:51 am, Kinsey Moore wrote: > > > Certain hardware

Re: [PATCH] zynqmp: Add support for the CFC-400X

On Tue, Nov 1, 2022 at 4:23 PM Chris Johns wrote: > On 2/11/2022 8:15 am, Kinsey Moore wrote: > > On Tue, Nov 1, 2022 at 3:59 PM Chris Johns > <mailto:chr...@rtems.org>> wrote: > > > > On 2/11/2022 5:38 am, Kinsey Moore wrote:> +#ifdef >

Re: [PATCH rtems-libbsd] freebsd/cgem: Use SGMII when necessary

On Tue, Nov 1, 2022 at 4:14 PM Chris Johns wrote: > On 2/11/2022 5:51 am, Kinsey Moore wrote: > > Certain hardware configurations will always use SGMII instead of RGMII. > > Apply the appropriate flags for the relevant BSPs. > > --- > > freebsd/sys/dev/cadence/if_cg

Re: [PATCH] zynqmp: Add support for the CFC-400X

On Tue, Nov 1, 2022 at 3:59 PM Chris Johns wrote: > On 2/11/2022 5:38 am, Kinsey Moore wrote:> +#ifdef > BSP_XILINX_ZYNQMP_MGMT_UART_BASE > > +/** > > + * @brief Zynq UltraScale+ MPSoC specific set up of a management > console. > > + * > > + * The ZynqMP So

Re: Fwd: Identify 3rd party source in spec?

On Tue, Nov 1, 2022 at 11:25 AM wrote: > Hello Gedare, > > Am 31.10.22 um 20:01 schrieb Gedare Bloom: > > Resending without the first patch since it may trigger size filters. > > > > -- Forwarded message - > > From: Gedare Bloom > > Date: Mon, Oct 31, 2022 at 12:55 PM > > Subject

[PATCH rtems-lwip 2/2] lwip.py: Remove redundant system includes

These includes are already provided in the build by the pkgconfig (.pc) from the installed BSP. --- lwip.py | 6 -- 1 file changed, 6 deletions(-) diff --git a/lwip.py b/lwip.py index e6580eb..23ffccf 100644 --- a/lwip.py +++ b/lwip.py @@ -166,9 +166,6 @@ def build(bld): drv_obj_incl = [

[PATCH rtems-lwip 1/2] lwip.py: Remove redundant assignment

--- lwip.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/lwip.py b/lwip.py index c11ed1f..e6580eb 100644 --- a/lwip.py +++ b/lwip.py @@ -214,8 +214,6 @@ def build(bld): lib=['rtemscpu', 'rtemsbsp', 'rtemstest', 'lwip'], includes=' '.join(test_app_incl))

[PATCH rtems-docs] user/zynqmp: Add information about CFC-400X

Add a list of known working hardware and commentary about bitstream loading for specific hardware. --- user/bsps/aarch64/xilinx-zynqmp.rst | 48 +++-- 1 file changed, 38 insertions(+), 10 deletions(-) diff --git a/user/bsps/aarch64/xilinx-zynqmp.rst b/user/bsps/aarch64/xi

[PATCH rtems-libbsd] freebsd/cgem: Use SGMII when necessary

Certain hardware configurations will always use SGMII instead of RGMII. Apply the appropriate flags for the relevant BSPs. --- freebsd/sys/dev/cadence/if_cgem.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/freebsd/sys/dev/cadence/if_cgem.c b/freebsd/sys/dev/cadence/if_cgem.c in

[PATCH] zynqmp: Add support for the CFC-400X

This adds a BSP variant for the ZynqMP BSP family to support the Innoflight CFC-400X platform. --- bsps/aarch64/xilinx-zynqmp/console/console.c | 72 +++ bsps/aarch64/xilinx-zynqmp/include/bsp.h | 11 +++ .../aarch64/xilinx-zynqmp/start/bspstartmmu.c | 7 ++ .../aarch64/xili

<    1   2   3   4   5   6   7   8   9   10   >