Re: [PATCH 01/34] validation: Test sparc/leon3 BSP family

[ resending ... ] On 1/6/2023 3:28 am, Sebastian Huber wrote: > On 31.05.23 19:25, Joel Sherrill wrote: >> On Wed, May 31, 2023 at 12:18 PM Sebastian Huber >> > > wrote: >> >>     On 31.05.23 19:14, Joel Sherrill wrote: >> > This patch has a couple

Re: [dspace-tech] Oddities around the Creative Commons license configuration in item-submission.xml

bserve email-free evenings and weekends. *** > > > On Fri, May 12, 2023 at 2:18 PM Erica Johns > wrote: > >> hi Paige, >> >> We've noticed the same thing at Cornell. I made a ticket >> <https://github.com/DSpace/DSpace/issues/8543> for this with dspac

[dspace-tech] metadata fields from dc metadata registry cannot be added to items

hi all- (posted in slack too, apologies for duplication. hoping to get some eyes on this!) in the middle of our migration to 7 (launch on friday [image: :crossed_fingers:]) and something surfaced that we missed before: we do a lot of metadata editing of items in the UI after upload, and currently

Re: [PATCHv2 rtems_waf] Allow vendor field in toolchain target triplet

On 27/5/2023 2:03 am, martinerikwerner@gmail.com wrote: On Fri, 2023-05-26 at 08:33 +1000, Chris Johns wrote: On 25/5/2023 6:53 pm, martinerikwerner@gmail.com wrote: While poking around some more, it seems like there's more places in this file where assumptions of no vendor

Re: [PATCH] score: Unify

On 26/5/2023 1:38 pm, Andy wrote: > > If you need my reply, I am ok to switch to BSD-2-Clause license.  > Thank you and thank you for letting us know. :) Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] score: Unify

On 25/5/2023 3:54 pm, Sebastian Huber wrote: > On 25.05.23 03:40, Kinsey Moore wrote:> Is there any reason this isn't just > being moved to a shared directory if >> they're all being made identical? > > Initially, they were all identical. We already have a shared implementation > >

Re: [PATCHv2 rtems_waf] Allow vendor field in toolchain target triplet

On 25/5/2023 6:53 pm, martinerikwerner@gmail.com wrote: > While poking around some more, it seems like there's more places in > this file where assumptions of no vendor in the triplet might come into > play (but did not affect my use of it), if I'm reading it correctly?: > > 227

Re: [PATCH] score: Unify

On 25/5/2023 3:51 pm, Sebastian Huber wrote: > > > On 25.05.23 02:11, Chris Johns wrote: >> On 24/5/2023 11:00 pm, Sebastian Huber wrote: >>> All CPU ports use the same file. >>> --- >>>   .../aarch64/include/rtems/score/cpuatomic.h   |  8 ++--- >>

Re: [PATCH 0/5] Minor ARM BSP Improvements

These look good. Thanks Chris On 24/5/2023 11:05 pm, Sebastian Huber wrote: > Sebastian Huber (5): > bsps/arm: Use interrupt entry for > bsps/arm: Use interrupt entry for clock driver > bsps/arm: Use interrupt entry for IPI > arm/xilinx-zynq: Do not provide legacy API >

Re: [PATCH] score: Unify

On 24/5/2023 11:00 pm, Sebastian Huber wrote: > All CPU ports use the same file. > --- > .../aarch64/include/rtems/score/cpuatomic.h | 8 ++--- > .../cpu/arm/include/rtems/score/cpuatomic.h | 11 +- > .../cpu/bfin/include/rtems/score/cpuatomic.h | 36 --- >

Re: Discussion: How to handle HALs, SDKs and libraries

On 24/5/2023 5:07 pm, Christian MAUDERER wrote: > Hello Chris, > > On 2023-05-24 03:44, Chris Johns wrote: >> Hi Christian, >> >> Thanks for raising this topic. It is a tough one. >> >> On 24/5/2023 12:11 am, Kinsey Moore wrote: >>> On

Re: [PATCH rtems-libbsd] ipsec-tools: Fix copying fd_set prior to select

On 24/5/2023 11:42 pm, Christian MAUDERER wrote: > On 2023-05-24 02:33, Chris Johns wrote: >> On 24/5/2023 9:13 am, Chris Johns wrote: >>> On 23/5/2023 5:30 pm, Christian MAUDERER wrote: >>>> Hello Chris, >>>> >>>> On 2023-05-23 08:53, Ch

Re: [PATCHv2 rtems_waf] Allow vendor field in toolchain target triplet

Looks good and thanks. I have pushed this. If you would like to submit module update patches for the various repos using rtems_waf please feel free to do so. Chris On 25/5/2023 4:13 am, Martin Erik Werner wrote: > Rework the splitting of arch and bsp to rely on the last field in the > arch

