[riot-devel] RIOT-OS Stammtisch in der c-base

-Party und Code-Review-Come-Togethers nennen. Ein bis zwei Mitentwickler und ich würden uns dann am Samstag beim nächsten circle-Treffen vorstellen wollen. Mit freundlichen Grüßen, Martine Lenders [1] riot-os.org ___ devel mailing list devel@riot-os.org

Re: [riot-devel] RIOT-OS Stammtisch in der c-base

Am 30. Oktober 2014 13:35 schrieb Martine Lenders mlend...@inf.fu-berlin.de : Hallo, wir, die Entwickler vom freien Betriebssystem RIOT [1] für embedded systems, würden gerne (zukünftig) regelmäßig (zunächst aber erstmal einmalig) unsere sogenannten Hack'n'ACK-Partys in der c-base

Re: [riot-devel] RIOT-OS Stammtisch in der c-base

Hi, 2014-10-30 14:04 GMT+01:00 Emmanuel Baccelli emmanuel.bacce...@inria.fr: Thanks Martine. Who is available to accompany Martine Saturday at 8PM at C-Base? Hauke already agreed to accompany, but a third person would be nice, I guess :-) (I will try to attend myself, but I cannot confirm

Re: [riot-devel] Regular Hack'n'ACK meetings at c-base, Berlin

Hi, this is a reminder to attend the poll regarding regular Hack'n'ACKs at c-base [1]. I plan to contact the orga team at c-base on sunday. Cheers, Martine [1] https://dudle.inf.tu-dresden.de/riot-hacknack-regular-dow/ 2014-11-01 23:08 GMT+01:00 Martine Lenders mlend...@inf.fu-berlin.de: Hi

Re: [riot-devel] Refectoring the network stack

Sorry for the many errors in grammar and spelling (and the missing complimentary close). Accidentaly hit the send button before reading through the mail again… Kind regards, Martine 2014-11-05 18:15 GMT+01:00 Martine Lenders mlend...@inf.fu-berlin.de: Hi, as discussed on the virtual meeting

Re: [riot-devel] Refectoring the network stack

at the moment or I'd take a look for myself (really, it probably has a bit more to do with my being hungover and slightly lazy this morning). Currently use the already existing TSCH implentation OpenWSN. So that's where it is hiding ;) Cheers, Martine --adam On Nov 5, 2014 9:15 AM, Martine Lenders mlend

Re: [riot-devel] Refectoring the network stack

Hi Adam, 2014-11-07 11:38 GMT+01:00 Adam Hunt voxa...@gmail.com: Will this refactoring effort allow for multiple interfaces on a single RIOT device? Yes this (and easier more modularity through less coherence = easier testing) is the main reason for the refactoring. What about bringing

Re: [riot-devel] FIB redesign

, Martine Lenders wrote: Hi Martin, 2014-11-14 15:23 GMT+01:00 Martin martin.landsm...@haw-hamburg.de: Hi Martine, I will change the interface and protocol IDs to `kernel_type_t` as you suggested. For the FIB handling perspective this seems also to be the best (and easiest) way to have

Re: [riot-devel] Dedicated RIOT Testing Meeting

Hi, Sorry I couldn't attend. Will there be minutes? Cheers, Martine Am 19.11.2014 12:58 schrieb Oleg Hahm oliver.h...@inria.fr: Here goes the PlaceCame link: http://placecam.de/call.php?c=VBYEpXi43MZ2MOrV~pegsMm6Z7woUbw.VRY0Qxal2pE- Am Tue, Nov 11, 2014 at 09:13:23PM +0100 schrieb Philipp

Re: [riot-devel] Switch to BSD?

Hi, 2014-12-03 22:59 GMT+01:00 Emmanuel Baccelli emmanuel.bacce...@inria.fr: […] But in the first place, we would like to debate this topic. In particular: is anyone violently opposing the idea of migrating to a less restrictive license, such as BSD? If so, why? On the other hand, if you

Re: [riot-devel] RIOT on Arduino UNO

Hi, 2014-12-21 21:13 GMT+01:00 eric fleury eric.fle...@inria.fr: Eric Fleury, Professor DANTE INRIA TEAM ENS LYON Tel: +33 672 162974 On 21 déc. 2014, at 20:15, Sudarshan S sudarshans.riot@gmail.com wrote: […] I would like to understand the following: 1) I believe there are ways

