AW: AW: [PATCH v3 2/3] amd64: Add to build

> -Ursprüngliche Nachricht- > Von: Chris Johns [mailto:chr...@rtems.org] > Gesendet: Mittwoch, 12. Februar 2020 00:36 > An: Sommer, Jan; sebastian.hu...@embedded-brains.de; devel@rtems.org > Betreff: Re: AW: [PATCH v3 2/3] amd64: Add to build > > On 12/2/20 12:21 am, jan.som...@dlr.de wr

Description of rtems-libbsd testsuite applications

Hello, is there already somewhere a file which gives some short description what the different test applications in the testsuite directory (are supposed to) do? If not, would you accept patches with some short descriptions and maybe an example output? Cheers, Jan Deutsches Zentrum für Luf

AW: Description of rtems-libbsd testsuite applications

Thanks for the suggestions. I have to figure out what some of the tests do anyway and writing it down somewhere will also prevent future-me to do it again. If I have some notes, is it ok to prepare a README.md inside the individual test's directory or do you prefer a single README inside the test

AW: Loading RTEMS applications from u-boot on Raspberry Pi 2

Hi Cláudio, I build a current BSP for the raspberry pi 2 recently (atm without SMP though). > -Ursprüngliche Nachricht- > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Cláudio Maia > Gesendet: Montag, 17. Februar 2020 21:19 > An: devel@rtems.org > Betreff: Loading RTEMS appli

AW: [PATCH v4 0/3] [rtems-libbsd] Fix compilation for amd64

Hi Chris, > -Ursprüngliche Nachricht- > Von: Chris Johns [mailto:chr...@rtems.org] > Gesendet: Mittwoch, 19. Februar 2020 00:13 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: [PATCH v4 0/3] [rtems-libbsd] Fix compilation for amd64 > > On 18/2/20 9:21 pm, Jan Sommer wrote: > > Similar t

AW: [PATCH] drvmgr: Fix determination of prefix in grlib uart driver

Hello, Could someone please push this change? There has been a lot of activity on this list recently, and I fear I will lose track at some point. Cheers, Jan > -Ursprüngliche Nachricht- > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Jan Sommer > Gesendet: Mittwoch, 12.

AW: [PATCH v4 0/3] [rtems-libbsd] Fix compilation for amd64

Are there any further comments regarding these patches? Is the solution with the "path-mappings" acceptable or do you prefer something different? Beste regards, Jan > -Ursprüngliche Nachricht- > Von: Sommer, Jan > Gesendet: Dienstag, 18. Februar 2020 11:22 > An: devel@rtems.org > Cc:

AW: [PATCH v4 0/3] [rtems-libbsd] Fix compilation for amd64

Hello, I am currently working on the backport of the i386 patch set for the 5-freebsd-12 branch (I don't see any use in backporting these amd64 patches). The question is, if I should use the path-mappings approach introduced with this patch set or keep the "if cpu == i386" which is the current s

AW: [PATCH 0/3] [rtems-libbsd] [backport] Fix compilation issue for

Please ignore this patch set. We managed to get the e1000 driver working, today. I will submit an updated version with it included next week. Best regards, Jan > -Ursprüngliche Nachricht- > Von: Sommer, Jan > Gesendet: Freitag, 6. März 2020 11:09 > An: devel@rtems.org > Cc: Sommer, Ja

AW: [PATCH v2 3/3] i386: Port to RTEMS

> -Ursprüngliche Nachricht- > Von: Sommer, Jan > Gesendet: Montag, 9. März 2020 16:11 > An: devel@rtems.org > Cc: Sommer, Jan > Betreff: [PATCH v2 3/3] i386: Port to RTEMS > > - Update imported files to compile rtems-libbsd for i386 based BSPs > --- > freebsd/sbin/sysctl/sysctl.c

AW: Successfully built EPICS 7 with RTEMS 5 for mvme6100

> Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Joel Sherrill > Gesendet: Mittwoch, 18. März 2020 22:18 > An: Heinz Junkes > Cc: rtems-de...@rtems.org > Betreff: Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100 > > > > On Wed, Mar 18, 2020 at 2:38 PM Heinz Junkes wrote: >

AW: AW: [PATCH v2 3/3] i386: Port to RTEMS

Thank you. That makes sense. I will prepare a new version. Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] Gesendet: Freitag, 20. März 2020 12:54 An: Sommer, Jan; devel@rtems.org Betreff: Re: AW: [PATCH v2 3/3] i386: Port to RTEMS On 10/03/2020 09:12, jan.som...@dlr.de

