[PATCH] 5: Update rtems-tools
Fixes #3827
---
rtems/config/tools/rtems-tools-5-1.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtems/config/tools/rtems-tools-5-1.cfg
b/rtems/config/tools/rtems-tools-5-1.cfg
index c633093..89e5d19 100644
--- a/rtems/config/tools/rtems-tools-5-1.cfg
+++ b/rtems/config/tools/rtems-tools-5-1.cfg
@@ -10,7 +10,7 @@
%define rtems_tools_source rtems-tools-%{rtems_tools_version}
%define rtems_tools_ext xz
%else
- %define rtems_tools_version 12bd8f77bad4779319039fd7be33d006e10f5618
+ %define rtems_tools_version c02459ee6533e73ac7b65f50f08ec254a0e6e84c
%define rtems_tools_ext bz2
%endif
--
2.17.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Re: [PATCH] 5: Update rtems-tools
On 29/11/2019 12:49, Hesham Almatary wrote: Fixes #3827 Ok. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] 5: Update the hash for the new rtems-tools revision
Fixes #3827
---
rtems/config/tools/rtems-tools-5-1.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtems/config/tools/rtems-tools-5-1.cfg
b/rtems/config/tools/rtems-tools-5-1.cfg
index 89e5d19..289e68d 100644
--- a/rtems/config/tools/rtems-tools-5-1.cfg
+++ b/rtems/config/tools/rtems-tools-5-1.cfg
@@ -17,7 +17,7 @@
%define rtems_tools_source rtems-tools-%{rtems_tools_version}
%source set rtems-tools
https://git.rtems.org/rtems-tools/snapshot/%{rtems_tools_source}.tar.%{rtems_tools_ext}
%hash sha512 rtems-tools-%{rtems_tools_version}.tar.bz2 \
-
1yCWa+4c1/RITK37yLrSrA104HkS3wtm+QCpWeZS0YCAFX4xyVfKDJpPDYvsmdzAt8BuYaYrlV7yMNljD2/hEQ==
+
ea664df9c7cd07344c6293edbd686d84e4cd854e62f671175d2f5e9fbf636fcc62d0741ee2cd72834ce3c1ae02df7d50391ce8527897000d3d9115bb78963a30
#
# Optionally enable/disable building the RTEMS Tools via the command line.
--
2.17.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
[PATCH] user: Add a link for the setup of frdme310arty BSP
Signed-off-by: Pragnesh Patel --- user/bsps/bsps-riscv.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/user/bsps/bsps-riscv.rst b/user/bsps/bsps-riscv.rst index 0799ad6..40d7606 100644 --- a/user/bsps/bsps-riscv.rst +++ b/user/bsps/bsps-riscv.rst @@ -93,6 +93,9 @@ The following options are available at the configure command line. Enables support sifive Freedom E310 Arty board if defined to a non-zero value,otherwise it is disabled (disabled by default) + Please see https://github.com/pragnesh26992/rtems and follow + README-frdme310arty.md + Interrupt Controller -- 2.17.1 ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
raspberrypi BSP current status
I am interested in contributing to the raspberry pi BSP. As of now RTEMS only has support for RPi1 and RPi2, but It seems that most of the code for RPi2 should work unmodified for RPi3 and RPi4, I am sure about the peripherals since the base address of the registers haven't changed in the new ones. I looked at the previous GSOC work and README section of the raspberrypi, but they look not up to date. I want to know the current status of the BSP, what all is completed, yet to be done? so that's I could start working on something. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: raspberrypi BSP current status
On 29/11/2019 21:12, Niteesh wrote: > I am interested in contributing to the raspberry pi BSP. As of now RTEMS > only has support for RPi1 and RPi2, but It seems that most of the code > for RPi2 should work unmodified for RPi3 and RPi4, I am sure about the > peripherals since the base address of the registers haven't changed in > the new ones. > I looked at the previous GSOC work and README section of the > raspberrypi, but they look not up to date. I want to know the current > status of the BSP, what all is completed, yet to be done? so that's I > could start working on something. > Hello Niteesh, from a quick look there are the following drivers: - Serial - GPIO - I2C - SPI - Some Framebuffer In 2016 a GSoC student tried to port the USB and Ethernet driver. But it seems that this work hadn't been merged: https://devel.rtems.org/wiki/GSoC/2016 Regarding good starting points: I think you already found some with just this mail. - If you have an old Pi1 or 2, you could try to run some basic RTEMS there as a first step. Or did you already try that? - You say that it "should work" on RPi3 and RPi4. It would be great if you could try it and update the documentation if it does. - If you take some notes while doing the tests, it would be great if you could donate them to the documentation so the old README could be replaced: https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#raspberrypi - If you want to start a bigger project you could take a look at the USB work and test it. Most likely it still needs some work. - If you are interested in any other peripheral of the Pi: Just ask. Best regards Christian ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: raspberrypi BSP current status
On Fri, Nov 29, 2019, 3:34 PM Christian Mauderer wrote: > On 29/11/2019 21:12, Niteesh wrote: > > I am interested in contributing to the raspberry pi BSP. As of now RTEMS > > only has support for RPi1 and RPi2, but It seems that most of the code > > for RPi2 should work unmodified for RPi3 and RPi4, I am sure about the > > peripherals since the base address of the registers haven't changed in > > the new ones. > > I looked at the previous GSOC work and README section of the > > raspberrypi, but they look not up to date. I want to know the current > > status of the BSP, what all is completed, yet to be done? so that's I > > could start working on something. > > > > Hello Niteesh, > > from a quick look there are the following drivers: > - Serial > - GPIO > - I2C > - SPI > - Some Framebuffer > > In 2016 a GSoC student tried to port the USB and Ethernet driver. But it > seems that this work hadn't been merged: > > https://devel.rtems.org/wiki/GSoC/2016 > > Regarding good starting points: I think you already found some with just > this mail. > > - If you have an old Pi1 or 2, you could try to run some basic RTEMS > there as a first step. Or did you already try that? > I have not tried it but the RSB bit qemu 4 lists the pi2 as a model. That may be an option. Certainly would be good for automates testing and maybe getting the network driver going > > - You say that it "should work" on RPi3 and RPi4. It would be great if > you could try it and update the documentation if it does. > > - If you take some notes while doing the tests, it would be great if you > could donate them to the documentation so the old README could be > replaced: > https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#raspberrypi > > - If you want to start a bigger project you could take a look at the USB > work and test it. Most likely it still needs some work. > > - If you are interested in any other peripheral of the Pi: Just ask. > > Best regards > > Christian > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