Re: [riot-devel] Example Application for testing microcoap in RIOT?

Hi Hasan, can you open a Pull Request on GitHub, so we can review and discuss your port there? 2014-12-22 10:41 GMT+01:00 Islam Hasan hasan.is...@aalto.fi: Hi, I have included microcoap as an external pkg in RIOT OS, but getting some frustrating warnings from RIOT as the followings:

Re: [riot-devel] New IPC API status

Hi 2015-01-24 9:49 GMT+01:00 Adam Hunt voxa...@gmail.com: If memory serves there were a number of potential features that were on the back burner until RIOT's new IPC API was finalized (e.g. filesystem/VFS, and maybe ELF loading). Just for clarification: FS would just be simplified by

Re: [riot-devel] git howto for a correct pulls

Hi Jan, 2015-02-04 21:18 GMT+01:00 Jan Wagner m...@jwagner.eu: why i am always feeling stupid using git... hub... in my naive way of thinking git clone https://u...@bitbucket.org/user/repo.git me -- if sync needed git remote add upstream https://github.com/RIOT-OS/riot.git git fetch

Re: [riot-devel] git howto for a correct pulls

Hi, 2015-02-04 21:55 GMT+01:00 Jan Wagner m...@jwagner.eu: and dont get me worng - i did some pulls requests already - I think I did a misstake by deleting my github fork: https://github.com/RIOT-OS/RIOT/pull/2387 https://github.com/RIOT-OS/RIOT/pull/2312 problem here I deleted the

Re: [riot-devel] Network Stack Task Force

Hello Martin, 2015-02-06 9:02 GMT+01:00 Martin martin.landsm...@haw-hamburg.de: thx again for recording the audio for the introducing presentation. It was a great help to get a more descend look at the information from the slides and the idea for the message based network stack approach.

Re: [riot-devel] Memory Management

Hi Raphael, for the native-stuff you have to ask Ludwig for the specifics as to of why, but most of the hosts system's implementation of standard functions are wrapped. I think this was because our POSIX interface would otherwise colide with the system's POSIX interface. As for the other boards

Re: [riot-devel] Network Stack Task Force

Hi, 2015-01-16 20:04 GMT+01:00 Oleg Hahm oliver.h...@inria.fr: Hey! For the workshop I propose January 27-28, but its just a proposal... Keep in mind, that the next HA is scheduled for January 27. Of course I did not. :-) But I think thats a perfect fit! I'm not so convinced about

Re: [riot-devel] [i...@meetup.com: Invitation: Internet of Things Meetup 12 – Intel Edison]

Hi, 2015-01-30 20:56 GMT+01:00 Christian Mehlis christ...@m3hlis.de: Am 29.01.2015 um 14:02 schrieb Thomas Eichinger: See you there! Me 2 Christian Made a note to my calendar, too. :-) ___ devel mailing list devel@riot-os.org

Re: [riot-devel] Network Stack Task Force

not a good idea, I agree. Thanks Martine for the doodle, let's wait until Thursday and decide on the dates based on the outcome of the doodle then. Cheers, Hauke On 19.01.2015 13:17, Martine Lenders wrote: Hi, Since this thread has gained some traction now I would propose to use

Re: [riot-devel] Network refactoring

Hello Baptiste, since I was mostly in charge of the refactoring last year and we want to split up this task this year a little bit, I'm currently in the process of compiling such a TODO list/progress report. Hope I have something to show end of the week. Best, Martine 2015-01-05 9:50 GMT+01:00

Re: [riot-devel] Network refactoring

Hi, Am 05.01.2015 18:06 schrieb Ludwig Ortmann ludwig.ortm...@fu-berlin.de: Hi, On Mon, Jan 05, 2015 at 06:00:34PM +0100, Oleg Hahm wrote: Maybe we can discuss a tentative schedule and set some milestones for the refactoring during a (PlaceCam) conf call this week? What do you think? How

Re: [riot-devel] Reference Radio-driver Implementation

Hello Jonas, truth is we are currently somewhat in a transition phase. We want the new netdev interface and have in place as soon as possible, but there are still modules and applications that use the old transceiver interface. Moreover, the cc2420 is older than the netdev API and was just adapted

