On Wed, Feb 22, 2023, 9:26 PM Prakhar Agrawal
wrote:
> Hello,
>
> Does the current RTEMS version support the Jetson nano board, if not, do
> you think It will be a good project for gsoc2023? something like porting
> RTEMS to Jetson nano or jetson AGX orin maybe?
>
I'm torn whether this is a good
Hello,
My name is Prakhar Agrawal and I am interested in contributing to RTEMS as
a gsoc this year.
While going through the list of open projects, the BSP executable
conversion project caught my interest.
I have completed the hello world task for gsoc and now looking to start
contributing to the
Hello,
Does the current RTEMS version support the Jetson nano board, if not, do
you think It will be a good project for gsoc2023? something like porting
RTEMS to Jetson nano or jetson AGX orin maybe?
Looking forward to your response.
Best Regards
Prakhar
_
Hi
There will be an RTEMS Open Class held virtually the week of April 24-28
Times each day will be based on the US Central time zone (Chicago).
Adjustments
may be considered to accommodate the participants.
April 24 - Kick Start and Getting Started
April 25-28 - Open Class
Details and registrat
On 22.02.23 16:14, Hesham Almatary wrote:
* Remove BSPs with medany name in them (See #4775).
RV64 BSPs are now all medany by default.
Do we still need the non-medany 64-bit multilibs in GCC? I plan to
adjust the multilib selection a bit and also add multilibs for
non-compact 32-bit variants.
Hi Sebastian,
This ticket has a number of commits logged against it. What remains or can
it be closed?
https://devel.rtems.org/ticket/4666
If it can't be closed, an update on what needs to be done should be added
and maybe the milestone bumped.
Thanks.
--joel
__
On 2/22/23 16:26, Joel Sherrill wrote:
Is it ok to push if I fix the comment?
I confess I have not tried your patch. I noted you have commented out
the gdb-readline8.2.patch. Beside that no surprises and from my side you
can go ahead.
Greetings
Frank
--joel
On Wed, Feb 22, 2023 at 3:29
Hi
This may be mechanical but
https://lists.rtems.org/pipermail/build/2023-February/date.html shows
recent RTEMS test runs with a lot of RISC-V BSP failures. Scanning them, it
seems as though there are 100s of test failures when SMP is enabled. Here
is one example:
https://lists.rtems.org/piperma
This is OK.
Be sure to follow up with a patch to bump the rtems-tools hash in the RSB.
--joel
On Wed, Feb 22, 2023 at 9:14 AM Hesham Almatary
wrote:
> * Only use BSPs supported by GCC's multilibs. This removes rv32imafdc
> * Remove BSPs with medany name in them (See #4775).
> RV64 BSPs are now
Is it ok to push if I fix the comment?
--joel
On Wed, Feb 22, 2023 at 3:29 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:
> Hello Joel,
>
> On 2/21/23 16:25, Joel Sherrill wrote:
> > Subject:
> > [PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6
> > From:
> > Joel She
* Only use BSPs supported by GCC's multilibs. This removes rv32imafdc
* Remove BSPs with medany name in them (See #4775).
RV64 BSPs are now all medany by default.
---
config/rtems-bsps-riscv.ini | 5 ++---
config/rtems-bsps-tiers.ini | 5 ++---
2 files changed, 4 insertions(+), 6 deletions(-)
dif
> -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
On Tue, 21 Feb 2023 at 14:30, wrote:
>
> 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
Hello Joel,
On 2/21/23 16:25, Joel Sherrill wrote:
Subject:
[PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6
From:
Joel Sherrill
Date:
2/21/23, 16:25
To:
devel@rtems.org
---
rtems/config/6/rtems-default.bset | 2 +-
rtems/config/tools/rtems-gdb-13.1.cfg | 16 ++
14 matches
Mail list logo