[riot-devel] Crypto Provider
Hi, I am a student at FU Berlin. I joined a seminar where we want to build a crypto provider for RIOT. We are still at the beginning and want to know, if there are some decision about how we should implement it or if someone startet to do this. Best regards, Sandra Kostic ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT Vs Iotivity, AllJoyn, Thread
Hi Gustavo, Hi Ivan, ok I see. thanks for your answers. That's too bad. It would have been great to gather OIC/OCF people in the same room with W3C, IETF and OpenThread people (who are attending the RIOT Summit) to discuss various IoT network stack approaches, and various IoT open source software approaches. Pitching Intel's approach to IoT in this context would also have been a good occasion, in the opinion of many among us. If there's anything we can do to help you or someone else from your community attend/present, let us know. Else, maybe next time. Cheers, Emmanuel On Mon, Jun 6, 2016 at 11:26 PM, Gustavo Lima Chaves < gustavo.lima.cha...@intel.com> wrote: > Hi, > > > Sorry, I was under the assumption that this had been settled in private > > conversations already, but now I see that's not the case (and the person > > involved is not even copied). > > > > Soletta has an implementation of OIC, the protocol that IoTivity > > implements, but there's nothing about AllJoyn or Thread. > > > > I'm in no position to talk about anything now, so I have to decline the > > invitation, but maybe some of the others listed that have been more > > involved with Soletta and OIC can respond. > > > > On Mon, 06 Jun 2016 22:40:34 +0200, Baptiste Clenet wrote: > > > Could some of you answer please? > > > Thanks > > > > > > Baptiste > > > > > > 2016-05-31 17:30 GMT+02:00 Thiago Macieira >: > > > > > > > Hello Baptiste, Emmanuel > > > > > > > > I'll let the people more familiar (in cc) with it reply. > > > > > > > > On terça-feira, 31 de maio de 2016 16:05:22 BRT Emmanuel Baccelli > wrote: > > > > > Hi Thiago, > > > > > basically, we are interested in learning more about it. > > > > > And in particular, we were wondering whether it could be a good > idea to > > > > > present this at the RIOT Summit [1]. > > > > > What do you think about this idea? > > > > > Best, > > > > > Emmanuel > > Oh, sorry, I was also in the private thread (was going to respond > soon, but now let's do it here). I have to say that I'm not very > comfortable to do a skype-based presentation. Given that the changes > of getting funds to travel to the summit are vague now, maybe I'll > have to decline as well, unfortunately. > > [...] > > > > > > Hi! > > > > > > > > > > On Mon, May 30, 2016 at 09:16:17AM +0200, Baptiste Clenet > wrote: > > > > > > - Iotivity would be great in RIOT, Soletta project [1] > imported it > > > > > > for > > > > > > RIOT, I haven't tried it but it seems to work. I think Riot > should > > > > > > > > > > have an > > > > > > > > > > > implementation of Iotivity directly in its repo (package) > so it > > > > will > > > > > > > > > > be > > > > > > > > > > > better maintain. > > If all of OIC/OCF is to be supported, that's quite a bit of code and > using Soletta is a much simpler path. > > -- > Gustavo Lima Chaves > Intel - Open Source Technology Center > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] UDP datagram sending
Hi, > can you elaborate on how it "doesn't work"? After the message is sent, the reading thread doesn't receive it. I have been watching what is going on in "gnrc_netapi_dispatch" function. The destination pid is correct and there wasn't a problem with message sending. Destination PID is 6 which is the udp thread (I put there a printf statement indicating any incoming message). I finally resolved the problem yesterday's night. I was certain about it, but now I repeated a couple of tests and I don't know why it is working properly... The UDP thread's priority equals 5, the same priority has my sending thread. After I lowered my thread's priority to be lesser than udp's (lets say 6) all began to work properly. Today I retried the test and all seems to work no matter what my thread priority is. So maybe there was another bug in my code. Sorry to bother you. But I have two more things that puzzles me. Why the program is aborting as a result of memory access violation after my thread has been: 1) Initialized with flag THREAD_CREATE_WOUT_YIELD 2) Has lower or the same priority as main thread from which it was created. The platform I am running my program on is native (Linux). ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Regarding RNDIS support
Hello. On 06/06/16 16:12, Johann Fischer wrote: Hello Stefan, Am 06.06.2016 um 14:39 schrieb Stefan Schmidt: I am working on usb device support for RIOT. There is a PR[1] for it, but it is outdated and will be rebased/updated with [2]. [2] supports kinetis and sam[r,d]-21. The CDC-ACM and CDC-ECM support is very anstable and WIP. Currently I am working on the stability of CDC-ACM. I plan: - remove CDC-ECM first - add a netdev2-802154-over-usb interface and opposite driver for linux kernel Could you elaborate on this part? I'm not sure I understand what your plan is here. If your plan is to expose 15.4 level API over USB and write a matching Linux Kernel driver that fits into linux-wpan at least Alexander and myself would be interested in your plans. :) That's exactly what I planned. Nice :) For the beginning we can take the netdev2 for it. If we (someday) have a proper MAC in RIOT, then it may be a better way to use it with linux hardmac interface and to build a 15.4 dongle based on RIOT. We currently have even the hardware for it [1] and a SAM-R21 Xplaned board can also be used as the dongle. Unfortunately, I have some ugly bugs in CDC-ACM code and the code needs clean up, when it is fixed i will update [2]. I will keep an eye on it. Just subscribed to the notifications. regards Stefan Schmidt ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] UDP datagram sending
Hi Mateusz, can you elaborate on how it "doesn't work"? I mean a small description of what's happening / until which point things work as expected / what happens next... How do you think the thread number of main is related to your problem? This IPC call: gnrc_netapi_dispatch_send(GNRC_NETTYPE_UDP, GNRC_NETREG_DEMUX_CTX_ALL, ip); should send a message to the appropriate (UDP-)thread, no matter from which thread it has been sent. That's why I assume your problem might be something else. Best regards Peter Am 06.06.2016 um 12:00 schrieb Mateusz Kubaszek: Hi :) I am writing an UDP module for sending and receiving datagrams with ACKs. It is based on udp and pktdump example. I have a certain problem with datagram sending from my custom thread. Using shell module the datagrams are prepared as pktsnip and then sent by calling "gnrc_netapi_dispatch_send(GNRC_NETTYPE_UDP, GNRC_NETREG_DEMUX_CTX_ALL, ip);". The thread number is 2 which indicates the main thread. Up to this point everything seems to work fine. When I'm doing the same thing using my custom thread it doesn't work. Why is it so? Best regards, Mateusz Kubaszek ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel -- Peter Kietzmann Hamburg University of Applied Sciences Dept. Informatik, Internet Technologies Group Berliner Tor 7, 20099 Hamburg, Germany Fon: +49-40-42875-8426 Web: http://www.haw-hamburg.de/inet ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
