[riot-devel] Fwd: 64bit and multi core support

Alex Mavrin alexeymavrin at gmail.com
Fri May 8 20:16:22 CEST 2015

Hi Ludwig, Nhat,

Thanks a lot for your answers! It is much clearer now. We will estimate how
difficult it would be to adopt RIOT to our use case.

It is very attractive that RIOT is modular, supports C++ and aims to POSIX

I just wanted to thank you all again.



On Thu, May 7, 2015 at 9:53 PM, Ludwig Ortmann <ludwig.ortmann at fu-berlin.de>

> Hi Alex,
> RIOT does not offer either.
> When I first wrote the native platform, I tried to support 64 bit but
> there were so many issues that I just chose to ignore it as there were no
> 64 bit platforms on the roadmap anyways.
> Since then two things changed:
> First, much work has gone into making integer types more explicit. Second,
> the native platform is relatively stable and offers valgrind support, so I
> think it could be used to make RIOT 64 bit safe relatively quickly.
> As for the scheduler - I'm not aware of any attempts at multicore support,
> but RIOT is very modular, so the scheduler could be changed/replaced with
> little trouble.
> Cheers,
> Ludwig
> Am 7. Mai 2015 20:33:41 MESZ, schrieb Alex Mavrin <alexeymavrin at gmail.com
> >:
> >Dear RIOT team,
> >
> >
> >Thanks for RIOT I personally think it is GREAT!
> >
> >We are considering using RIOT on our ARM v8 64bit multicore (SMP)
> >hardware.
> >The platform requires 64bit memory addressing (DDR is at higher than
> >32bit
> >address range). We would appreciate if you could help us understand if
> >using RIOT is feasible by answering below questions:
> >
> >   1. Does RIOT support 64bit memory addressing? For example if I build
> >“hello-world” sample project on native platform then 32bit binary
> >generated. Is it possible to build it for 64bit? Have this been tested?
> >
> >
> >  2. Does RIOT support multi core? I.e. scheduling threads on different
> >cores, synchronizing threads running on different cores? Have this been
> >done before?
> >
> >
> >Best Regards,
> >
> >
> >Alex

Alex Mavrin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20150508/918ac9bf/attachment.html>

More information about the devel mailing list