Re: [riot-devel] microcoap app

Hi, I don't know how much expertise Martin has on the microcoap application, but I tried to compile it against current master and it worked. Did you try a `make distclean` before `make`? Sometimes the checkout points for the pkg repositories get a little deprecated. Cheers, Martine 2015-03-16

Re: [riot-devel] ESP8266 - Easy tcp/ip support

Hello David, 2015-03-17 0:02 GMT+01:00 David Lyon david.l...@clixx.io: Hello Ludwig, Lately, I've been putting a lot of time into the ESP8266 wifi modules, and learning how to get them to work. How is the unified network driver system going? Here's my conclusion on the ESP8266. If Riot

Re: [riot-devel] Radio duty cycling

Hello Joakim, currently there are no specific plans to utilize the power modes of the radios to my knowledge, except that mostly MAC/link layers will implement it. So if you have any idea: feel free to speak about it. Cheers, Martine 2015-03-17 10:05 GMT+01:00 Joakim Gebart

[riot-devel] New Event: Hack'n'ACK @ Monthly from 5pm to 10pm on the last Tuesday (RIOT Events)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST X-GOOGLE-CALID:k3ql8setv7l48ofnol0tfuu...@group.calendar.google.com BEGIN:VTIMEZONE TZID:Europe/Berlin X-LIC-LOCATION:Europe/Berlin BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200

Re: [riot-devel] CSMA MAC-layer, Open Issues

Hi Jonas, 2015-03-20 18:02 GMT+01:00 Jonas Remmert j.remm...@phytec.de: Hi, […] 2. The drivers send function builds the IEEE 802.15.4 MAC header on its own. The alternative would be to let the MAC layer do this job. This would avoid code duplication and make it easier to implement new

[riot-devel] Galileo-Board

Hi, there is a second person now asking for support for the Galileo board. Though there is a Wiki page I did not find any source files for this board. I can't remember: Do we support the board or was the development aborted do to the complications René encountered. If the latter one is the case,

[riot-devel] Updated Invitation: Biweekly virtual meeting @ Wed Mar 25, 2015 2pm - 3pm (RIOT Events)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST X-GOOGLE-CALID:k3ql8setv7l48ofnol0tfuu...@group.calendar.google.com BEGIN:VTIMEZONE TZID:Europe/Berlin X-LIC-LOCATION:Europe/Berlin BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200

Re: [riot-devel] Build issue on Windows (8.1)

Hi Oleg, Hi Murat, Oleg, maybe it is a good idea if we download the images into the Wiki's repository and link them from there? Cheers, Martine 2015-04-01 13:39 GMT+02:00 Oleg Hahm oliver.h...@inria.fr: Hi Murat! I did not see any issue about picture. I have re-added same picture(address)

Re: [riot-devel] Notification: Hack'n'ACK @ Tue Mar 31, 2015 5pm - 10pm (RIOT Events)

Events *Who* • Martine Lenders - creator Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account peterschme...@gmail.com because you are subscribed for notifications on calendar RIOT Events. To stop receiving these emails, please log

Re: [riot-devel] replace printf, puts issue

+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 ludwig.ortm...@fu-berlin.de: Hi Jozef, AFAIK there has been no work on a solution so far. However, I thought about

Re: [riot-devel] Changing the workflow.

Hi, 2015-02-21 20:06 GMT+01:00 Ludwig Ortmann ludwig.ortm...@fu-berlin.de: Hi, On Sat, Feb 21, 2015 at 07:02:58PM +0100, Martine Lenders wrote: This is why I propose we change to a slightly adapted topic branch workflow (also known as feature branch) workflow [1]: - the main RIOT

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

Hi Tara, have you tried to include your external library as an external module [1]? Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/wiki/Creating-external-modules 2015-02-24 15:19 GMT+01:00 Tararaina Klipffel tei...@gmail.com: Hello, We are 4 French students in engineering school.

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

Martine Lenders authmille...@gmail.com: Hi Tara, have you tried to include your external library as an external module [1]? Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/wiki/Creating-external-modules 2015-02-24 15:19 GMT+01:00 Tararaina Klipffel tei...@gmail.com: Hello

