The way I envision it is as a starting point for RIOT, a base. Once the project
is integrated, then we can make changes to it as we see fit. Is that an
accurate picture or is it more a case of utilizing the project and handling
changes to that project that affect RIOT as they occur on Wakaama in
Hi David,
when using Wakaama (which is certainly an option), the way would be to
include it in RIOT as a package and include some Makefiles that are able
to download/checkout the library and build it into RIOT. When choosing
this path, one important thing is to think of a concept for continuou
Hi Joakim,
as of today, I PRed a new version of the Xbee S1 radio driver[1], which
is build 100% on the new netdev interface. I think it makes a good
reference implementation for radio drivers, even if it is through it's
UART interface a little different from others drivers we are supporting..
I am almost certainly planning on using the Wakaama project(formerly liblwM2M)
for this project. A possibly silly question but, would a final port of this
implementation look similar to the various ports under RIOT/pkg/ or is it more
involved than that? I am just trying to get a picture of what
Hi Jonas,
On 20.03.2015 18:02, Jonas Remmert wrote:
1. Both, the upper layer and the current implementations of the
ng_netdev radio drivers use task messages to signalize an event
(Packet to be sent or Packet to receive waiting). Both message
mechanisms send their messages to the mac_pid and
Hi Kausthub,
with a clean hardware abstraction the BLE implementation should be
mostly independent of hardware. For the small hardware dependent part we
propose the NRF51822 SoC (as it is broadly available and cheap), that is
correct. But as a basic driver for the SoC's radio is already availa
Hi!
Okay, I removed it from the organization on Github. To be on the safe side I
just moved it to my personal repos.
Cheers,
Oleg
--
printk(KERN_DEBUG "%s: Flex. T...\n", DRV_NAME);
linux-2.6.6/drivers/net/wan/dscc4.c
pgpPOJlgt5sAT.pgp
Description: PGP signature
___
Hi!
At least for IoTivity it should be fairly simple to port it to RIOT according
to the response I got on their mailing list:
http://lists.iotivity.org/pipermail/iotivity-dev/2015-March/000600.html
The only problem I see is the incompatible license of their implementation.
(Btw. the Contiki por
