Re: “AW:” ?

It seems another pedantic expresion of fascism from redmond software... Regards RMD On 2/1/24 05:51, jan.som...@dlr.de wrote: -Original Message- From: users On Behalf Of Sebastian Huber Sent: Donnerstag, 1. Februar 2024 07:48 To: John Howard ; users@rtems.org Subject: Re: “AW

RE: “AW:” ?

> -Original Message- > From: users On Behalf Of Sebastian Huber > Sent: Donnerstag, 1. Februar 2024 07:48 > To: John Howard ; users@rtems.org > Subject: Re: “AW:” ? > > On 31.01.24 18:20, John Howard wrote: > > Lost in translation. > > > > Anyb

Re: “AW:” ?

On 31.01.24 18:20, John Howard wrote: Lost in translation. Anybody here know what “AW:” in the Subject means? At first, I took it to mean a comical expression of sarcasm because of an accident. Ironically, that’s not it. It is an abbreviation of Antwort (answer) and was probably produced

Re: “AW:” ?

On Wed, Jan 31, 2024 at 11:20 AM John Howard wrote: > Lost in translation. > > Anybody here know what “AW:” in the Subject means? > Should be German version of "RE: " > > At first, I took it to mean a comical expression of sarcasm because of an > a

Re: “AW:” ?

I believe it's the German equivalent of "Re:" - Andrew On 1/31/24, 11:20 AM, "users" wrote: Lost in translation. Anybody here know what “AW:” in the Subject means? At first, I took it to mean a comical expression of sarcasm because of an accident. Ironically, tha

“AW:” ?

Lost in translation. Anybody here know what “AW:” in the Subject means? At first, I took it to mean a comical expression of sarcasm because of an accident. Ironically, that’s not it. -- John ___ users mailing list users@rtems.org http

AW: AW: NOOBS

> -Ursprüngliche Nachricht- > Von: John Howard > Gesendet: Dienstag, 30. Januar 2024 22:59 > An: Sommer, Jan > Betreff: Re: AW: NOOBS > > Hi Jan, > > Thanks for your reply. > > I think the RTEMS dynamic loader can load other ELF’s. DL supports

Re: AW: Rust on RTEMS

Hello Jan, cool progress! Looking forward to test once things settles a bit, although I'm more of thumb person in arm world. :-) Thanks for sharing! Karel On 1/30/24 11:03, Frank Kühndel wrote: On 1/29/24 19:27, jan.som...@dlr.de wrote: Hi everyone, Sorry for the delayed response. Yes,

AW: AW: Rust on RTEMS

> -Ursprüngliche Nachricht- > Von: Frank Kühndel > Gesendet: Dienstag, 30. Januar 2024 11:03 > An: Sommer, Jan ; j...@rtems.org > Cc: dwaine.s.mol...@nasa.gov; users@rtems.org > Betreff: Re: AW: Rust on RTEMS > > Hello Jan, > > thanks for the info and

Re: AW: Rust on RTEMS

Hello Jan, thanks for the info and all your efforts. Are you planing to add a short "How to use Rust with RTEMS?" section to the RTEMS user manual? I am asking because I was thinking of writing a description on how to use Rust with `#![no_std]` and `#![no_main]` into the user manual.

AW: NOOBS

Hi John, > -Ursprüngliche Nachricht- > Von: users Im Auftrag von John Howard > Gesendet: Dienstag, 30. Januar 2024 02:56 > An: users@rtems.org > Betreff: NOOBS > > I used RSB 5.3 to build RTEMS 5.3 for Raspberry Pi Zero W. > > (At least I think I did. Untested yet.) > > Several

AW: Rust on RTEMS

Hi everyone, Sorry for the delayed response. Yes, that’s me. I am responsible for the RTEMS related work-package in the “cRustacea in Space” project. One of the goals is to create a prototypical port of Rust to RTEMS for our example target platform (Xilinx Zynq). The status is currently the

AW: Problems with docs on docs.rtems.org

I opened ticket #4861 Jens Tesat-Spacecom GmbH & Co. KG Sitz: Backnang; Registergericht: Amtsgericht Stuttgart HRA 270977 Persoenlich haftender Gesellschafter: Tesat-Spacecom Geschaeftsfuehrungs GmbH; Sitz: Backnang;

AW: Running two RTEMS instances on two RISC-V harts

Hi Jan, well, in the beginning there was a system with just one telescope. Now a second shall be added. Easy as 1-2-3: duplicate the software and run it on two cores. No SW changes needed. Developers like me are expensive J That’s how corporate thinks. Driving a telescope involves not just a

AW: RTEMS trap handling versus RISCV mtvec BASE and MODE

Hesham Almatary wrote: > You might be confusing taking BASE[XLEN-1:2] (see Figure 3.8) with shifting > an address by 2. RTEMS aligns _RISCV_Exception_handler to 4 bytes as per the > specification, so you'd always end up with an address with zeros in the least > significant 2 bits. So,

Re: AW: RTEMS mkimage.py for U-Boot scripts