Re: [riot-devel] [PROJECT][RIOT-OS][STM32-L152RE]

Hi again 2015-02-24 20:16 GMT+01:00 Martine Lenders authmille...@gmail.com: […] 2 things: Have you added the Makefile.base to the directory YOUR_PATH/RIOT-master/examples/test? Sorry I meant the Makefile, not the Makefile.base here. ___ devel

Re: [riot-devel] LGPL compliance testing

Hi Murat, You made the PR to your own repository. You have to open a Pull Request to our repository. Hope I could help, Martine 2015-02-26 16:56 GMT+01:00 Murat CAKMAK m...@muratcakmak.net: Hi Ludwig, Pull request link : https://github.com/cakmakmurat2000/RIOT/pull/1 It is my first GIT

[riot-devel] Changing the workflow.

Hello coding RIOTers, After I needed to rebase several PRs multiple times last week I'm really fed up with our current workflow. Furthermore, I discovered three things that show that we are in need of a more established workflow. 1. our community is growing 2. our master branch is changing

[riot-devel] IEEE 802.15.4 addressing

Hi, now that we start to get in IEEE 802.15.4/6LoWPAN territory with netdev/netapi [1-3] I wonder if it makes sense to not have 2 (16-bit/64-bit) but 3 addressing modes: * 16-bit short address * 32-bit (16-bit PAN ID + 16-bit short address) as originally introduced to RIOT, but somehow ignored

Re: [riot-devel] MIPS platform (PIC32)

Hi, 2015-01-14 0:10 GMT+01:00 Adam Hunt voxa...@gmail.com: […] Aside from those you should take a look at the Porting Guide https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide on the wiki if you haven't already. You might also find the API documentation http://riot-os.org/api/ useful. Beyond

Re: [riot-devel] new network stack mini howto

Hey Kaspar, Just take the current ng_icmpv6/feat/initial branch in my repo (PR'ed in #2555) + your favorite device driver. Start your device in a nomac thread (look into tests/driver_xbee for how to do it) and add ng_icmpv6_echo, ng_netbase and ng_nomac to your application's modules. Currently you

[riot-devel] Fwd: [Seminarorga:] RIOT Hack'n'ACK Mai

-base.org, mlend...@inf.fu-berlin.de Hallo Martine, Am 22/04/15 um 14:38 schrieb Martine Lenders: ich wollte kurz nachfragen, ob wir den Seminarraum wieder nächste Di nutzen können, da wir nicht im Kalender eingetragen sind. ich hab nochmal nachgeschaut. Ihr habt den Raum auf jeden Fall

[riot-devel] RIOT Hack'n'ACK Mai

Hallo, ich wollte kurz nachfragen, ob wir den Seminarraum wieder nächste Di nutzen können, da wir nicht im Kalender eingetragen sind. Viele Grüße, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] NSTF - Naming the stack

Hi, I'm not in favor of keeping the prefix. Three reasons: 1. https://github.com/RIOT-OS/RIOT/pull/2731#discussion_r27350056 2. I'm really looking forward to the day when I don't need to prepend the ng_ prefix anymore 3. Angie sounds to me like a political statement ;-) In all seriousness: I

Re: [riot-devel] Network API task force

Hi Kaspar, just to state the opposite opinion, too: while I see the need for an API suitable for embedded use only and other stacks than the default one too, I'm of the opinion, that the POSIX sockets (needed for library and application ports) should also be as slim as possible. This means: A

Re: [riot-devel] Network API task force

Hi Kaspar, 2015-05-08 11:09 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hi, On 05/08/15 10:58, Martine Lenders wrote: just to state the opposite opinion, too: while I see the need for an API suitable for embedded use only and other stacks than the default one too, I'm

Re: [riot-devel] Network API task force

Hi, 2015-05-08 11:25 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hi, On 05/08/15 11:14, Martine Lenders wrote: Actually, yes. But I'm still trying to get my head around why netapi (or it's wrapper functions [1], slightly renamed) could not be that API. Because it requires the use

Re: [riot-devel] Network API task force

Hi Kaspar, 2015-05-08 11:32 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hey, On 05/08/15 11:29, Martine Lenders wrote: On 05/08/15 11:14, Martine Lenders wrote: Actually, yes. But I'm still trying to get my head around why netapi (or it's wrapper functions [1], slightly renamed

