Hi,
On Mon, Feb 16, 2015 at 06:41:05PM +0100, Oleg Hahm wrote:
> > the minutes from the meeting have been added to our wiki:
> > https://github.com/RIOT-OS/RIOT/wiki/minutes-OTA-meetup-13.2.2015
>
> Have there any concrete next steps been identified? Did you conclude in some
> kind of a schedule
Dear relentless RIOTers,
I would like to introduce an official repository for keeping Dockerfiles
used for building Docker images. The images can be used to build RIOT in
conjunction with the work being proposed in [1]. The images will contain
supported versions of tool chains to make getting start
Hi,
fine with me, thank you for the initiative =)
Cheers,
Ludwig
On Sun, Feb 22, 2015 at 11:54:16AM +0100, Joakim Gebart wrote:
> Dear relentless RIOTers,
> I would like to introduce an official repository for keeping Dockerfiles
> used for building Docker images. The images can be used to build
Hi,
Could you please give me information about actual state of "replace printf and
puts" issues? https://github.com/RIOT-OS/RIOT/issues/994,
https://github.com/RIOT-OS/RIOT/issues/641
I’m working with MKL02Z32 which has 4kB RAM. Printf or puts which are almost
everywhere make a big problem. I
Hi Jozef,
AFAIK there has been no work on a solution so far.
However, I thought about this the other day in the context of the function
pointer discussion and would like to propose a "logging" API (maybe there is an
issue for that as well somewhere) for `core`, which offers things like
`log.inf
+1 thought about this for a long time, too. Though my approach would be
with macros and more global (similar to how DEBUG is now).
Am 23.02.2015 07:16 schrieb "Ludwig Ortmann" :
>
> Hi Jozef,
>
> AFAIK there has been no work on a solution so far.
> However, I thought about this the other day in th