Re: Discussion: How to handle HALs, SDKs and libraries

Hi Christian, Thanks for raising this topic. It is a tough one. On 24/5/2023 12:11 am, Kinsey Moore wrote: > On Tue, May 23, 2023 at 2:26 AM Christian MAUDERER > > wrote: > > Hello, > > I recently updated the HAL in the i.MXRT BSP. I used

Re: [PATCH rtems-libbsd] ipsec-tools: Fix copying fd_set prior to select

On 24/5/2023 9:13 am, Chris Johns wrote: > On 23/5/2023 5:30 pm, Christian MAUDERER wrote: >> Hello Chris, >> >> On 2023-05-23 08:53, Chris Johns wrote: >>> On 23/5/2023 4:25 pm, Christian MAUDERER wrote: >>>> Hello Chris, >>>> >>>&g

Re: [PATCH rtems-libbsd] ipsec-tools: Fix copying fd_set prior to select

On 23/5/2023 5:30 pm, Christian MAUDERER wrote: > Hello Chris, > > On 2023-05-23 08:53, Chris Johns wrote: >> On 23/5/2023 4:25 pm, Christian MAUDERER wrote: >>> Hello Chris, >>> >>> On 2023-05-23 03:36, Chris Johns wrote: >>>> Hi, >>>

Re: [PATCH rtems-libbsd] ipsec-tools: Fix copying fd_set prior to select

On 23/5/2023 4:25 pm, Christian MAUDERER wrote: > Hello Chris, > > On 2023-05-23 03:36, Chris Johns wrote: >> Hi, >> >> I have been resolving this by adding: >> >> #define preset_mask *preset_mask_prealloc >> #define active_mask *active_mask

Re: [PATCH rtems-libbsd] ipsec-tools: Fix copying fd_set prior to select

Hi, I have been resolving this by adding: #define preset_mask *preset_mask_prealloc #define active_mask *active_mask_prealloc as the assignment logic works as is. It does not catch FD_ZERO which is a shame but is helps avoid us adding a special case. Chris On 22/5/2023 5:36 pm, Christian

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 22/5/2023 6:29 pm, Sebastian Huber wrote: > On 22.05.23 01:48, Chris Johns wrote: >>> The support for the CSafeLoader is just about 60 lines of additional code. >>> It would be a nice improvement for systems supporting this feature. I don't >>> have >

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 19/5/2023 4:46 pm, Sebastian Huber wrote: > On 15.05.23 01:44, Chris Johns wrote: >> On 5/5/2023 8:16 pm, Sebastian Huber wrote: >>> On 05.05.23 01:38, Chris Johns wrote: >>>>> When I install it >>>>> through pip, I get the CSafeLoader on my m

Re: [PATCH rtems-source-builder] rtems-gcc-*-newlib-head.cfg: Update to include true long double math

OK Thanks Chris On 20/5/2023 12:54 am, Joel Sherrill wrote: > Previously newlib only had long double math functions when the > sizeof(double) was equal to sizeof(long double). Newlib now includes > support for true long double on x86, x86_64, and aarch64. > > These files were not included in

Re: [PATCH] libdl: Add support for LDST128_ABS_LO12_NC

OK Chris On 20/5/2023 5:16 am, Kinsey Moore wrote: > --- > cpukit/libdl/rtl-mdreloc-aarch64.c | 4 > 1 file changed, 4 insertions(+) > > diff --git a/cpukit/libdl/rtl-mdreloc-aarch64.c > b/cpukit/libdl/rtl-mdreloc-aarch64.c > index 25057ce9d7..46f87e9178 100644 > ---

Re: [PATCH 0/2] bsps/microblaze: GPIO improvements

OK. This is a great change to see and a good direction for the Microblaze to take. Thanks Chris On 19/5/2023 1:46 pm, Alex White wrote: > Hi, > > This patch set removes the build system options for the GPIO driver and adds > device tree support. The build system options were removed because

Re: [PATCH rtems-source-builder] rtems-gcc-12-newlib-head.cfg: Update to include true long double math

OK. Well done on the long doubles work. Chris On 18/5/2023 7:13 am, Joel Sherrill wrote: > Previously newlib only had long double math functions when the > sizeof(double) was equal to sizeof(long double). Newlib now includes > support for true long double on x86, x86_64, and aarch64. > --- >

Re: [PATCH rtems 00/12] bsp/imxrt: Update SDK and prepare for new variant

On 15/5/2023 6:13 pm, o...@c-mauderer.de wrote: > Hello Chris, > > Am 15.05.23 um 05:18 schrieb Chris Johns: >> >> >> On 6/5/2023 2:02 am, Gedare Bloom wrote: >>> On Fri, May 5, 2023 at 9:02 AM wrote: >>>> >>>> Hello Gedare, >&

