The usage of a build date prevents reproducible builds.
---
common/conf.py | 25 +
common/waf.py | 22 ++
wscript| 39 ---
3 files changed, 39 insertions(+), 47 deletions(-)
diff --git a/common/conf.py b/comm
On 07/01/2019 12:03, Sebastian Huber wrote:
Sebastian Huber (6):
Remove build date from first page
Update general copyright notice
Remove superfluous word "Copyright"
Add common header.rst to reduce copy and paste
Update header.rst
user: Rework overview
Any comments to the rem
Hi,
I am GSOC aspirant. I am new to RTEMs and this project interests me a lot.
I have set up the RTEMs development environment on Ubuntu and also have run
"hello world application".
I would like to know more about it. Please, can you connect me to the
developers who are contributing to the RTEMs?
On 08/01/2019 16:04, Joel Sherrill wrote:
How should we progress with my gcc patches that largely eliminate the
need for specs files? I can start updating, testing, and submitting
them to gcc if we like.
I think the basic problem with the dummy Newlib crt0.o which is used for
the configure c
On 08/01/2019 08:57, Sebastian Huber wrote:
It is not clear why the failures didn't show up on the Qemu test runs.
I did some tests with Qemu and the sp37 fails also here. Somehow I
didn't notice this failure before.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178
Hello Jiri,
could you please rebase your work to this RTEMS commit:
https://git.rtems.org/rtems/commit/?id=b9ffc41c9678fb3c5386c1a6ab394656ec85dbc6
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47
On 9/1/19 7:24 pm, Sebastian Huber wrote:
> The usage of a build date prevents reproducible builds.
Nice.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On 9/1/19 7:34 pm, Sebastian Huber wrote:
> On 07/01/2019 12:03, Sebastian Huber wrote:
>> Sebastian Huber (6):
>> Remove build date from first page
>> Update general copyright notice
>> Remove superfluous word "Copyright"
>> Add common header.rst to reduce copy and paste
>> Update h
On 09/01/2019 11:11, Chris Johns wrote:
On 9/1/19 7:34 pm, Sebastian Huber wrote:
On 07/01/2019 12:03, Sebastian Huber wrote:
Sebastian Huber (6):
Remove build date from first page
Update general copyright notice
Remove superfluous word "Copyright"
Add common header.rst to reduc
Hello,
the RSB has currently its own manual in the documentation set:
https://docs.rtems.org/branches/master/rsb/index.html
I think it would make sense to move the RSB documentation into the user
manual as a chapter. If you are new to RTEMS, then dealing with the RSB
is one of the first thing
Hi Ravindra
This link has a list of open projects
https://devel.rtems.org/wiki/Developer/OpenProjects
you can always ask the developers about projects on this list .
Thank you for your interest
--Shashvat
On Wed, Jan 9, 2019 at 2:24 PM Ravindra Meena wrote:
> Hi,
>
> I am GSOC aspirant. I am
---
bsp-howto/ada95_interrupt.rst | 1 -
bsp-howto/ata.rst | 1 -
bsp-howto/clock.rst| 1 -
bsp-howto/console.rst | 1 -
bsp-howto/frame_buffer.rst | 1 -
bsp-howto/getentropy.rst
---
book/index_book.rst| 2 +-
bsp-howto/ada95_interrupt.rst | 2 +-
bsp-howto/ata.rst | 2 +-
bsp-howto/clock.rst| 2 +-
bsp-howto/command.rst | 2 +-
bsp-howto/console.r
---
bsp-howto/ada95_interrupt.rst | 3 +--
bsp-howto/ata.rst | 3 +--
bsp-howto/clock.rst| 3 +--
bsp-howto/console.rst | 3 +--
bsp-howto/frame_buffer.rst | 3 +--
bsp-howto
I'm OK with this proposal. We used to include quite messy details about
how to bootstrap your own GCC in the user manual. This is a bit nicer. ;)
At the maturity of RSB now, merging the doco with the User Manual is
sensible.
On Wed, Jan 9, 2019 at 5:55 AM Sebastian Huber <
sebastian.hu...@embedde
Thanks, I'll check them out. Hope RTEMs participates this year too! :)
On Wed, Jan 9, 2019 at 8:31 PM Shashvat Jain
wrote:
> Hi Ravindra
> This link has a list of open projects
> https://devel.rtems.org/wiki/Developer/OpenProjects
> you can always ask the developers about projects on this list .
Hi
I think the subject covers it.
../../../../../../rtems/c/src/../../testsuites/psxtests/psxstat/test.c: In
function 'stat_a_file_helper':
../../../../../../rtems/c/src/../../testsuites/psxtests/psxstat/test.c:243:14:
warning: format '%lx' expects argument of type 'long unsigned int', but
argume
On 9/1/19 7:24 pm, Sebastian Huber wrote:
> The usage of a build date prevents reproducible builds.
Sorry to revisit this change. I have reviewed the generated the docs and they
look good and the changes are welcome, thank you. I would like to ask a few
questions.
1. Can the hash be the short ver
On 10/1/19 2:14 am, Sebastian Huber wrote:
> -.. COMMENT: COPYRIGHT (c) 1988-2008.
> -.. COMMENT: On-Line Applications Research Corporation (OAR).
> +.. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
Can this be added without being a comment? I could not find 'Copyright'
On 10/1/19 2:14 am, Sebastian Huber wrote:
> -.. comment SPDX-License-Identifier: CC-BY-SA-4.0
> +.. SPDX-License-Identifier: CC-BY-SA-4.0
Hmm, I must be missing something here with the handling of directives.
What does sphinx-build show if you can -v to the build via the waf configure
options?
On 10/1/19 3:41 am, Gedare Bloom wrote:
> I'm OK with this proposal. We used to include quite messy details about how
> to
> bootstrap your own GCC in the user manual. This is a bit nicer. ;) At the
> maturity of RSB now, merging the doco with the User Manual is sensible.
Agreed, this is sensibl
Hi
Many BSPs have recently run into linking issues for a few tests. For
example, the following BSPs no longer link sp71.exe.
arm-lm3s3749
arm-lm3s6965
arm-lm4f120
arm-lpc1768_mbed_ahb_ram_eth
arm-lpc1768_mbed_ahb_ram
arm-lpc1768_mbed
arm-lpc2362
arm-lpc23xx_tli800
arm-lpc32xx_mzx_stage_1
arm-stm3
Hi,
I am currently using RTEMS to access a DMA core on the Zynq and am noticing
some interesting/peculiar behavior:
When I provide my DMA engine a statically allocated buffer what I notice is
that the first few bytes (5) of the buffer, after getting it back from the DMA,
remain unchanged how
On 10/1/19 2:28 pm, Misra, Avinash wrote:
>
> I am currently using RTEMS to access a DMA core on the Zynq and am noticing
> some
> interesting/peculiar behavior:
>
> When I provide my DMA engine a statically allocated buffer what I notice is
> that
> the first few bytes (5) of the buffer, after
On 10/01/2019 00:49, Chris Johns wrote:
On 10/1/19 2:14 am, Sebastian Huber wrote:
-.. comment SPDX-License-Identifier: CC-BY-SA-4.0
+.. SPDX-License-Identifier: CC-BY-SA-4.0
Hmm, I must be missing something here with the handling of directives.
What does sphinx-build show if you can -v to the
On 10/01/2019 01:39, Joel Sherrill wrote:
Hi
Many BSPs have recently run into linking issues for a few tests. For
example, the following BSPs no longer link sp71.exe.
arm-lm3s3749
arm-lm3s6965
arm-lm4f120
arm-lpc1768_mbed_ahb_ram_eth
arm-lpc1768_mbed_ahb_ram
arm-lpc1768_mbed
arm-lpc2362
arm-l
26 matches
Mail list logo