tml?highlight=commit#creating-a-patch Thanks Chris > > -Ursprüngliche Nachricht- > Von: users Im Auftrag von andre.nahrw...@dlr.de > Gesendet: Donnerstag, 11. Februar 2021 16:14 > An: users@rtems.org > Betreff: AW: RTEMS mkimage.py for U-Boot scripts > > Hello

AW: RTEMS mkimage.py for U-Boot scripts

There has been a small typo in the previous patch. -Ursprüngliche Nachricht- Von: users Im Auftrag von andre.nahrw...@dlr.de Gesendet: Donnerstag, 11. Februar 2021 16:14 An: users@rtems.org Betreff: AW: RTEMS mkimage.py for U-Boot scripts Hello, after some digging I think I found

AW: RTEMS mkimage.py for U-Boot scripts

Hello, after some digging I think I found the problem and at least a workaround. As a disclaimer, I do not know if this really counts as a general fix. I have not invested enough time to dig through the original mkimage U-Boot source to figure this out. But I have attached my workaround patch

AW: rtems-test with serial device and run.cfg

> -Ursprüngliche Nachricht- > Von: Chris Johns [mailto:chr...@rtems.org] > Gesendet: Mittwoch, 8. April 2020 02:57 > An: Sommer, Jan; users@rtems.org > Betreff: Re: rtems-test with serial device and run.cfg > [...] > > Which seems to be caused by this: > > > > Traceback (most recent

AW: rtems-test with serial device and run.cfg

> -Ursprüngliche Nachricht- > Von: Chris Johns [mailto:chr...@rtems.org] > Gesendet: Mittwoch, 8. April 2020 02:57 > An: Sommer, Jan; users@rtems.org > Betreff: Re: rtems-test with serial device and run.cfg > > On 2020-04-07 23:37, jan.som...@dlr.de wrote: > > I have trouble figuring

AW: write a network driver

> -Ursprüngliche Nachricht- > Von: users [mailto:users-boun...@rtems.org] Im Auftrag von Sebastian Huber > Gesendet: Mittwoch, 11. März 2020 09:17 > An: mojtaba nadi; users@rtems.org > Betreff: Re: write a network driver > > Hello Mojtaba, > > On 11/03/2020 06:44, mojtaba nadi wrote: > >

AW: LEON3 RTEMS rc7 Tool Issue

The rc7 change log talks about DWARF v2 versus v4 incompatibilities: 1.3-rc7 (20191129) - released LLVM/Clang 8.0 toolchain built on stable LLVM branch * UT700/UT699E support with errata work-arounds * REX support: LEON-REX backend (16-bit ISA) added * various LEON optimizations

AW: RTEMS ethernet stack and drvmgr

Thanks, I think I get it now. So for example the https://git.rtems.org/rtems/tree/bsps/arm/atsam/net/if_atsam.c is the legacy one. And https://git.rtems.org/rtems-libbsd/tree/rtemsbsd/sys/dev/atsam/if_atsam.c is the newer version ported to libbsd. Best regards, Jan -Ursprüngliche

Re: AW: sparc and trap 4 (floating point disabled)

Hello Jens, On 04/12/2019 13:24, Schweikhardt, Jens (TSPCE3-TL4) wrote: If it isn't already, may I suggest adding some wording in the sparc-specific documentation? It might save someone in the future a bit of head-scratching.:-) Thanks! yes, everyone can help to improve the documentation:

AW: sparc and trap 4 (floating point disabled)

Hello Sebastian et al., > Hello Jens, > in uni-processor configurations a lazy floating-point context switch is done > on SPARC. You can search for SPARC_USE_LAZY_FP_SWITCH in the sources. This appears to be the reason for the observed behavior. Looking at the disassembled application code:

AW: Problems running RTEMS on Raspberry Pi2

Hi Chris, > -Ursprüngliche Nachricht- > Von: Chris Johns [mailto:chr...@rtems.org] > Gesendet: Freitag, 26. Juli 2019 02:26 > An: Nils Hölscher > Cc: Sebastian Huber; Sommer, Jan; users@rtems.org > Betreff: Re: Problems running RTEMS on Raspberry Pi2 > > Hi Nils, > > Many thanks for

AW: pc686: --enable-rtems-debug not working

Hi Joel, Thank you for the hint. It worked and the testsuite runs through again now. I attached a patch for the master branch. Best regards, Jan Von: Joel Sherrill [mailto:j...@rtems.org] Gesendet: Donnerstag, 18. April 2019 15:43 An: Sommer, Jan Cc: rtems-us...@rtems.org Betreff: Re:

AW: device-tree example for altera-cyclone-v bsp

Hi Christian, If your change is only regarding to the clock frequency then it should be possible to simply pass the value to configure: configure --target=arm-rtems4.12 --enable-rtemsbsp=altera-cyclone-v BSP_ARM_A9MPCORE_PERIPHCLK=1000U At least that is what we do with the microzed

AW: Problem intializing the Network Stack

It uses RTEMS 5.0 -Ursprüngliche Nachricht- Von: Chris Johns [mailto:chr...@rtems.org] Gesendet: Mittwoch, 14. Februar 2018 00:40 An: Sascha.Tetkov; users@rtems.org Betreff: Re: Problem intializing the Network Stack On 14/02/2018 00:15, Sascha.Tetkov wrote: > Hello, > > I'm currently