Re: [PATCH rtems 00/12] bsp/imxrt: Update SDK and prepare for new variant

On 6/5/2023 2:02 am, Gedare Bloom wrote: > On Fri, May 5, 2023 at 9:02 AM wrote: >> >> Hello Gedare, >> >> thanks for taking a look at the patch set. >> >> Am 05.05.23 um 15:56 schrieb Gedare Bloom: >>> On Thu, May 4, 2023 at 9:01 AM Christian Mauderer >>> wrote: Hello,

Re: [PATCH 00/12] Update documentation of specification items

No issues here. Chris On 6/5/2023 12:07 am, Gedare Bloom wrote: > these look ok. I'll leave the register one for Chris to comment. > > On Fri, May 5, 2023 at 2:46 AM Sebastian Huber > wrote: >> >> Sebastian Huber (12): >> eng: Rework performance meansurement items >> eng: Generalize

Re: [PATCH v3] eng: Add register block specification types

Hi, Sorry about the delay, I have been out sick for the last week or so. I am ok with this to be pushed. I have a minor correction below and a clean up if you want. On 5/5/2023 6:50 pm, Sebastian Huber wrote: > A register block may be used to specify the interface of devices which > contain

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 5/5/2023 8:16 pm, Sebastian Huber wrote: > On 05.05.23 01:38, Chris Johns wrote: >>> When I install it >>> through pip, I get the CSafeLoader on my machine. I don't have a libyaml >>> development package installed. >> This is what I was not understanding.

Re: [dspace-tech] Oddities around the Creative Commons license configuration in item-submission.xml

hi Paige, We've noticed the same thing at Cornell. I made a ticket for this with dspace and it was determined this is a bug on the CC side. I then made a github ticket with CC to fix. CC has marked the ticket high priority and awaiting triage.

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 4/5/2023 4:16 pm, Sebastian Huber wrote: > On 04.05.23 05:35, Chris Johns wrote: >> On 3/5/2023 7:40 pm, Sebastian Huber wrote: >>> On 03.05.23 05:30, Chris Johns wrote: >>>> On 28/4/2023 3:38 pm, Sebastian Huber wrote: >>>>> On 27.04.23 20:27, Ge

Re: [dspace-community] Copyright infringement on theses and dissertations

would have grounds to issue a DMCA takedown request. Whether the institution can do this on behalf of the author depends on the nature of the repository license.” Best, Erica Erica M. Johns Lead Librarian for the eCommons Institutional Repository Service Cornell University Library E: em

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 3/5/2023 7:40 pm, Sebastian Huber wrote: > On 03.05.23 05:30, Chris Johns wrote: >> On 28/4/2023 3:38 pm, Sebastian Huber wrote: >>> On 27.04.23 20:27, Gedare Bloom wrote: >>>> On Wed, Apr 26, 2023 at 11:46 PM Sebastian Huber >>>>   wrote:

Re: [RBW] Re: New Sim Works Taco Pedals: Looks appealing

much going out and not enough coming in, cash wise. JohnS On Tuesday, April 25, 2023 at 8:59:41 AM UTC-4 JohnS wrote: > Hello Eric, > > I saw them the other day and thought they would be good pedal for me. I > like the minimal platform, some engagement but not too much. Lookin

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 28/4/2023 3:38 pm, Sebastian Huber wrote: > On 27.04.23 20:27, Gedare Bloom wrote: >> On Wed, Apr 26, 2023 at 11:46 PM Sebastian Huber >>   wrote: >>> On 27.04.23 02:11, Chris Johns wrote: >>>> On 26/4/2023 6:04 pm, Sebastian Huber wrote: >>>

Re: [PATCH rtems-libbsd] Revert "waf: Move the tools/BSP include path to be last"

py > @@ -2,7 +2,7 @@ > """LibBSD build configuration to waf integration module. > """ > > -# Copyright (c) 2015, 2021 Chris Johns . All rights > reserved. > +# Copyright (c) 2015, 2020 Chris Johns . All rights > reserved. > # > #

Re: RSB repo commits need approval

On 29/4/2023 3:48 am, o...@c-mauderer.de wrote: > Hello Joel, > > Am 28.04.23 um 00:19 schrieb Joel Sherrill: >> >> >> On Wed, Apr 26, 2023 at 7:06 PM Chris Johns > <mailto:chr...@rtems.org>> wrote: >> >>     Hi, >> >>     Al

Re: Change build specification files from YAML to JSON?

On 26/4/2023 6:22 pm, Sebastian Huber wrote: > On 26.04.23 01:52, Chris Johns wrote: >> On 25/4/2023 5:35 pm, Sebastian Huber wrote: >>> Tooling makes sense if you have a high change rate. >> >> That is not the use case I am discussing and it is not a facto

