Hey,
On 02/18/15 22:50, Oleg Hahm wrote:
but we don't know which weird
compilers on some esoteric hardware platform might be used for RIOT somewhere
sometime, so I rather rely on optimized C code than on optimized compilers.
this keeps popping up as an excuse not to do some elegant, readable,
Hello Oleg,
Le 18/02/2015 23:16, Oleg Hahm a écrit :
Hi Kévin!
I began to use function pointers in the 'radio_driver.h' when trying to
create a unified model for radio drivers. I guess it went over later to the
whole netdev effort.
Yes, I remember that, but why can't this be implemented in
On Feb 18, 2015, at 1:42 PM 2/18/15, Thomas Eichinger
thomas.eichin...@fu-berlin.de wrote:
Hi Ralph,
a short update:
I spent most of today’s afternoon to set up toolchain and additional tools
again which
didn’t left much time for testing.
Thanks a lot for looking into the problem...
Hi Kaspar,
sorry for the silence!
As you pointed out in your email, there are scenarios where the
approach will not help due to technical reasons (and using a weird
compiler might have technical reasons as well). You may consider these
as irrelevant. But there is one aspect for sure in
PS: Sorry, you are Joakim not Joachim :-)
Am 20.02.2015 um 08:51 schrieb Peter Kietzmann:
Hi Joachim,
I think it will be the at86rf231-driver (in near future).
@thomaseichinger is currently working on the refactoring according to
the network restructuring. There is still no PR but as far as
I answered my own question by a little searching on the wiki - according to
github.com/RIOT-OS/RIOT/wiki/Board%3A-Samr21-xpro I should use GNU Tools for
ARM Embedded Processors toolchain.
On Feb 19, 2015, at 9:52 PM 2/19/15, Ralph Droms (rdroms) rdr...@cisco.com
wrote:
What's the
Dear RIOT developers,
- Which radio driver is the most up to date with regards to the
network stack restructuring work being done in #2278?
- How stable is the radio device API currently? Are there any more
API changes coming?
- Would it be wise to wait until the restructuring todo list is
Hi Kaspar!
On 02/18/15 22:50, Oleg Hahm wrote:
but we don't know which weird
compilers on some esoteric hardware platform might be used for RIOT somewhere
sometime, so I rather rely on optimized C code than on optimized compilers.
this keeps popping up as an excuse not to do some elegant,
Hi Joachim,
I think it will be the at86rf231-driver (in near future).
@thomaseichinger is currently working on the refactoring according to
the network restructuring. There is still no PR but as far as I know the
progress is well. I think it's wise to wait at least until this driver
is
What's the recommended toolchain for the SAMR21-XPRO board?
- Ralph
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel
10 matches
Mail list logo
