Am 03.03.2016 21:02 schrieb "Kaspar Schleiser" :
>
> Hey,
>
> On 03/03/2016 07:03 PM, Cenk Gündogan wrote:
> > should we just wait until we
> > hit the next great invention (Kaspar (; ) ?
>
> it's nearly ready...
>
> Kaspar
The KasparCI will be ready soon ;)
Oops, did not remember that one. Thanks Hauke!
Emmanuel
On Mar 4, 2016 08:49, "Hauke Petersen" wrote:
> Hi,
>
> this is not quite true, I have started to work on this some time ago [1],
> but don't quite remember were I left of. But maybe this branch might give
> you
Hi,
this is not quite true, I have started to work on this some time ago
[1], but don't quite remember were I left of. But maybe this branch
might give you a head start? Feel free to copy what you need!
Cheers,
Hauke
[1] https://github.com/haukepetersen/RIOT/tree/add_board_stm32f7discovery
Hello Bernhard,
AFAIK autoinit module is enabled by default, just check if you have defined
-DMODULE_AT86RF2XX, -DMODULE_AUTO_INIT_GNRC_NETIF and
-DMODULE_AUTO_INIT_GNRC_NETIF while compiling.
Im not using default toolchain based on Makefiles so Im not that familiar
with it...
wbr
malo
On 3
Hi everyone,
I am interested in using RTOS with an STM32F746NG Discovery (a board
with an ARM Cortex M7), but it doesn't seem to be supported yet. Does
anyone know if someone started working on this ?
Here is a link to the board I'm talking about :
Hello everybody,
today I tried to find out how I can set an IPv6 address for the network
interface.
In all examples and readme's you can read how to show the settings for
the network
interface, but I can't find any example how an IP address is set for a
given interface.
I tried several styles
Hi Antoine,
As far as I know, no one has started porting to this board, or to any other
Cortex M7-based board yet.
However, it would be great to have support for this Discovery board (and
initial M7 support).
Are you interested/willing to start porting?
The community usually turns out to be
Hi Bernhard,
I thik the printf is just wrong. It should be
DEBUG("Initializing AT86RF2xx radio at SPI_%i\n", p->spi);
The SPI bus itself is stored in the parameter descriptor in
at86rf2xx_params.h which is either provided by the board (if it is shipped
with the device) or the application
Hello everybody,
I have seen in the auto_init_at86rf2xx.c file a loop which tries to find
valid devices.
The loop-counter is used for discovering spi-busses and also for the
device descriptor ("i" in the code).
I think this is not a good idea because what happens if you have only
ONE device
Have you looked at CircleCI?
This seems to be the rage for IETF repos at this point.
(ISTR I couldn't get it to work for my repos, but I probably just didn't
try hard enough.)
Grüße, Carsten
___
devel mailing list
devel@riot-os.org
Hello Cenk,
I have found the "ifconfig help" but nevertheless I was doing something
wrong.
Why not giving just a simple example? I have worked with ifconfig a long
time
under Linux but not with IPv6.
"ifconfig ..add" worked well - as expected.
Best,
Bernhard
Hello developers,
what is the best way to find out that a given core-frequency isn't
sufficient for carrying 6LoWPAN protocol? I guess if the cpu-frequency
is too low it just won't work no hint from the OS side - is this true?
Best regards,
Bernhard
Dear hard-working Developers,
I just wanted to share with you the chart in [1]
with the caption "Active Linux Builds for Open Source Projects (GCE)"
All our current jobs are build on that infrastructure and looking at the
chart:
travis is pretty flat-lining. It seems that there are more jobs
Hey,
On 03/03/2016 07:03 PM, Cenk Gündogan wrote:
> should we just wait until we
> hit the next great invention (Kaspar (; ) ?
it's nearly ready...
Kaspar
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
14 matches
Mail list logo