Re: RSB repo commits need approval

On 28/4/2023 4:05 am, Gedare Bloom wrote: > On Thu, Apr 27, 2023 at 3:27 AM Karel Gardas wrote: >> On 4/27/23 08:13, Sebastian Huber wrote: >>> Why >>> don't we use a Git pull request workflow with CI pipelines in the RTEMS >>> Project? >> >> I don't know, but certainly github.com is not

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 28/4/2023 4:27 am, Gedare Bloom wrote: > On Wed, Apr 26, 2023 at 11:46 PM Sebastian Huber > wrote: >> >> On 27.04.23 02:11, Chris Johns wrote: >>> On 26/4/2023 6:04 pm, Sebastian Huber wrote: >>>> The CSafeLoader uses the C libyaml libary to considerably

Re: RSB repo commits need approval

On 27/4/2023 4:13 pm, Sebastian Huber wrote: > what is your (or the RTEMS Project in general) plan to maintain the tools and > ensure that we can use up to date versions of Newlib, GCC, Binutils, and GDB? > This involves building the latest versions, reviewing build issues, reporting > bugs,

Re: [PATCH 2/5] build: Use CSafeLoader if available

On 26/4/2023 6:04 pm, Sebastian Huber wrote: > The CSafeLoader uses the C libyaml libary to considerably speed up the > loading of YAML files. No from me. I do not agree with conditional states of operation in the build system that depend on packages a host has installed. If speed is an

RSB repo commits need approval

Hi, All RSB repo commits need to be posted for review and independent approval given before being pushed to the top level repo. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: Change build specification files from YAML to JSON?

On 25/4/2023 5:35 pm, Sebastian Huber wrote: > Tooling makes sense if you have a high change rate. That is not the use case I am discussing and it is not a factor. > This is not the case for the RTEMS build specification items. I am not saying it is. > For which use case do we need tooling

Re: Change build specification files from YAML to JSON?

On 26/4/2023 4:01 am, Sebastian Huber wrote: > On 25.04.23 13:02, Karel Gardas wrote: >> On 4/25/23 12:32, Sebastian Huber wrote: >>> On 25.04.23 12:10, Karel Gardas wrote: On 4/25/23 11:03, Sebastian Huber wrote: > > > On 25.04.23 11:00, Karel Gardas wrote: >> On 4/25/23

Re: [RBW] Re: New Sim Works Taco Pedals: Looks appealing

Hello Eric, I saw them the other day and thought they would be good pedal for me. I like the minimal platform, some engagement but not too much. Looking forward to ordering a pair when they're available in late May. JohnS On Monday, April 24, 2023 at 6:49:23 PM UTC-4 Jason Fuller wrote: >

Re: Change build specification files from YAML to JSON?

On 25/4/2023 12:20 am, Sebastian Huber wrote: > On 24.04.23 16:17, Kinsey Moore wrote: >> I think we've been moving away from in-file comments in the YAML and toward >> actual labels in the data, anyway. If it's important information, it should >> be >> kept properly. > > Yes, there should be no

Re: [PATCH] score: Avoid cyclic header file dependencies

Looks good and thanks for sorting this out. Chris On 24/4/2023 11:00 pm, Sebastian Huber wrote: > There was a cyclic dependency: For RTEMS_STATIC_ANALYSIS we needed > basedefs.h in assert.h. For RTEMS_UNREACHABLE() we needed _Assert() from > assert.h in basedefs.h. > > Fix this by introducing

Re: Qemu and missing dynamic libraries

On 25/4/2023 7:05 am, Joel Sherrill wrote: > > > On Mon, Apr 24, 2023 at 3:11 PM Karel Gardas wrote: > > On 4/24/23 21:33, Joel Sherrill wrote: > > > > > > On Mon, Apr 24, 2023, 2:11 PM Karel Gardas > wrote: > > > > > >     What have you done to this poor FBSD?

Re: [PATCH] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

On 24/4/2023 7:14 pm, Sebastian Huber wrote: > Looks good, thanks. Thanks for the review, pushed. Sorry about forgetting to post the fix. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2 2/2] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

On 24/4/2023 6:42 pm, Sebastian Huber wrote: > On 12.04.23 03:56, chr...@rtems.org wrote: >> From: Chris Johns >> >> - This change avoids the GCC extension of blocks in expressions that >>    ISO forbids and is warned about with the pedantic warnings option. >

Re: [PATCH rtems-examples 1/6] c11/wscript: C11 concurrency does not require POSIX enabled

Looks good. Chris On 24/4/2023 6:44 am, Joel Sherrill wrote: > --- > c11/wscript | 9 - > 1 file changed, 4 insertions(+), 5 deletions(-) > > diff --git a/c11/wscript b/c11/wscript > index 151c591..eeb60a9 100644 > --- a/c11/wscript > +++ b/c11/wscript > @@ -6,8 +6,7 @@ > import

