Re: Current state of RISC-V BSP

2017-08-08 Thread Hesham Almatary
Hi Denis, That's good to know. You might want to try running other samples now that are not low-memory and see if they work. Cheers, Hesham On Tue, Aug 8, 2017 at 7:51 PM, Denis Obrezkov wrote: > 2017-08-07 0:49 GMT+02:00 Denis Obrezkov : >> >>

[PATCH 3/4] 4.12/gcc-4.8.3 Fix building with a newer version of gcc.

2017-08-08 Thread Chris Johns
Updates #2990. --- .../tools/rtems-gcc-4.8.3-newlib-2.5.0.20170623-1.cfg | 14 ++ 1 file changed, 14 insertions(+) diff --git a/rtems/config/tools/rtems-gcc-4.8.3-newlib-2.5.0.20170623-1.cfg b/rtems/config/tools/rtems-gcc-4.8.3-newlib-2.5.0.20170623-1.cfg index ff82df0..5ec7eea

[PATCH 4/4] 4.12/lm32: Fix building on Windows.

2017-08-08 Thread Chris Johns
This patch fixes building the LM32 GDB on Windows. Closes #3030. --- rtems/config/4.12/rtems-lm32.bset | 7 +++ 1 file changed, 7 insertions(+) diff --git a/rtems/config/4.12/rtems-lm32.bset b/rtems/config/4.12/rtems-lm32.bset index 54850e3..3508d79 100644 ---

[PATCH 1/4] sb: Fix long path support in copy_tree and removeall path support.

2017-08-08 Thread Chris Johns
The change lets the LM32 target build on Windows which has temporary install paths greater than the Win32 API max size. The buildroot path compression is still needed as the GNU assembler does not like paths that exceed the max Windows limit. Closes #2992. --- source-builder/sb/path.py | 99

[PATCH 2/4] gcc: Disable makeinfo cause newer versions do not build gcc-4.8 docs.

2017-08-08 Thread Chris Johns
Newer makeinfo tools cannot build the existing texinfo in gcc so disable building it. This will not be fixed on the gcc branch. Updates #3027. --- rtems/config/tools/rtems-gcc-4.8-newlib-2.2.0-1.cfg | 2 ++ source-builder/config/gcc-common-1.cfg | 1 + 2 files changed, 3

Re: Current state of RISC-V BSP

2017-08-08 Thread Denis Obrezkov
2017-08-07 0:49 GMT+02:00 Denis Obrezkov : > 2017-08-07 0:44 GMT+02:00 Hesham Almatary : > >> Hi Denis, >> >> Thanks for sharing the state of HiFive1 BSP. At this stage of GSoC, we >> would want you to clean-up the code, write