[PATCH] common: Show page references after internal links

The custom RTEMS extension produced quite verbose references like "Chapter 3 - Section 7 - Bla blub". This may distract the reading flow. Use a standard Sphinx option to show page references instead, e.g. "Bla blub (page 11)". This has some value for printed out documents. --- common/conf.py

Re: [PATCH v2] rtems-record: New program

Hello Chris, sorry for the rush, but what do you think of this patch? I would like to integrate the tracing work of the GSoC project and this patch is a blocking point. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 F

Re: RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

Hello Chris, the patch just changed GCC 9.1 to 9.2 on all targets which use GCC 9, these are or1k, riscv, and x86_64. Since there will be probably no RTEMS 5 in the near future, maybe we should move to GCC 9.2 in general. If we do this on PowerPC, then the SPE is no longer supported. On AR

RTEMS 5 gcc-fb371a33fa6 vs gcc-9.2.0

Hi, I am not sure what the difference between these versions of gcc are? The hash based version is the default while 9.2.0 is used on or1k, riscv, and x86_64. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/de

Re: [PATCH] RTEMS BSP Buildset

On 13/8/19 2:46 am, Jonathan Brandmeyer wrote: > On Mon, Aug 12, 2019 at 12:10 AM Chris Johns wrote: > If it boots via a device tree, then the RTEMS BSP should do this as well. > > Current generation petalinux generates a device tree for Linux. > Hmm. How would you integrate the

Re: Chapter/section numbers in document internal references

On 13/8/19 12:06 am, Sebastian Huber wrote: > On 08/08/2019 08:52, Sebastian Huber wrote: >> On 06/08/2019 10:23, Sebastian Huber wrote: >>> >>> >>> On 06/08/2019 10:05, Chris Johns wrote: On 6/8/19 4:36 pm, Sebastian Huber wrote: > Hello, > > when you use document internal referen

Re: rtems-tester with griscv

On Mon, Aug 12, 2019 at 4:23 PM Jiri Gaisler wrote: > You should probably use --rtems-bsp=griscv-sis . The griscv bsp uses the > (now deleted) built-in sis in gdb... > Thanks. That seems to have worked. --joel > I am preparing a patch to purge the stale tester bsps ... > > Jiri. > On 8/12/

Re: rtems-tester with griscv

You should probably use --rtems-bsp=griscv-sis . The griscv bsp uses the (now deleted) built-in sis in gdb... I am preparing a patch to purge the stale tester bsps ... Jiri. On 8/12/19 8:22 PM, Joel Sherrill wrote: > Hi > > Running riscv-rtems5-sis by hand, hello.exe runs. But when I try it wit

rtems-tester with griscv

Hi Running riscv-rtems5-sis by hand, hello.exe runs. But when I try it with rtems-tester, nothign passes and the tester hangs. I killed python after about 30 minutes of CPU time. + /home/joel/rtems-work/rtems-tools//tester/rtems-test --rtems-tools=/home/joel/rtems-work/tools/5 --rtems-bsp=griscv

Re: GSoC 2019: POSIX Compliance - FENV Environment probably not working properly in RISCV

Can you post or email me privately the full patch? I can try to see what I spot. Can you check with objdump or gdb that the methods which don't appear to work are actually the RISC-V implementation? Look at the disassembly and see if it looks like you expect. Does this require a patch to newlib a

Re: [PATCH] RTEMS BSP Buildset

On Mon, Aug 12, 2019 at 12:10 AM Chris Johns wrote: > >>> If it boots via a device tree, then the RTEMS BSP should do this as well. Current generation petalinux generates a device tree for Linux. > >> > >> How would you integrate the Xilinx tools to handle this, ie ps7_init and > >> friends? I

Re: Chapter/section numbers in document internal references

On 08/08/2019 08:52, Sebastian Huber wrote: On 06/08/2019 10:23, Sebastian Huber wrote: On 06/08/2019 10:05, Chris Johns wrote: On 6/8/19 4:36 pm, Sebastian Huber wrote: Hello, when you use document internal references, e.g. :ref:`RSB` then this is turned into: "Chapter 12 - RTEMS Source

[PATCH] user: Update bug reporting section

Include information from https://devel.rtems.org/wiki/NewTicket --- user/support/bugs.rst | 32 +++- 1 file changed, 23 insertions(+), 9 deletions(-) diff --git a/user/support/bugs.rst b/user/support/bugs.rst index 290f317..14c47dd 100644 --- a/user/support/bugs.rst +

Re: GSoC Project | Basic Support for Trace Compass

Documentation patch review is pending: https://lists.rtems.org/pipermail/devel/2019-August/027215.html > -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) , Dhanbad

Re: GSoC Project | Basic Support for Trace Compass

> > > What's the procedure for getting code merged? Do I have to raise PR on > > GitHub or simply send a patch on devel? > > First we have to integrate the initial support for the rtems-record > program: > > https://lists.rtems.org/pipermail/devel/2019-August/027278.html > > Then you can rebase you

Re: GSoC Project | Basic Support for Trace Compass

On 12/08/2019 12:27, Ravindra Kumar Meena wrote: This is too complicated: +    strcpy( filename, "event_" );       snprintf( file_index, sizeof( file_index ), "%ld", i );       strcat( filename, file_index ); In addition, the strcpy() and strcat() functions are dangerous t

Re: GSoC Project | Basic Support for Trace Compass

> > This is too complicated: > > +strcpy( filename, "event_" ); > snprintf( file_index, sizeof( file_index ), "%ld", i ); > strcat( filename, file_index ); > > In addition, the strcpy() and strcat() functions are dangerous to use. > Why don't you simply use: > > snprintf( filename,

Re: Not able to run riscv-rv32imac testsuites

Okay. Thanks On Mon, Aug 12, 2019 at 3:00 PM Hesham Almatary < hesham.almat...@cl.cam.ac.uk> wrote: > On Mon, 12 Aug 2019 at 03:55, Vaibhav Gupta > wrote: > > > > > > > > On Mon, Aug 12, 2019, 12:01 AM Hesham Almatary < > hesham.almat...@cl.cam.ac.uk> wrote: > >> > >> > >> > >> On Sun, 11 Aug 20

Re: Not able to run riscv-rv32imac testsuites

On Mon, 12 Aug 2019 at 03:55, Vaibhav Gupta wrote: > > > > On Mon, Aug 12, 2019, 12:01 AM Hesham Almatary > wrote: >> >> >> >> On Sun, 11 Aug 2019 at 16:11, Vaibhav Gupta wrote: >>> >>> But I am not able to run: >>> >>> qemu-system-riscv64 -no-reboot -nographic -machine virt -m 256M -kernel >>

[PATCH v1] Add steps to test Newlib patch.

Update the checksum to be used for the Newlib patches. Earlier it was msd5, but it is depreciated for security reasons. Now RSB accepts sha512. --- user/rsb/project-sets.rst | 41 +-- 1 file changed, 35 insertions(+), 6 deletions(-) diff --git a/user/rsb/projec