Hello,
I added a basic RISC-V 32-bit tool chain to the RSB. It is based on the
latest Newlib snapshot and GCC 7.2. The GDB is not included. I guess for
this we have to update to GDB 8.0. I didn't test this tool chain.
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Pu
Denis,
Please confirm if this works for you.
On Tue, Aug 22, 2017 at 9:17 AM, Sebastian Huber
wrote:
> Hello,
>
> I added a basic RISC-V 32-bit tool chain to the RSB. It is based on the
> latest Newlib snapshot and GCC 7.2. The GDB is not included. I guess for
> this we have to update to GDB 8.0
Ok, I will try today
2017-08-22 16:44 GMT+02:00 Gedare Bloom :
> Denis,
>
> Please confirm if this works for you.
>
> On Tue, Aug 22, 2017 at 9:17 AM, Sebastian Huber
> wrote:
> > Hello,
> >
> > I added a basic RISC-V 32-bit tool chain to the RSB. It is based on the
> > latest Newlib snapshot an
On 17/08/17 15:17, Gedare Bloom wrote:
To our C-library experts: What would be the right way of handling this?
It is best to bring it in to newlib. It can temporarily come into the
libbsd if needed, but a note should be made to port it to newlib.
Yes, this should move to Newlib.
--
Sebasti
On Tue, Aug 22, 2017 at 10:49 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 17/08/17 15:17, Gedare Bloom wrote:
>
> To our C-library experts: What would be the right way of handling this?
>>>
>>> It is best to bring it in to newlib. It can temporarily come into the
>> libbs
---
testsuites/psxtests/Makefile.am| 6 ++
testsuites/psxtests/configure.ac | 6 ++
testsuites/psxtests/psxinttypes01/Makefile.am | 22 ++
testsuites/psxtests/psxinttypes01/init.c | 58 ++
.../psxtests/psxinttypes01/psxinttypes
Ok, I fixed it.
2017-08-22 3:48 GMT+02:00 Gedare Bloom :
> On Mon, Aug 21, 2017 at 7:56 PM, Denis Obrezkov
> wrote:
> > ---
> > c/src/lib/libbsp/riscv32/hifive1/include/prci.h | 9 +
> > c/src/lib/libbsp/riscv32/hifive1/start/bspstart.c | 23 +
> > c/src/lib/libbsp/riscv32/hi
Sebastian,
Did you consciously not add riscv do rtems-all.bset? Or was it an
oversight?
Thanks for doing this. I was building on the master of the tools and
I haven't checked gdb for riscv but all targets did build.
--joel
On Tue, Aug 22, 2017 at 9:55 AM, Denis Obrezkov
wrote:
> Ok, I will tr
2017-08-22 22:09 GMT+02:00 Joel Sherrill :
> Sebastian,
>
> Did you consciously not add riscv do rtems-all.bset? Or was it an
> oversight?
>
> Thanks for doing this. I was building on the master of the tools and
> I haven't checked gdb for riscv but all targets did build.
>
> --joel
>
> On Tue, Au
On Tue, Aug 22, 2017 at 4:25 PM, Denis Obrezkov
wrote:
> 2017-08-22 22:09 GMT+02:00 Joel Sherrill :
>
>> Sebastian,
>>
>> Did you consciously not add riscv do rtems-all.bset? Or was it an
>> oversight?
>>
>> Thanks for doing this. I was building on the master of the tools and
>> I haven't checked
2017-08-22 23:49 GMT+02:00 Joel Sherrill :
>
>
> On Tue, Aug 22, 2017 at 4:25 PM, Denis Obrezkov
> wrote:
>
>> 2017-08-22 22:09 GMT+02:00 Joel Sherrill :
>>
>>> Sebastian,
>>>
>>> Did you consciously not add riscv do rtems-all.bset? Or was it an
>>> oversight?
>>>
>>> Thanks for doing this. I was
2017-08-23 0:02 GMT+02:00 Denis Obrezkov :
> 2017-08-22 23:49 GMT+02:00 Joel Sherrill :
>
>>
>>
>> On Tue, Aug 22, 2017 at 4:25 PM, Denis Obrezkov
>> wrote:
>>
>>> 2017-08-22 22:09 GMT+02:00 Joel Sherrill :
>>>
Sebastian,
Did you consciously not add riscv do rtems-all.bset? Or was
I would guess that's the case:
$ cd rtems
[joel@localhost rtems]$ find . -name "_kernel*.h"
./cpukit/libcsupport/include/machine/_kernel_time.h
./cpukit/libcsupport/include/machine/_kernel_types.h
./cpukit/libcsupport/include/machine/_kernel_cpuset.h
./cpukit/libcsupport/include/machine/_kernel_pa
2017-08-23 0:58 GMT+02:00 Joel Sherrill :
> I would guess that's the case:
>
> $ cd rtems
> [joel@localhost rtems]$ find . -name "_kernel*.h"
> ./cpukit/libcsupport/include/machine/_kernel_time.h
> ./cpukit/libcsupport/include/machine/_kernel_types.h
> ./cpukit/libcsupport/include/machine/_kernel_
Definitely looks like that tree is out of date a bit.
Looks like Heshams's tree needs to be rebased. Even better would
be merging it to rtems.org if it is ready now. :)
--joel
On Tue, Aug 22, 2017 at 6:01 PM, Denis Obrezkov
wrote:
> 2017-08-23 0:58 GMT+02:00 Joel Sherrill :
>
>> I would guess
I propose Hesham to rebase his tree so I can rebase my tree against his one
and send a pull request till the end of GSoC.
2017-08-23 1:07 GMT+02:00 Joel Sherrill :
> Definitely looks like that tree is out of date a bit.
>
> Looks like Heshams's tree needs to be rebased. Even better would
> be mer
On Tue, Aug 22, 2017 at 9:56 AM, Denis Obrezkov wrote:
> ---
> c/src/lib/libbsp/riscv32/hifive1/include/irq.h | 12 +++
> c/src/lib/libbsp/riscv32/hifive1/irq/irq.c | 86
> ++
> c/src/lib/libbsp/riscv32/hifive1/start/start.S | 3 +-
> .../score/cpu/riscv32/rt
If that is the 2-paragraph BSD, then it is the newly preferred license.
The RTEMS GPLv2 has an exception which allows linking and eliminates the
viral characteristic. In practice and intent, the two licenses are the same
but the 2-paragraph BSD is simpler and better recognized for our intent.
Tha
Hi all,
I am reporting my efforts on this thread:
* RSB/master/vanilla: riscv32 tested and builds just fine with no
changes from my side.
* RTEMS/riscv32: priv-1.10 branch - rebased with rtems/master, fixed
errors, and pushed to GitHub [1].
* RTEMS/Spike: BSP builds sample tests and tested hello/
On 23/08/2017 11:34, Hesham Almatary wrote:
> Hi all,
>
> I am reporting my efforts on this thread:
>
> * RSB/master/vanilla: riscv32 tested and builds just fine with no
> changes from my side.
Hesham, can you please update rtems-all.bset to add RISC-V? The change is OK'ed
by me so please just p
On 23/08/17 04:16, Chris Johns wrote:
On 23/08/2017 11:34, Hesham Almatary wrote:
Hi all,
I am reporting my efforts on this thread:
* RSB/master/vanilla: riscv32 tested and builds just fine with no
changes from my side.
Hesham, can you please update rtems-all.bset to add RISC-V? The change i
21 matches
Mail list logo