AW: [PATCH v3 3/3] i386: Port to RTEMS

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Montag, 23. März 2020 10:59 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: [PATCH v3 3/3] i386: Port to RTEMS > > On 23/03/2020 09:06, Jan Sommer wrote: > > > @@ -4597,7 +4599,1

AW: AW: [PATCH v3 3/3] i386: Port to RTEMS

Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] Gesendet: Montag, 23. März 2020 14:20 An: Sommer, Jan; devel@rtems.org Betreff: Re: AW: [PATCH v3 3/3] i386: Port to RTEMS > > > > -Ursprüngliche Nachricht- > > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von > >

AW: PC BSP bset failure

Hi Joel, Thanks, yes the changes have not been merged yet to the 5-freebsd-12 branch. I am about to prepare the next version of the patch set. Cheers, Jan Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Joel Sherrill Gesendet: Dienstag, 7. April 2020 01:31 An: rtems-de...@rtems.or

AW: [PATCH 0/2] [rtems-tools] Allow telnet tty devices for run.cfg

Could you give me some direction where we would add the documentation and what is missing? The pc-run.ini is basically a copy of the xilinx_zynq_zedboard.ini with just a different tester. Or do you mean the change in the run.cfg? Von: Gedare Bloom [mailto:ged...@rtems.org] Gesendet: Mittwoch, 8.

Re: [PATCH v4 3/3] i386: Port to RTEMS

> -Ursprüngliche Nachricht- > Von: Sommer, Jan > Gesendet: Donnerstag, 9. April 2020 15:57 > An: devel@rtems.org > Cc: Sommer, Jan > Betreff: [PATCH v4 3/3] i386: Port to RTEMS > > - Update imported files to compile rtems-libbsd for i386 based BSPs > --- [...] > diff --git a/freebsd/sy

AW: [PATCH v4 3/3] i386: Port to RTEMS

> -Ursprüngliche Nachricht- > Von: Sommer, Jan > Gesendet: Donnerstag, 9. April 2020 15:57 > An: devel@rtems.org > Cc: Sommer, Jan > Betreff: [PATCH v4 3/3] i386: Port to RTEMS > > - Update imported files to compile rtems-libbsd for i386 based BSPs > --- > freebsd-org

RISCV-SIS: Different busy cycles per tick for primary and secondary cores

Hello, We noticed a bit strange behavior while doing some measurements with the riscv bsps running on SIS. If we run "T_get_one_clock_tick_busy" to get a base reference for busy cycles, the values between cpu0 and other secondary cores differ by a constant value. For example for a 200us tick tim

RE: [PATCH rtems] arm/xilinx: Fix zynq-uart interrupt receive

Is this patch also something to backport to RTEMS5 or is this problem only specific to the current version? Best regards, Jan > -Original Message- > From: devel On Behalf Of Chris Johns > Sent: Wednesday, August 18, 2021 1:02 AM > To: j...@rtems.org > Cc: rtems-de...@rtems.org > S

RE: [PATCH v1 1/1] gpiolib/grgpio: Add support for newer grgpio features

Does anyone have any objections to this? See also https://lists.rtems.org/pipermail/devel/2021-July/068086.html for the cover letter. Best regards, Jan > -Original Message- > From: Sommer, Jan > Sent: Thursday, July 1, 2021 5:44 PM > To: devel@rtems.org > Cc: softw...@gaisler.com;

RE: [PATCH v1 1/1] gpiolib/grgpio: Add support for newer grgpio features

Hi Daniel, As far as I understand the code the bus sets the “info.irq” to the pirq value from the PnP information of the devices. Then the “drvmgr_interrupt_register(priv->dev, irq, "grgpio", isr, arg) )“ will register the isr with “irq” as an offset of pirq. So, for devices with GENIRQ == 0,

RE: [PATCH v1 1/1] gpiolib/grgpio: Add support for newer grgpio features