Re: [PATCH 4/4] sb/pkg-config: Add --cflags-only-I and --cflags-only-other option

On 23/4/2023 6:12 am, Joel Sherrill wrote: > Do these  options need some help/explanation? https://manpages.ubuntu.com/manpages/bionic/man1/pkg-config.1.html Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: MIPS build requires native expat lib (Was: [rtems-source-builder PATCH] rtems: Add back gsed that was remove by mistake)

On 21/4/2023 2:53 am, Frank Kühndel wrote: > Hi Chris, > > I compared the successful Debian-11 MIPS build with the failing AlmaLinux MIPS > build. > > The Debian 11 container has a native "expat.h" and "libexpat.a" installed (and > the source-builder uses >

Re: Build Linux: FAILED 6/rtems-v850 on x86_64-linux-gnu (v850-rtems6-gcc-28fc129-newlib-836d04d-x86_64-linux-gnu-1)

On 20/4/2023 4:05 pm, Sebastian Huber wrote: > On 19.04.23 02:07, Chris Johns wrote: >> On 18/4/2023 11:29 pm,sebastian.hu...@embedded-brains.de  wrote: >>> RTEMS Source Builder - Set Builder, 6 (7841a1e9056f) >>> config: tools/rtems-gcc-10-newlib-head.cfg >>&

Re: [rtems-source-builder PATCH] rtems: Add back gsed that was remove by mistake

On 19/4/2023 11:26 pm, Frank Kühndel wrote: > Hello Chris, > > thanks for the introduction to package build. On AlmaLinux the file > rtems-source-builder/rtems/build/mipstx39-rtems6-gdb-13.1-x86_64-linux-gnu-1/build/gdb/config.log > (attached) contains this error: > > > configure:21340:

Re: [PATCH] bsps/microblaze: Add device tree support to GPIO driver

On 20/4/2023 12:57 am, Alex White wrote: > This removes the ability to statically configure a second GPIO device. > Instead, any number of GPIO devices can be configured using the device > tree. If a device tree is not used, a single GPIO device can still be > configured statically. > --- >

Re: [PATCH v2 1/3] cpukit/flash: Add API for Flash devices

On 20/4/2023 7:42 am, Gedare Bloom wrote: > On Mon, Apr 17, 2023 at 9:55 PM Chris Johns wrote: >> >> On 18/4/2023 1:48 pm, Gedare Bloom wrote: >>> On Sun, Apr 16, 2023 at 6:48 PM Aaron Nyholm >>> wrote: >>>> As for the RTEMS_FLASHDEV_

[RBW] Re: What do I replace coroplast with in Sackville

I'm with Ian, but instead of plywood, I use 1/8" fiberboard for bike bag stiffeners. Cut to size and coat with polyurethane to water proof it. Holds up great, downside is it's heavier than the plastic. JohnS On Tuesday, April 18, 2023 at 4:28:43 PM UTC-4 lconley wrote: > You could tr

Re: Build Linux: FAILED 6/rtems-v850 on x86_64-linux-gnu (v850-rtems6-gcc-28fc129-newlib-836d04d-x86_64-linux-gnu-1)

On 18/4/2023 11:29 pm, sebastian.hu...@embedded-brains.de wrote: > RTEMS Source Builder - Set Builder, 6 (7841a1e9056f) > config: tools/rtems-gcc-10-newlib-head.cfg > package: v850-rtems6-gcc-28fc129-newlib-836d04d-x86_64-linux-gnu-1 > warning: checksum error: gnu-mirror-gcc-28fc129.tar.gz This

Re: [rtems-source-builder PATCH] rtems: Add back gsed that was remove by mistake

/src/rtems-source-builder/rtems/build/mipstx39-rtems6-gdb-13.1-x86_64-linux-gnu-1/build' >>> shell cmd failed: /bin/sh -ex >>> /home/minna/src/rtems-source-builder/rtems/build/mipstx39-rtems6-gdb-13.1-x86_64-linux-gnu-1/do-build >>> error: building mipstx39-r

Re: [PATCH v2 1/3] cpukit/flash: Add API for Flash devices

On 18/4/2023 1:48 pm, Gedare Bloom wrote: > On Sun, Apr 16, 2023 at 6:48 PM Aaron Nyholm > wrote: >> As for the RTEMS_FLASHDEV_MAX_REGIONS being set at 32 I chose the value as >> it seamed a good balance between memory usage and function. I wanted to >> avoid using malloc as your previous

Re: [PATCH v2] bsps/aarch64: Enable MMU during remaps

Looks good. OK to push. Chris On 18/4/2023 11:41 am, Kinsey Moore wrote: > The MMU must be enabled during mapping changes and TLB invalidations. > When this is not the case, TLB updates do not occur correctly in all > cases. This is especially apparent when changing a block entry to a > table

Re: [RBW] Lovely Blue Riv Custom

The color matched, with strips Silca Impero Ultimate frame pump looks great too! JohnS On Sunday, April 16, 2023 at 10:53:43 AM UTC-4 E. Ricky Creek wrote: > It has one of those new OEM Brooks B-68s. Jealous  > > On Sunday, April 16, 2023 at 5:36:24 AM UTC-5 Eric Da

Re: rtems.org websites https not working?

On 17/4/2023 6:16 am, Alan Cudmore wrote: > Hi, > When I try to go to docs.rtems.org , www.rtems.org > , or git.rtems.org , I get an > error > from my browser: ERR:CERT_DATE_INVALID. > Just wanted to see if anyone else noticed

Re: [rtems-net-legacy PATCH] bsd: Add iface calls to help user manage the iface state

On 15/4/2023 12:14 am, Gedare Bloom wrote: > two nits below Thanks for the review. I appreciate you doing it. I will clean these up and push the result. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-net-legacy commit] waf: Generate a version header called rtems-net-legacy.h