Re: [riot-devel] NSTF - Naming the stack

Hey, what about `ipc_stack` due to its utilization of the former? But still: I'm still not convinced of the reason to give it a name. All operating systems have a default stack but no one is bound to use it and can use their `ultra` stack etc. (in Linux e.g. as a library). The naming of uIP is

Re: [riot-devel] NSTF - Naming the stack

Hi, given that I was asked today what the R means in RIOT (and Thomas W. giving the most excellent to my revelutionary or restricted: RIOT) I really like gnrc. Let's find some alternative meanings for that! :D Generic newly retained code? Great networking! RIOT certified? Google never really

Re: [riot-devel] Testing Task Force

Hi, there were ~40 new builds opened yesterday [1] and it takes travis ~30 min to finish a build (and since we are in the fair-use queue it works of the jobs more or less sequentially), so thats why the later ones are pending. I think we can speed up things a little if everyone (who has rights to

Re: [riot-devel] Testing Task Force

Hi Oleg, 2015-04-16 9:36 GMT+02:00 Oleg Hahm oliver.h...@inria.fr: Hi! there were ~40 new builds opened yesterday [1] Sorry for the maybe stupid question, but how do zou see this? I find the Travis UI pretty confusing (and slow). The date the build opened you sadly can't see, but I

Re: [riot-devel] Task force ping

Hi Kaspar, The organizational issue [1] for the NSTF gives a good overview I think. At least I try to keep it current from the overview I have. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/issues/2278 2015-04-09 8:44 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hey guys, trying a

Re: [riot-devel] new network stack mini howto

Hi, 2015-04-12 11:33 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hey Martine, thanks a lot, that was what I was looking for! On 04/11/15 22:31, Martine Lenders wrote: Just take the current ng_icmpv6/feat/initial branch in my repo (PR'ed in #2555) + your favorite device driver. Start

Re: [riot-devel] Network Stack diagram

Hey Baptiste, I don't know how useful they are for your context, but I drew up some (preliminary) activity diagrams for my parts (IPv6 and 6LoWPAN) [1]. Cheers, Martine [1] https://www.dropbox.com/sh/rn750v8r8ezszqw/AABKpegFODterMuE6X4g0kQSa?dl=0 2015-04-17 13:22 GMT+02:00 Baptiste Clenet

Re: [riot-devel] Notification: Biweekly virtual meeting @ Every 2 weeks from 10am to 11am on Wednesday (RIOT Events)

Hi, in general I prefer 2pm, but tomorrow I'm not able to attend at this time. Cheers, Martine Am 07.04.2015 10:08 schrieb Oleg Hahm oliver.h...@inria.fr: Hi, anyone opposed to permanently rescheduling this call to 2pm CEST? Cheers, Oleg On Tue, Apr 07, 2015 at 08:00:13AM +, Google

[riot-devel] Black-box testing of ng_netapi modules

Hi, since two days ago we have a module to black-box test ng_netapi modules: ng_nettest. I've PR'd tests for UDP as an example for that [1] (there are still some issues) and wrote a wiki page on how to write tests [2]. Please consider testing the other ng_netapi modules with that. Cheers, Martine

Re: [riot-devel] Open Processes Task Force

Hi, Just to be clear, we are talking about administrative processes on our work in RIOT here, right? Not some kind of system processes. Because that's what I was thinking first Manu's mail was about and I had a really hard time wrapping my head around it. Cheers, Martine Am 28.05.2015 00:09

[riot-devel] Neighbor Discovery finalized for now

Dear routing RIOTers, with PR #3049 I'm happy to announce that I finally finished my work on vanilla IPv6 neighbor discovery. Please test it extensive. Things still missing is the Redirect Function [2] which I see as optional for now (because it is not really needed for LoWPANs) and the 6LoWPAN

[riot-devel] Where's the iot-lab_M3 gone?

Hello renaming IoTlers, First of all, sorry about cross-posting, but I think that could interest both lists. if you try to build with BOARD=iot-lab_M3 you will discover, that it is not possible: *** The specified board iot-lab_M3 does not exist.. Stop. This is because we just renamed it to

[riot-devel] GNRC is one module now

Dear relentless IOTlers, Yesterday we finally got rid of the `ng_` prefix by moving all GNRC-related modules into the new `gnrc` module (see PR #3645 [1]). The structure is now as follows: * `ng_netbase` is now the `gnrc` module (and is not a pseudo-module anymore, but still pulls in the same

Re: [riot-devel] RIOT examples

Hey, 2015-08-19 14:47 GMT+02:00 Kaspar Schleiser kas...@schleiser.de: Hey, On 08/14/15 14:54, Oleg Hahm wrote: But maybe we can even live with one examples directory holding all examples, as that makes finding them very easy. I think I would also prefer a flat hierarchy and keep it

Re: [riot-devel] Pull request procedure

Hi, +1 for your guideline (though I really need to put some work into point s 1 and 3 ^^). On the somewhat-positive-feedback-side for the maintainers and reviewers in general: If I saw and remember correctly we, brought the number of open PRs of ~170 in the last few weeks finally down to ~140

Re: [riot-devel] Pull request procedure

Hi Cenk, 2015-08-20 21:18 GMT+02:00 Cenk Gündogan cenk.guendo...@fu-berlin.de: Hi Oleg, Out of curiosity (and maybe to state the obvious): The rules you proposed would forbid WIP pull requests, right? How did you come to this implication? If one marks a PR as WIP (either by label because

[riot-devel] SourceForge Maintenance

Hi, SourceForge is currently partly shut down for maintenance [1] so brace yourself for failing `tests/coap` builds on Travis. Regards, Martine [1] https://twitter.com/sfnet_ops/status/622236074052464641 ___ devel mailing list devel@riot-os.org

Re: [riot-devel] CoAP

Hi, as libcoap uses POSIX sockets it should work without any porting effort to gnrc. But since the socket API does not support options at the moment, there might be some unexpected problems. Cheers, Martine 2015-10-29 15:32 GMT+01:00 Baptiste Clenet : > Hi Lennart, > >

[riot-devel] Hack'n'ACK October '15

Hello fellow RIOTers, Cenk and I are holding the castle for tonight's Hack'n'ACK at FU Berlin. You can join via your favorite PlaceCam link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- If you never used PlaceCam before, please refer to [1] Lots of fun and merges

Re: [riot-devel] Network Stack Question

Hi Haoyang, 2015-10-23 20:08 GMT+02:00 Haoyang Yu : > >- txtsnd: I cannot set the interface, if I use tap0, which will echo: >error: invalid interface given. > > You need to use the interface on the node, not the TAP. The TAP is the endpoint on the host system

Re: [riot-devel] Network Stack Question

Hi Haoyang, 2015-10-24 21:17 GMT+02:00 Haoyang Yu : > >1. where can I find the txtsnd source codes? > > `txtsnd` is a default shell command for the `gnrc_netif` module pulled in by the `shell_commands` module. As such you can find it in

Re: [riot-devel] The border router wi^H^H is ready!

Hi Ralph, we use a very simple SLIP implementation over its second UART. Regards, Martine 2015-09-17 19:27 GMT+02:00 Ralph Droms (rdroms) : > Congratulations! > > How do you use a samr21-xpro as a border router? What's the second > interface? > > - Ralph > > > On Sep 17,

[riot-devel] Hack'n'Ack September '15 edition

Hello everybody, You can join today's Hack'n'Ack via the usual PlaceCam link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- If you never used PlaceCam before, please refer to [1] Have fun tonight, Martine [1]

Re: [riot-devel] Fwd: tapsetup problem

Hi, make sure you have the `netdev2_tap` module included to your project. You can do that by either adding the line USEMODULE += netdev2_tap to your project or - more generally for all boards, not just native USEMODULE += gnrc_netif_default If you want the OS to setup the device

Re: [riot-devel] RIOT Release 2015.09

\o/ finally! /goes to bed Am 05.10.2015 22:17 schrieb "Oleg Hahm" : > Dear RIOT developers and users, > > it has been a long and rocky road, but thanks to the marvellous community, > we > managed to finalize the fifth official release of the RIOT operating > system: >

Re: [riot-devel] Ubuntu to Riot Communication

Hi, 2015-11-24 17:49 GMT+01:00 Oleg Hahm : > […] > > Also I have some issue with pyterm the node. After successfully "make > flash" > > > > I can not access the node via pyterm: > > sudo pyterm -p "/dev/ttyACM0" > > > Any idea? The debug light flash as the same frequency

Re: [riot-devel] Arduino API merged

Lol I need coffee. Cheers, Martine 2015-11-27 14:10 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>: > You just did :-) > > Cheers, > Hauke > > > On 27.11.2015 14:03, Martine Lenders wrote: > > Hi, > the Arduino API wrapper [1] was fin

Re: [riot-devel] module documentation

t; I use module only for gnrc_netif_default, it seems include the 6LoWPAN > module too? > > Thanks! > Haoyang > > On Nov 18, 2015, at 01:18, Martine Lenders <authmille...@gmail.com> wrote: > > Hello Haoyang, > gnrc_netif_default is a pseudo-module, defined in Makefile.pse

Re: [riot-devel] Task Forces

Yes to both. 2015-11-19 17:54 GMT+01:00 Hauke Petersen : > > > On 19.11.2015 16:50, Emmanuel Baccelli wrote: > > OK, I could go ahead and modify the wiki with some tentative text for > that, which we could refine later on. > In practice: > > - would Kaspar agree he

Re: [riot-devel] module documentation

gnrc_netif, right? And add packet header I defined by myself. > > Thanks for your answers. > > Cheers, > Haoyang > > > On Nov 17, 2015, at 10:05, Oleg Hahm <oliver.h...@inria.fr> wrote: > > > > Hi! > > > > One tiny addition: > > > > Am Tu

Re: [riot-devel] MAC Layer Implementation in RIOT

he features provided by the device. Hope this made things clearer for you. Best regards, Martine Lenders [1] https://github.com/RIOT-OS/RIOT/pull/3730 [2] https://github.com/RIOT-OS/RIOT/pull/4180 [3] https://github.com/RIOT-OS/RIOT/pull/4184 [4] https://github.com/RIOT-OS/RIOT/pull/4213 [5] https://openws

Re: [riot-devel] RIOT Vs Iotivity, AllJoyn, Thread

Hi, 2016-06-08 20:29 GMT+02:00 Iván Briano : > On Wed, 08 Jun 2016 19:58:50 +0200, Baptiste Clenet wrote: > > 2016-06-08 17:14 GMT+02:00 Emmanuel Baccelli >: > > > > > Hi Ivan, > > > it would be great to have it as a pkg indeed! > > > That's

[riot-devel] API CHANGE: msg_t now carries void pointers

Hello revising IOTlers, another day another API change: After some discussion in [1] we decided to unify the typing of pointers of unspecified type. The first fall-out from that discussion was the changing of the pointer of the `content.ptr` field of `msg_t`. It is now `void *` instead of `char

Re: [riot-devel] API CHANGE: msg_t now carries void pointers

Hi again, sorry, forgot to quote the PR that changed it: [2]. Cheers, Martine [2] https://github.com/RIOT-OS/RIOT/pull/5498 2016-06-03 14:02 GMT+02:00 Martine Lenders <authmille...@gmail.com>: > Hello revising IOTlers, > > another day another API change: After some discussion in

Re: [riot-devel] arduino-uno support

Hi Laurent, don't want to discourage you, but you do not have to update on this mailing list for every step you do. Just the major ones are enough ;-). Those of us interested (as for example me) will most likely follow your PR anyways. BTW: when you write your wiki page on the board can you add a

[riot-devel] API change in netdev2

Hi, quick note to all network device driver and MAC protocol developers: The API of netdev2 was changed slightly [1] in that the event_callback now doesn't expect a `void *` argument anymore. This argument has proven to be superfluous, since the data was always stored in the `netdev2_t` struct

Re: [riot-devel] Notification: Hack'n'ACK @ Tue May 31, 2016 5pm - 10pm (RIOT Events)

Hi, we finally managed to set-up here in Berlin. If you like to join via PlaceCam [1] feel free to do so at http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation

Re: [riot-devel] Problem with UDP and SAMR21-XPRO

Hi Mattia, hi Alex, due to having my head mostly on the defense of my master thesis I have next monday I wasn't able to look into this as promised. :( Thanks however Mattia for the in-depth analysis and the bisect! As soon as I find some head space I will look into it, too. Cheers, Martine

Re: [riot-devel] RIOT, Windows, and Code Composer Studio

Hey Clark, that sounds something like the path to your make installation isn't set in the environment variable PATH. I know from the past, that you can set them somewhere in the system config, but I haven't used Windows in years and when I did I had it in German, so don't ask me were exactly (in

Re: [riot-devel] Hack'N'ACK, January 2016

the Hack'n'ACK. > > In general, I also think that there is room for optimization regarding > the way we deal with Hack'n'ACKs currently and I like your proposal so far. > > Best, > Cenk > > > On 18.01.2016 15:12, Martine Lenders wrote: > > Hi, > just a kind reminder that n

[riot-devel] Hack'N'ACK, January 2016

Hi, just a kind reminder that next week it is Hack'n'ACK time again and (on the time I write this Mail) we have 213 (!) open Pull Requests. I already discussed locally here in Berlin with some colleagues, how we can maybe optimize the Hack'n'ACK to get more Pull Requests merged or closed this

Re: [riot-devel] Contiki as a RIOT thread

Hi, Just on the subject on uIP: I'm currently working on an emb6 port (in parallel to the lwIP port), which is a proto-thread-less fork of uIP. But as discussed in [1] and by the advantages you have given additionally, it would definitely make sense to run Contiki in RIOT. Cheers, Martine Am

Re: [riot-devel] IoT

Hi Doni, A lot of what you asked for can be found in our documentation [1]. For an introduction of how to use an existing application you can read [2]. To create an application there is this page [3] and to create a module (a new functionality for RIOT), there is also information on this [4]. If

Re: [riot-devel] Odd problems with xtimer

Hi, normally you can guess where the timer came from by looking at the address (or the debugger straight tells you). Is this somehow possible for your case (i.e. 0x200010a4)? That might be helpful for the timer people. Regards, Martine 2016-02-10 23:08 GMT+01:00 Michael Andersen

Re: [riot-devel] RIOT TCP Stack

Hello Sam, You are right GNRC replaced the old stack (which was also developed as a UDP stack first), since the old one was very buggy and not really manageable. The TCP component is currently under development by Simon Brunner at [1]. Since it is developed as part of a thesis which IIRC

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

Hi Bernhard, there was an update to the netdev2 API [1]. Please rebase and adapt your driver accordingly (4646 is adapted too already). Best, Martine [1] https://github.com/RIOT-OS/RIOT/pull/4648 2016-02-24 12:36 GMT+01:00 Bernhard Nägele : > Hello everyone, > I

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

Hi Bernhard, that's not what I said: cc11xx is the only *radio* in master. Since netdev2 was introduced around the time we introduced Ethernet, there are also several Ethernet devices (netdev2_tap, enc28j60, encx24j600) that support the netdev2 interface. Our IEEE 802.15.4 radios work with the

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

Hi, what radio is the nrf24l01p using? The only radio in master currently implementing netdev2 is the cc11xx driver (all others are either Ethernet drivers or not merged yet). As stated before: there is a move to port the IEEE 802.15.4 devices (which are currently implementing the older

Re: [riot-devel] Hack'N'ACK, January 2016

Hi, Kind reminder to all to use the weekend (or Monday and Tuesday) to prepare the PRs for the Hack'n'ACK. Cheers, Martine 2016-01-18 16:01 GMT+01:00 Martine Lenders <authmille...@gmail.com>: > Hi Cenk, > > I also want to add and stress that we should make proper use of &g

Re: [riot-devel] Hack'n'ACK tonight

Hi, I think we did a great job tonight. We met our target to get under 200 pretty precise. Here's a little tally: * 44 PRs were updated (either discussed, pushed to, merged or closed): * 16 PRs were closed (of this 10 were merged) * 2 PRs were created Of course before the Hack'n'ACK

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

Hi Bernhard, Have you seen [1] and [2]? Let us know if they are lacking any information you need. Since the MRF24J40 is an IEEE 802.15.4 radio I think it's best to look into my PR 4646 [3], which ports the at86rf2xx driver (currently based on gnrc_netdev in master) to the stack agnostic netdev2.

  1   2   3   4   >