Hi Daniel, Did you by any chance found the time to have another look at it or test it on the GR712RC? Best regards, Jan From: devel On Behalf Of jan.som...@dlr.de Sent: Friday, August 27, 2021 2:36 PM To: dan...@gaisler.com; devel@rtems.org Cc: softw...@gaisler.com Subject: RE: [PATCH v1

RE: [PATCH v1] bsps/riscv: Give enough time for clock driver initialization

Sorry, for digging out this old patch. > On Mon, Jun 7, 2021 at 1:57 PM wrote: > > > > -Original Message- > > From: Gedare Bloom > > Sent: Monday, June 7, 2021 7:00 PM > > To: Sommer, Jan > > Cc: devel@rtems.org > > Subject: Re: [PATCH v1] bsps/riscv: Give enough time for clock driver

RE: V2 : Zynq/ZynqMP UART driver

> -Original Message- > From: devel On Behalf Of chr...@rtems.org > Sent: Thursday, September 9, 2021 10:25 AM > To: devel@rtems.org > Subject: V2 : Zynq/ZynqMP UART driver > > Hi, > > I have tested this version on zynq and zynqmp hardware and I am not seeing > any issues. > > I was s

Move to bsps finished?

Hello, I just wanted to ask if the reorganization of the BSP source code is more or less finished? Then this might be a good point for us to pull the changes into our local copies to be close to the development branch again otherwise it might be easier to wait a bit longer. Best regards, J

RE: Move to bsps finished?

> -Original Message- > From: Amaan Cheval [mailto:amaan.che...@gmail.com] > Sent: Tuesday, May 15, 2018 2:46 PM > To: Sommer, Jan > Cc: RTEMS > Subject: Re: Move to bsps finished? > > Hey Jan! > > The ticket tracking the BSP reorganization seems to have been closed > once the docs were

RE: [GSoC - x86_64] Using FreeBSD's UEFI loader for RTEMS static binaries

> -Original Message- > From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Chris Johns > Sent: Thursday, June 14, 2018 7:56 AM > To: j...@rtems.org; Amaan Cheval > Cc: RTEMS > Subject: Re: [GSoC - x86_64] Using FreeBSD's UEFI loader for RTEMS static > binaries [...] > > >> > >

RE: new to rtems , looking for some help

Hi Vijay, I usually start the configuration from the top level directory of rtems, but I would assume that you need to give configure the same options about which platform and BSP to build as in the normal setup. Just running ./configure will probably not work. Check out the getting started pag

RE: docs not building to PDF

There is also Kroki: https://kroki.io/ It does the rendering of multiple text based diagram languages, including PlantUML, Mermaid, Ditaa and a bunch of others. Then you only need one tool for it. Best regards, Jan > -Original Message- > From: devel On Behalf Of Chris Johns > Sent:

RE: GitLab and BuildBot

> -Original Message- > From: devel On Behalf Of Chris Johns > Sent: Donnerstag, 9. Februar 2023 23:26 > To: Christian MAUDERER ; > RTEMS Devel > Subject: Re: GitLab and BuildBot > > > Thanks and it is great to get the feedback. We normally only ever hear from > people when it does not w

RE: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

> -Original Message- > From: Joel Sherrill > Sent: Freitag, 10. Februar 2023 15:21 > To: Sommer, Jan > Cc: devel@rtems.org > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0 > > > > On Fri, Feb 10, 2023 at 3:16 AM Jan Sommer > wrote: > > >

New GPIO-API merged?

Hello everyone, Alex' patch reminded me that there was work done related a new general GPIO-API. Has that been finished? I tried to find the corresponding header files, but couldn't. So, I was wondering what the current status is. Best regards, Jan Deutsches Zentrum für Luft- und Raumfahr

RE: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

> -Original Message- > From: Hesham Almatary > Sent: Montag, 13. Februar 2023 16:19 > To: Sommer, Jan > Cc: j...@rtems.org; devel@rtems.org > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0 > > On Mon, 13 Feb 2023 at 12:12, wrote: > > > > > -Original Message-

RE: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

Hello everyone, I tried to build a riscv BSP with the information from Hesham. Thanks again. It now compiles the files, but produces a lot of warnings and fails to link in the end. The warnings are of this type ../../../cpukit/score/cpu/riscv/riscv-exception-handler.S:48:10: warning: unknown op

RE: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

> -Original Message- > From: Hesham Almatary > Sent: Mittwoch, 22. Februar 2023 14:34 > To: Sommer, Jan > Cc: j...@rtems.org; devel@rtems.org > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0 > > On Tue, 21 Feb 2023 at 14:30, wrote: > > > > Hello everyone, > > > > I t

RE: Interested for GSoC 2023

> -Original Message- > From: devel On Behalf Of Karel Gardas > Sent: Montag, 27. Februar 2023 09:16 > To: j...@rtems.org; Vihas Makwana > Cc: rtems-de...@rtems.org > Subject: Re: Interested for GSoC 2023 > > On 2/27/23 02:16, Joel Sherrill wrote: > > Another GCC related project could

RE: New GPIO-API merged?

We now found this general GPIO API here: https://github.com/RTEMS/rtems/blob/master/bsps/include/bsp/gpio.h Is this the current one to use when implementing a new GPIO driver? > -Original Message- > From: devel On Behalf Of jan.som...@dlr.de > Sent: Mittwoch, 15. Februar 2023 08:40 > To

RE: libbsd fails to link on i386

Hi Joel, I remember I spent some time fiddling with the bus.h include order. I can try to have a look at it some time next week. Best regards, Jan From: devel On Behalf Of Joel Sherrill Sent: Wednesday, August 17, 2022 11:24 PM To: rtems-de...@rtems.org Subject: libbsd fails to l

RE: libbsd fails to link on i386

Hi Joel, Sorry for the long delay. I tried to reproduce the error locally. For me building rtems and rtems-libbsd master for pc386 and pc686 works. I get some undefined references for the 6-freebsd-12 branch though. Which branch of rtems-libbsd did you use? Best regards, Jan F

SMP for pc686 BSP

Hello, I have been working recently to enable SMP for the pc686-BSP and managed to get a basic setup running with 2 cores which currently passes 44/57 smptests. Next step is to make it work for arbitrary numbers of cores. The goal is to push the patches upstream. That's why I would like to ask t

AW: SMP for pc686 BSP

> -Ursprüngliche Nachricht- > Von: Joel Sherrill [mailto:j...@rtems.org] > Gesendet: Donnerstag, 16. Mai 2019 16:33 > An: Sommer, Jan > Cc: rtems-de...@rtems.org > Betreff: Re: SMP for pc686 BSP > > > > On Thu, May 16, 2019, 9:01 AM wrote: > > > Hello, > > I have been wor

AW: SMP for pc686 BSP

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Freitag, 17. Mai 2019 06:57 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: SMP for pc686 BSP > > Hello Jan, > > there is also an amd64 BSP: > > https://docs.rtems.org/branches/

AW: AW: SMP for pc686 BSP

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Freitag, 17. Mai 2019 07:00 > An: Chris Johns; Sommer, Jan; j...@rtems.org > Cc: devel@rtems.org > Betreff: Re: AW: SMP for pc686 BSP > > On 17/05/2019 04:26, Chris Johns wrote: > >

AW: GSoC Project | Basic Support for Trace Compass

Hi Ravindra, > -Ursprüngliche Nachricht- > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Ravindra > Kumar Meena > Gesendet: Dienstag, 25. Juni 2019 14:39 > An: Sebastian Huber > Cc: devel > Betreff: Re: GSoC Project | Basic Support for Trace Compass > > Hi Sebastian, > > Lik

AW: GSoC Project | Basic support for Trace Compass

Hi Ravindra, I have only had a look at the documentation and not worked with CTF at all so far, so take my words with a grain of salt. I don’t really get why you define 32 different streams in your metadata which means you have to copy the event definition as well 32 times. This amount of duplic

AW: GSoC Project | Basic Support for Trace Compass

> -Ursprüngliche Nachricht- > Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Ravindra > Kumar Meena > Gesendet: Dienstag, 6. August 2019 10:59 > An: Sebastian Huber > Cc: rtems-de...@rtems.org > Betreff: Re: GSoC Project | Basic Support for Trace Compass > > e.g. >

Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

Hello, I tried compiling the RTEMS with fortran support for the Leon2/3 processors. Building the cross-compiler with gfortran and the bsp worked both fine (I set the bsp to compile with --mhard-float). A small example program for the Leon3 compiles and runs as expected, however for the leon2 I

AW: Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Montag, 27. Februar 2017 13:46 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: Undefined reference to `__sync_bool_compare_and_swap_4' for > some Leon configurations with gfortran

AW: AW: Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

Ok, thanks for the clarification. I will try to create a patch for gcc and put rtems CC for the discussion. Best regards, Jan > -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Montag, 27. Februar 2017 15:01 > An: Sommer, Jan; de

AW: AW: AW: Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Montag, 27. Februar 2017 15:11 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: AW: AW: Undefined reference to > `__sync_bool_compare_and_swap_4' for some Leon configurations with > g

__sync_-builtins cause undefined references on some sparc targets

Hello, I compiled the gcc 6.3.0 for the leon2 processor for RTEMS (i.e. sparc-rtems4.12-*). When linking a fortran program for the leon2 processor I get undefined references for `__sync_bool_compare_and_swap_4' (see below). According to the discussion on the rtems mailinglist the __sync_*-operat

Re: Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

> -Ursprüngliche Nachricht- > Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Gesendet: Montag, 27. Februar 2017 15:25 > An: Sommer, Jan; devel@rtems.org > Betreff: Re: AW: AW: AW: Undefined reference to > `__sync_bool_compare_and_swap_4' for some Leon configurations wi

RE: Undefined reference to `__sync_bool_compare_and_swap_4' for some Leon configurations with gfortran

> -Original Message- > From: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de] > Sent: Wednesday, March 01, 2017 7:47 AM > To: Sommer, Jan; devel@rtems.org > Subject: Re: Undefined reference to `__sync_bool_compare_and_swap_4' for > some Leon configurations with gfortran [...] >

Naming convention for Rust target platforms

Hi everyone, As mentioned in the other Rust thread, I am working on an initial Rust port for RTEMS. The target platform for testing is the ARM Xilinx Zynq-7000 based BSPs. Where I am not completely sure, is how to name the new target for Rust (see here the current list: https://doc.rust-lang.or

AW: Naming convention for Rust target platforms

> -Ursprüngliche Nachricht- > Von: Sebastian Huber > Gesendet: Dienstag, 30. Januar 2024 11:08 > An: devel > Cc: Sommer, Jan > Betreff: Re: Naming convention for Rust target platforms > > Hello Jan, > > On 29.01.24 19:41, jan.som...@dlr.de wrote: > > So, for the Zynq and similar BSPs

AW: AW: Naming convention for Rust target platforms

> -Ursprüngliche Nachricht- > Von: Sebastian Huber > Gesendet: Mittwoch, 31. Januar 2024 08:08 > An: Sommer, Jan ; devel@rtems.org > Betreff: Re: AW: Naming convention for Rust target platforms > > On 30.01.24 13:45, jan.som...@dlr.de wrote: > >> -Ursprüngliche Nachricht- > >> V

AW: Naming convention for Rust target platforms

> -Ursprüngliche Nachricht- > Von: Frank Kühndel > Gesendet: Dienstag, 30. Januar 2024 18:14 > An: Sommer, Jan ; devel@rtems.org > Betreff: Re: Naming convention for Rust target platforms > > Hello Jan, > > On 1/29/24 19:41, jan.som...@dlr.de wrote: > > Hi everyone, > > > > As mentione

AW: Naming convention for Rust target platforms

Von: Joel Sherrill Gesendet: Mittwoch, 31. Januar 2024 16:57 An: Karel Gardas Cc: Frank Kühndel ; Sommer, Jan ; devel@rtems.org Betreff: Re: Naming convention for Rust target platforms On Wed, Jan 31, 2024 at 12:31 AM Karel Gardas mailto:karel@functional.vision>> wrote: On 1/30/24 18:13, F

AW: Naming convention for Rust target platforms

Hm. Somehow Outlook botched the inline quotes of the html mail. Does it work now? Von: Joel Sherrill Gesendet: Mittwoch, 31. Januar 2024 16:57 An: Karel Gardas Cc: Frank Kühndel ; Sommer, Jan ; devel@rtems.org Betreff: Re: Naming convention for Rust target platforms On Wed, Jan 31, 2024 at 12:

AW: Clone RTEMS Repositories via HTTPS?

Hi, I used to clone the repositories of git.rtems.org via https, because ssh is blocked outside of our intranet. I just tried again and it seems to work: /tmp> git clone https://git.rtems.org/rtems-tools/ Klone nach 'rtems-tools' ... /tmp> With the main rtems-repository cloning takes quite a l

AW: Requirements Format

In one project we use Doorstop (https://doorstop.readthedocs.io/en/latest/reference/items/) due to a lack of an actual DOORS license for every partner. For software developers it is quite easy to handle as it has a CLI and can be easily integrated with git as everything is a text file. However,

[PATCH] drvmgr: Fix determination of prefix in grlib uart driver

Hi, A collegue of mine stumbled upon this small bug. Best regards, Jan Deutsches Zentrum für Luft- und Raumfahrt e. V. (DLR) German Aerospace Center Simulation and Software Technology | Software for Space Systems and Interactive Visualization | Lilienthalplatz 7 | 38108 Braunschweig | Ger

<    1   2