On 15/4/2023 12:06 am, Gedare Bloom wrote: > On Thu, Apr 13, 2023 at 11:59 PM Chris Johns wrote: >> +#ifndef _RTEMS_NET_LGEACY_H_ > typo in the header guard Nice catch. Thanks. I will fix this. Chris ___ devel mailing list devel@rt

Re: [rtems-net-legacy PATCH] waf: Generate a version header called rtems-net-legacy.h

On 14/4/2023 3:40 pm, Vijay Kumar Banerjee wrote: > > The patch looks great. Thanks. Thanks for quick review. I will push it. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

On 13/4/2023 11:48 pm, Will wrote: > This change is fine, but it also needs the packageconfig change to match. The > thread from October has the full patch (title was "[PATCH v2] spec/pkgconfig: > Allow builds to override headers"). This also needs a change to libbsd to > account for this

Re: [PATCH] spec/bsp/makecustom: Make BSP include path a system include path

On 14/4/2023 1:32 am, Joel Sherrill wrote: > On Thu, Apr 13, 2023 at 8:49 AM Will > wrote: > > This change is fine, but it also needs the packageconfig change to match. > The thread from October has the full patch (title was "[PATCH v2] > spec/pkgconfig:

Re: [PATCH 00/18] Port PTPd to rtems-libbsd

On 12/4/2023 11:54 pm, Gabriel Moyano wrote: > These commits are for porting PTPd to rtems-libbsd and are based on the > master branch. > > This work is a joint effort with Chris Johns, which we started some time ago. > Originally, we wanted to port some of the commits t

Re: [PATCH 2/2] bsps/powerpc: Fix warnings with PPC_SPECIAL_PURPOSE_REGISTER

blocks in expressions that ISO forbids and is warned about with the pedantic warnings option. ? Chris > > On Tue, Apr 11, 2023, 12:00 AM mailto:chr...@rtems.org>> > wrote: > > From: Chris Johns mailto:chr...@rtems.org>> > > --- &g

Re: [PATCH 1/2] bsps/motorola_powerpc: Change defines from BSP names to avoid clash

On 11/4/2023 10:44 pm, Joel Sherrill wrote: > On Tue, Apr 11, 2023, 12:00 AM mailto:chr...@rtems.org>> > wrote: > > From: Chris Johns mailto:chr...@rtems.org>> > > - Change mvme2100 to mot_pcc_mvme2100 to avoid clashing with the >   RTEMS_BSP v

[RBW] Re: Sharing your winter ride photos northern hemisphere Spring 2023

Ted, nice picture of your bike and the lighthouse. Which one is that? I'll be on the upper Cape in the beginning of July. Always enjoy the riding there. JohnS On Tuesday, April 11, 2023 at 11:30:14 AM UTC-4 Ted Durant wrote: > I realize now that I left the word "winter" in the

Re: Motorola PowerPC asm warning

On 9/4/2023 1:26 am, Joel Sherrill wrote: > > > On Fri, Apr 7, 2023, 6:55 PM Joel Sherrill <mailto:j...@rtems.org>> wrote: > > > > On Fri, Apr 7, 2023, 5:54 PM Chris Johns <mailto:chr...@rtems.org>> wrote: > > Hi > >

Re: [PATCH v3 1/3] bsps/microblaze: Allow copying FDT from U-Boot

On 10/4/2023 1:47 pm, Alex White wrote: > .../microblaze_invalidate_dcache_range.S | 104 ++ Why not provide the RTEMS cache API and use that? Chris ___ devel mailing list devel@rtems.org

Motorola PowerPC asm warning

Hi Building the motorola_powerpc BSPs I noticed this warning: ../../../bsps/powerpc/shared/exceptions/ppc_exc.S: Assembler messages: ../../../bsps/powerpc/shared/exceptions/ppc_exc.S:132: Warning: invalid register expression ../../../bsps/powerpc/shared/exceptions/ppc_exc.S:135: Warning: invalid

Re: [PATCH] bsps/motorola_powerpc: Add spec support for BSP defines

with the macros. Chris On 6/4/2023 2:27 pm, chr...@rtems.org wrote: > From: Chris Johns > > - These are need by the net legacy stack > --- > .../bsps/powerpc/motorola_powerpc/grp.yml | 4 > .../powerpc/motorola_powerpc/optmvme2307.yml | 18 ++ > .../pow

Re: powerpc/motorola_powerpc: Add MVME2700 BSP

On 7/4/2023 1:28 am, Joel Sherrill wrote: > Random (and late) question. For this generic BSP, the bsp.h has this: > > LIBBSP_POWERPC_MOTOROLA_POWERPC_BSP_H > > as the bsp guard. libbsd uses that to configure the nexus device and  > peripherals. Are there board model differences which need to be

Re: Add Flash Device API

Hi Aaron, Thanks for this. Is this v2 of patches? Chris On 6/4/2023 4:52 pm, aaron.nyh...@unfoldedeffective.com wrote: > Attached is the updated flashdev API. I've focused on the feedback > previously provided. I've added called the missing calls to bring > this API inline with that of the

Re: [rtems-net-legacy PATCH 2/2] testsuite: Add telenet02 test

The commit missed the doco update. I will send a v2. Chris On 6/4/2023 3:08 pm, chr...@rtems.org wrote: > From: Chris Johns > > --- > testsuites/telnetd02/init.c| 116 + > testsuites/telnetd02/telnetd02.doc | 11 +++ > testsuites/telne

Re: [PATCH 7/8] rtems/mipsstx39: Update to GDB 13.1 and stage build GMP

On 6/4/2023 3:27 am, Joel Sherrill wrote: > This is separate because mipstx39 is not a full toolchain but we have to built > this target to get the jmr3904 simulator. It should normally be in sync with > the > other gdb configurations. > > This looks ok. Thanks. The ability for the RSB to stage

Re: [PATCH 1/8] dtc: Disable warnings

On 6 Apr 2023, at 3:27 am, Joel Sherrill wrote:Looks good.Does this stop build failures for warnings?YesChrisOn Tue, Apr 4, 2023 at 8:31 PM <chr...@rtems.org> wrote:From: Chris Johns <ch...@contemporary.net.au> Updates #4892 ---  source-builder/config/dtc-1-1.cfg | 4 ++--  1 fil

Re: arm bsps: changing the float-abi to softfp

On 5/4/2023 4:11 am, Sebastian Huber wrote: > If you really need such a multilib, then you can patch > gcc/config/arm/t-rtems. I > don't know if you can add custom patches to the RTEMS Source Builder. There is a means if someone wants to update gcc-common-1.cfg to allow user macro maps. 1. User

Re: [PATCH 2/2] cpukit/libdl: Resolve size mismatch warnings

OK to the libdl patch Chris On 5/4/2023 7:33 am, Kinsey Moore wrote: > Resolve warnings about mismatched pointer and integer sizes in AArch64 > libdl when building with the ILP32 ABI. > --- > cpukit/libdl/rtl-elf.c | 4 ++-- > cpukit/libdl/rtl-mdreloc-aarch64.c | 31

Re: [PATCH rtems-lwip] rtemslwip/xil_shims: Perform flush with invalidate

On 4/4/2023 10:23 pm, Kinsey Moore wrote: > On Mon, Apr 3, 2023 at 8:00 PM Chris Johns <mailto:chr...@rtems.org>> wrote: > > On 31/3/2023 8:13 am, Kinsey Moore wrote: > > Xilinx wrote their A53 HAL with the assumption that the CPU did not > > supp

Re: [PATCH rtems-lwip] rtemslwip/xil_shims: Perform flush with invalidate

On 31/3/2023 8:13 am, Kinsey Moore wrote: > Xilinx wrote their A53 HAL with the assumption that the CPU did not > support cache invalidation without a flush, so the flush and > invalidation functions were combined and all range invalidations are > promoted to flush/invalidate. The implementation

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

On 4/4/2023 12:55 am, Alan Cudmore wrote: > Hi Chris, > Sorry I should have read that and formatted my changes correctly. I submitted > a > v5 patch, but as I sent it, I realized that there are a couple of places where > the RTEMS version macro can be embedded rather than hard-coding "6". I

Re: [PATCH v2] docs/user: add docs for riscv/kendrytek210 BSP variant

Hi Alan, We have a standard for the documentation source: https://git.rtems.org/rtems-docs/tree/README.txt#n469 Please note the line length. That can be relaxed when pasting in output but we need the written text to be within the bounds. Thanks Chris On 1/4/2023 3:15 am, Alan Cudmore wrote:

Re: The problem of versioning a large project.

>Now we have organized versioning, where our project is divided into separate GIT repositories which are created for each application. why? what's the reasoning for this? django already has apps, so why do you need to make multiple projects for single components? On Friday, March 31, 2023 at

Re: [PATCH rtems-net-legacy] leon3: Replace ambapp_plb with ambapp_plb()

OK to push. Thanks Chris On 31/3/2023 11:20 am, Vijay Kumar Banerjee wrote: > RTEMS commit 2c07f24af210c4738fbe6f75a53c58fbd80fb658 removed the ambapp_plb > global variable > --- > bsps/sparc/leon3/net/leon_greth.c| 3 ++- > bsps/sparc/leon3/net/leon_open_eth.c | 5 +++-- >

Re: [PATCH rtems-lwip] rtemslwip/xil_shims: Avoid hang in IRQ context

OK Chris On 31/3/2023 3:49 am, Kinsey Moore wrote: > Do not try to alter IRQ server handlers while executing in the IRQ > server thread context. This change avoids a deadlock in CGEM error > condition handling that causes a reinitialization of the driver which > attempts to reinstall the IRQ

Re: [PATCH 2/3] bsps/microblaze: Add support for multiple UARTs

On 31/3/2023 2:55 am, Alex White wrote: > On Wed, Mar 29, 2023 at 11:04 PM Chris Johns wrote: >> >> On 30/3/2023 12:26 pm, Sam Price wrote: >>> Same IP as the regular KCU105. >>> The current uart ip is dependent on the fpga. >>> I don't believe this modi

Re: [RBW] ISO: Padded Cycling Gloves Sans Velcro

Sorry, missed that you were looking for padded gloves. On Thursday, March 30, 2023 at 2:22:26 PM UTC-4 JohnS wrote: > I like the Giro Zero CS glove, no velcro, no padding. I were them mostly > for the grip they provide. Good deal on them now at BTD if you like black > and size XL.

Re: [RBW] ISO: Padded Cycling Gloves Sans Velcro

I like the Giro Zero CS glove, no velcro, no padding. I were them mostly for the grip they provide. Good deal on them now at BTD if you like black and size XL. https://www.biketiresdirect.com/product/giro-zero-cs-glove_1?sg=1 John On Thursday, March 30, 2023 at 10:17:10 AM UTC-4

Re: [RBW] Hozan Bottom Bracket Tapping Tool

Thanks Eric L, everything else came off the bike easily, so go figure. Making progress slowly. Thank you Rob and Nick, my homemade tools are ok for now, but I should really get a quality tool next time I have this problem. John On Thursday, March 30, 2023 at 4:03:16 AM UTC-4 Nick Payne wrote:

Re: [PATCH 2/3] bsps/microblaze: Add support for multiple UARTs

On 30/3/2023 12:26 pm, Sam Price wrote: > Same IP as the regular KCU105. > The current uart ip is dependent on the fpga. > I don't believe this modifies the kcu105 bsp, but allows other bsps to > support up to 4 uarts. I am not sure if this patch is OK. If the UART driver is needed for a console

Re: [PATCH] Add support for ELF notes

On 30/3/2023 2:07 am, Sebastian Huber wrote: > On 28.03.23 23:46, Chris Johns wrote: >> On 29/3/2023 5:36 am, Sebastian Huber wrote: >>> On 28.03.23 09:26, Chris Johns wrote: >>>> On 28/3/2023 6:20 pm, Sebastian Huber wrote: >>>>> On 28.03.23 09:03, C

Re: [PATCH rtems-lwip 1/2] rtemslwip: Use common lwipopts for all BSPs

This looks good. Thanks for cleaning this up. Chris On 30/3/2023 7:51 am, Kinsey Moore wrote: > This reworks all BSPs to use a shared lwipopts.h that includes > lwipbspopts.h for per-BSP configuration instead of having lwIP > configuration scattered everywhere for individual BSPs. This also >

Re: [PATCH 2/3] bsps/microblaze: Add support for multiple UARTs

On 30/3/2023 6:22 am, Alex White wrote: > From: "Maldonado, Sergio E. (GSFC-580.0)" .../microblaze/microblaze_fpga/optuartirq.yml | 20 ++ > .../microblaze/microblaze_fpga/optuseuart.yml | 17 ++ > .../microblaze_fpga/optuseuart1.yml | 17 ++ > .../microblaze_fpga/optuseuart2.yml

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