[riot-devel] qemu-i386 port

Hi, we now have the third person wondering about the qemu-i386 port. Fact is, it doesn't work (we do not even have the unittests activated anymore). Is there a reason why we did not drop it yet (except making all the good work by René void)? Or are we planning to provide better support for it in th

Re: [riot-devel] qemu-i386 port

ping qemu-i386 >> >>On the same subject, would it make sense to clean up some other boards >>with less than ideal support? >>chronos is one board which I frequently run into trouble with because >>it is never up to date with the other platform implementations, >>e

[riot-devel] conn f2f (+ remote) meeting

Hi all, we finally want to discuss the overhaul of conn next week. The meeting will be held on Wednesday next week (August 17th) at 1pm (UTC+0200). Remote participation will be possible, we'll try to find a tool that everyone is comfortable with. I'll provide you with an agenda for the meeting unt

Re: [riot-devel] conn f2f (+ remote) meeting

Hi, as promised: here is the agenda for the meeting next Wednesday: http://yourpart.eu/p/netapp-api-riot Cheers, Martine 2016-08-11 15:33 GMT+02:00 Martine Lenders : > Hi all, > we finally want to discuss the overhaul of conn next week. The meeting > will be held on Wednesday next wee

Re: [riot-devel] conn f2f (+ remote) meeting

://wiki.mumble.info/wiki/Main_Page 2016-08-15 16:11 GMT+02:00 Martine Lenders : > Hi, > as promised: here is the agenda for the meeting next Wednesday: > http://yourpart.eu/p/netapp-api-riot > > Cheers, > Martine > > 2016-08-11 15:33 GMT+02:00 Martine Lenders : > >&

Re: [riot-devel] conn f2f (+ remote) meeting

;. Regards, Martine 2016-08-16 15:26 GMT+02:00 Peter Kietzmann : > Mi Martine, > > no objections from my side. I would like to join virtually. > > Regards > Peter > > > Am 16.08.2016 um 14:12 schrieb Martine Lenders: > >> Hi, >> are there any objections to ha

Re: [riot-devel] conn f2f (+ remote) meeting

Hi, 2016-08-17 19:28 GMT+02:00 Oleg Hahm : > Hey folks, > > On Mon, Aug 15, 2016 at 04:11:48PM +0200, Martine Lenders wrote: > > as promised: here is the agenda for the meeting next Wednesday: > > http://yourpart.eu/p/netapp-api-riot > > thanks for the protocol, but i

Re: [riot-devel] conn f2f (+ remote) meeting

Hi, I've made a new PR for the sock API: https://github.com/RIOT-OS/RIOT/pull/5758. Ports for stacks and applications will be provided in seperate PRs. Cheers, Martine 2016-08-18 10:41 GMT+02:00 Oleg Hahm : > Thanks a lot! > > On Thu, Aug 18, 2016 at 08:25:50AM +0200, Martine

Re: [riot-devel] Fragmentation support in IP

Hi Adeel, What do you mean by "lost fragment recovery"? To my knowledge there is no such thing in 6LoWPAN fragmentation. Regards, Martine Am 19.08.2016 12:59 vorm. schrieb "Adeel Mohammad Malik" < adeel.mohammad.ma...@ericsson.com>: > Hi again Thomas, > > Do you mean that 6LoWPAN in RIOT does no

Re: [riot-devel] RFC: development procedures

Hi, 2016-08-19 17:25 GMT+02:00 Kaspar Schleiser : > Hey, > > On 08/19/2016 05:15 PM, Oleg Hahm wrote: > > Hence, I would propose to somehow reference the addressed > > comment in the commit message. What do you think? > > That would rule out --fixup commits (and thus automatic rebasing). "git > c

Re: [riot-devel] RFC: development procedures

Hi, Am 19.08.2016 7:51 nachm. schrieb "Kaspar Schleiser" : > > Hey, > > On 08/19/2016 05:54 PM, Martine Lenders wrote: > > Not necessarily. I would put such links to comments in the commit body > > anyway and that is ignored by --autosquash. > > Not nec

Re: [riot-devel] RFC: development procedures

Hi Kaspar, 2016-08-19 22:34 GMT+02:00 Kaspar Schleiser : > Hi, > > On 08/19/2016 08:05 PM, Martine Lenders wrote: > >>> Not necessarily. I would put such links to comments in the commit body > >>> anyway and that is ignored by --autosquash. > >> &

[riot-devel] gprof for non-native boards

Hi, for stack memory optimizations in GNRC I need some kind of tool to analyze the call-path of its threads (the stackusage of each function itself can easily determined using GCC [1]). After some experiments with some static solutions (I basically went through the list here [2]) I wasn't able to c

Re: [riot-devel] gprof for non-native boards

:16:02PM +0200, Martine Lenders wrote: >> for stack memory optimizations in GNRC I need some kind of tool to >> analyze the call-path of its threads (the stackusage of each function >> itself can easily determined using GCC [1]). After some experiments >> with some static s

Re: [riot-devel] BorderRouter: Global IPV6 address lost in ncache after UDP message sent

Hi, can you check if this is https://github.com/RIOT-OS/RIOT/issues/5467? > Why or how can a node be removed from ncache? Why the node does not automatically reconnect with BR? As the implementer of the neighbor discovery I can say this: because the neighbor discovery is sh** ;-). It was written

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

dar/event?action=VIEW&eid=bGJrNG1mdWNxZG9tY2Y3YzhvOWNnNGNtc2dfMjAxNjA4MzBUMTUwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn> > Hack'n'ACK > > *When* > Tue Aug 30, 2016 5pm – 10pm Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://maps.google.com/maps?q=FU+Berlin;+HAW+Hamburg&hl=en>) > > *Cal

Re: [riot-devel] BorderRouter: Global IPV6 address lost in ncache after UDP message sent

tation? > > Cheers, > > 2016-08-29 19:56 GMT+02:00 Martine Lenders : >> Hi, >> can you check if this is https://github.com/RIOT-OS/RIOT/issues/5467? >> >>> Why or how can a node be removed from ncache? Why the node does not >> automatically reconnect with B

Re: [riot-devel] BorderRouter: Global IPV6 address lost in ncache after UDP message sent

Hi Baptiste, (sorry, hit the send button for the previous mail accidentally to early) 2016-08-30 16:01 GMT+02:00 Baptiste Clenet : > Thanks Martine, > The issue you mentioned seems to be different. Okay, could you report that issue to the tracker then please so I don't lose track of it. > Did y

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

Hi Oleg, 2016-08-30 16:14 GMT+02:00 Oleg Hahm : > I'm still in Dagstuhl the whole week. I know :-). Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] arduino-uno support

gt; boards/arduino-uno and boards/arduino-duemilanove. > > Should I push -f on original PR [1] ? > Or it is cleaner to close [1] and open a new PR ? > > Regards, > Laurent > > [1]https://github.com/RIOT-OS/RIOT/pull/5451 > > 2016-05-25 22:31 UTC+02:00, Martine Lenders

[riot-devel] Canceled Event: Biweekly virtual meeting @ Wed Dec 28, 2016 2pm - 3pm (RIOT Events)

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

Re: [riot-devel] Canceled Event: Biweekly virtual meeting @ Wed Dec 28, 2016 2pm - 3pm (RIOT Events)

Oops, sorry. I was cleaning out my calendar and forgot that was connected to the official one... But I guess nobody else wants to meet at that day, too. Best regards, Martine Am 05.09.2016 6:30 nachm. schrieb "Martine Lenders" : > This event has been canceled and removed from

Re: [riot-devel] char* to int and vice versa

Hi, sprintf (and it's siblings) should be avoided in production code though, since in newlib these functions are quite large. I'm not sure if this exist on all platforms, but there is also atoi()'s counterpart itoa(). Cheers, Martine Am 05.09.2016 6:44 nachm. schrieb "Marc" : Try sprintf(a_stri

Re: [riot-devel] Easy ping

Hi Baptiste, have you had a look at the implementation of the ping shell command? Another way would be to (re-)implement ping using conn_ip (or sock if merged). In that case, if you want it relly easy you don't even have to implement ICMPv6 ping but can do whatever you want ;-). Cheers, Martin

Re: [riot-devel] Easy ping

Hi Baptiste, that depends on what you mean by reachable. Even for ICMPv6 ping (which is used with the shell ping command) you need some "server", that handles the request and issues a reply. If that server is not present the node will not reply to pings, even if it is reachable in the sense that yo

Re: [riot-devel] Easy ping

the node is connected. > Sock is in PR so I prefer not to use it for the moment > > 2016-09-23 20:37 GMT+02:00 Martine Lenders : > > Hi Baptiste, > > that depends on what you mean by reachable. Even for ICMPv6 ping (which > is > > used with the shell ping command) y

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

://maps.google.com/maps?q=FU+Berlin;+HAW+Hamburg&hl=en>) > > *Calendar* > RIOT Events > > *Who* > • > Martine Lenders - creator > > Invitation from Google Calendar <https://www.google.com/calendar/> > > You are receiving this email at the account peters

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 5, 2016 2pm - 3pm (RIOT Events)

Dear RIOTers, as the Google Calendar reminds is: tomorrow is our "biweekly" virtual meeting. I started an agenda at [1]. Feel free to add to it if you think something needs to be discussed. Cheers, Martine [1] http://www.yourpart.eu/p/riot-2016-10-05-virtual-meeting 2016-10-04 14:00 GMT+02:00 Go

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 5, 2016 2pm - 3pm (RIOT Events)

t; > http://placecam.de/call.php?c=kWtmE~M0jTbKGFQSGnUBLtC.xAbWgTythbQbBMVXUvs- > > Best > Peter > > Am 04.10.2016 um 14:59 schrieb Martine Lenders: >> Dear RIOTers, >> as the Google Calendar reminds is: tomorrow is our "biweekly" virtual >> meeting. I started an

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 5, 2016 2pm - 3pm (RIOT Events)

Hi, 2016-10-05 15:27 GMT+02:00 Oleg Hahm : > Hi! > > Sorry, couldn't make it, but some comments/questions: > > On Wed, Oct 05, 2016 at 03:16:11PM +0200, Martine Lenders wrote: >>* How to prevent server problems we had at the weekend? >> * downloads.r

Re: [riot-devel] gnrc tcp not working

Hi, what board are you using (we support multiple arduino boards) and what kind of network device are you using to communicate? Also, since gnrc_tcp_srv isn't merged yet: can you try gnrc_networking (if it fits) on master? Cheers, Martine 2016-10-13 13:17 GMT+02:00 Doni Pradana : > I tried on gnr

[riot-devel] Release 2016.10

Dear release-hungry IoTlers, I'm currently in the process of reevaluating the Pull Requests and issues for our autumn release [1]. While I'm doing this, here a few important dates for the release: * Feature Freeze: Monday, Oct 31 (we have a Hackathon at Wikimedia coming up Oct 29 [2], so that's wh

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 19, 2016 2pm - 3pm (RIOT Events)

Hi, I prepared an agenda at [1]. If anyone likes to add to that, please feel free. Apart from that (see first agenda item) I like to propose to move from PlaceCam to Mumble. Apart from some setup problems (which can easily be documented in the Wiki) my experience with Mumble was much more positive

Re: [riot-devel] Release 2016.10

merged during the release but are no new features or platforms. Since both "Known issue" and the "Under review for release" columns are rather large now, I'll to get things a little bit more manageable in the next few days. @maintainers: The project panel is now free to b

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 19, 2016 2pm - 3pm (RIOT Events)

2016-10-18 17:30 GMT+02:00 Martine Lenders : > Hi, > > I prepared an agenda at [1]. If anyone likes to add to that, please feel > free. Apart from that (see first agenda item) I like to propose to move from > PlaceCam to Mumble. Apart from some setup problems (which can easily be >

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 19, 2016 2pm - 3pm (RIOT Events)

Hi, due to the usual problems we changed over to Mumble [1] now. Please join us at Server: riot-labs.de Port: 64738 PW: riot Sorry and cheers, Martine [1] http://wiki.mumble.info/wiki/Main_Page 2016-10-19 13:56 GMT+02:00 Martine Lenders : > Hi, > for this session we will still use Place

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 19, 2016 2pm - 3pm (RIOT Events)

Hi, find attached the cleaned up version of the minutes of the meeting. You can find it also in the Wiki [1]. The live notes can be found in the previously linked etherpad [2]. Cheers, Martine Attendees * Martine (FU Berlin) * Peter (HAW Hamburg) * Cenk (HAW Hamburg)

Re: [riot-devel] openthread and riot - license issues?

Hi Alex, we include openthread's source code as a package so as far as we are concerned (but we are not lawyers) there is no licensing issue. If you know anything different, please let us know! Cheers, Martine 2016-10-22 16:36 GMT+02:00 Alexander Aring : > Hi, > > I currently detect that openthr

Re: [riot-devel] openthread and riot - license issues?

Hi Alex, 2016-10-22 22:49 GMT+02:00 Alexander Aring : > > Hi, > > On 10/22/2016 05:11 PM, Martine Lenders wrote: > > Hi Alex, > > we include openthread's source code as a package so as far as we are > > concerned (but we are not lawyers) there is no licensin

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

ndar/event?action=VIEW&eid=bGJrNG1mdWNxZG9tY2Y3YzhvOWNnNGNtc2dfMjAxNjEwMjVUMTUwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn> > Hack'n'ACK > > *When* > Tue Oct 25, 2016 5pm – 10pm Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://maps.google.com/maps?q=FU+Berlin;+HAW+Hamburg&hl=e

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

Oops, sorry that was a little trigger happy (I just prepared that e-mail). We are not set-up yet. I'll notify you again when we are! Kind Regards, Martine 2016-10-25 16:39 GMT+02:00 Martine Lenders : > Hi, > we are now set-up in Berlin for this month's. If you like to join v

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

Hi, we are now set-up (for real this time ;-)): *http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- <http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc->* Cheers, Martine 2016-10-25 16:40 GMT+02:00 Martine Lenders : > Oops, sorry that was

Re: [riot-devel] Release 2016.10

se also have a look if you can manage to fix those until Monday. Happy hacking! Martine [1] https://github.com/RIOT-OS/RIOT/projects/4 2016-10-18 18:13 GMT+02:00 Martine Lenders : > Good evening, > I finally sifted through all open issues and PRs and evaluated them > for the release [1]

Re: [riot-devel] bitfeilds

Hi, because this discussion came up in one of my (higher level) PRs, too. 2016-10-27 12:33 GMT+02:00 Neil Jones : > are you suggesting the compiler generated code for accessing the bitfeilds > is less size efficient than doing it manually? I would be suprised if that > was the case ? > > On 27 Oc

Re: [riot-devel] bitfeilds

(okay it's not the case for MSP430 e.g.) 2016-10-27 13:35 GMT+02:00 Martine Lenders : > Hi, > because this discussion came up in one of my (higher level) PRs, too. > > 2016-10-27 12:33 GMT+02:00 Neil Jones : > >> are you suggesting the compiler generated code for acc

Re: [riot-devel] bitfeilds

Hi, 2016-10-27 15:01 GMT+02:00 Oleg Hahm : > Hi Martine! > > On Thu, Oct 27, 2016 at 01:35:21PM +0200, Martine Lenders wrote: > > >> As example I was able to save several 100 bytes of ROM when removing > the > > >> named bitfield use from the samr21s periphe

Re: [riot-devel] Release 2016.10 - One more day

Dear release-sprinting IoTlers, the feature freeze is upon us, but there are still 17 PRs open (9 of those non-bugfixes, one is just waiting for Murdock to finish). Because of those 9 I move the feature freeze to tomorrow 5pm (2016-01-01 17:00 +0100). But everything that isn't merged by then will n

Re: [riot-devel] Release 2016.10 - One more day

I meant of course 2016-11-01 17:00 +0100 Am 31.10.2016 7:51 nachm. schrieb "Martine Lenders" : > Dear release-sprinting IoTlers, > the feature freeze is upon us, but there are still 17 PRs open (9 of > those non-bugfixes, one is just waiting for Murdock to finish). > Bec

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Nov 2, 2016 2pm - 3pm (RIOT Events)

Hi, I'm currently deep into release management so can somebody else please take the reins on this one? Cheers, Martine 2016-11-01 14:00 GMT+01:00 Google Calendar : > more details » >

[riot-devel] Release 2016.10 - Feature freeze

Dear releasing IoTlers, we now entered the feature freeze for the upcoming release. I created a release branch [1] and tagged the first release candidate [2]. So please start testing it [3]. Maintainers: Don't forget that there are already 6 open bugfixes [4] (there will be most likely more) so al

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Nov 2, 2016 2pm - 3pm (RIOT Events)

e adds a > point). Elsewise I can open a PlaceCam session, even if I'm busy as well > and would prefer not to have this meeting. > > Best > Peter > > Am 01.11.2016 um 15:04 schrieb Martine Lenders: > > Hi, > > I'm currently deep into release management

Re: [riot-devel] Release 2016.10 - Feature freeze

Hi, with RC2 [1] now open we can start testing again [2]. Happy testing, Martine [1] https://github.com/RIOT-OS/RIOT/releases/tag/2016.10-RC2 [2] https://github.com/RIOT-OS/Release-Specs/issues/29 2016-11-01 17:29 GMT+01:00 Martine Lenders : > Dear releasing IoTlers, > > we now en

Re: [riot-devel] Third party snippets

Hi Jose, the "RIOT way" or rather the GNRC way would be to extend (in the object oriented sense) `gnrc_netdev2_t`, similar how `gnrc_netdev2_ieee80215.c` and `gnrc_netdev2_eth.c` already did. Hope I was able to helpful. Cheers, Martine 2016-11-04 19:11 GMT+01:00 Anon Anonymous : > Hi Jose, > > I

Re: [riot-devel] Fwd: TI-ez430-Chronos

Hi Harshad, I don't have any specific project in mind, but maybe using another device as a cc11xx border router you can use the on-board radio (I might be mistaking so if there is non, sorry for the noise) to sync your watching using our SNTP implementation [1]. Mind that IPv6 over cc11xx is not we

[riot-devel] The state of 2016.10

Hi, as many of you might have noticed: we did not release yesterday. This was due to the fact that many errors were still found. As of the writing of this mail we now have 11 open bugfixes PR'd to master (without any backports yet) and 3 merged bugfixes that still need backporting to the 2016.10-br

[riot-devel] RIOT Release 2016.10

Dear RIOTers, we are happy to announce the ninth official release of the RIOT: --- * RIOT 2016.10 * --- This release provides a lot of new features as well as it fixes several major bugs. Among these new features are the new simplified netw

[riot-devel] GitHub's new features - A release managers assessment

Dear RIOTers, due to me being the release manager for the first release after GitHub rolled out a bunch of new features I came a lot in contact with them. I thought it might be beneficial to share my impressions and opinions about these features and how we could utilize them as the RIOT community

Re: [riot-devel] GitHub's new features - A release managers assessment

Hi Kaspar, 2016-11-11 19:57 GMT+01:00 Kaspar Schleiser : > That sounds interesting. Github will soon deprecate the merge commit > field from PRs, and I always found it somehow flaky that the CI tests > one thing but merges another. This option you're talking about, does it > trigger a hook when a

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

e.com/calendar/event?action=VIEW&eid=bGJrNG1mdWNxZG9tY2Y3YzhvOWNnNGNtc2dfMjAxNjExMjlUMTYwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn> > Hack'n'ACK > > *When* > Tue Nov 29, 2016 5pm – 10pm Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://maps.google.com/maps?q=FU+Berlin;+

Re: [riot-devel] SiLabs Gecko

Hi Akshay, I fear you have to be a bit more specific than that. What application are you using e.g., which network stack? Also, I might be mistaking but it seems like there is no RF support for the EZR32LG in master yet. Maybe that is the problem? Cheers, Martine 2016-12-08 8:34 GMT+01:00 Akshay

[riot-devel] Canceled Event: Hack'n'ACK @ Tue Dec 27, 2016 5pm - 10pm (RIOT Events)

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

Re: [riot-devel] Greetings from the 33c3 and Pointer to an interesting USB talk

Hi, I'll also be there. But I won't make it to a talk that is also interesting for ongoing discussions in the RIOT community: "Wheel of Fortune - Analyzing Embedded OS Random Number Generators" [1]. Streaming is at [2]. [1] https://fahrplan.events.ccc.de/congress/2016/Fahrplan/events/7949.html [2]

[riot-devel] New Event: CANCELLED @ Every 2 weeks from 2pm to 3pm on Wednesday (RIOT Events)

You have been invited to the following event. Title: CANCELLED When: Every 2 weeks from 2pm to 3pm on Wednesday Berlin Calendar: RIOT Events Event details: https://www.google.com/calendar/event?action=VIEW&eid=Z2tqN2ZyY3NmdnEzOWFkbDdmMXJkb2hrbzhAME9tbGdPMEJCWURxU1FId3pVa09nT3BKQVpDR1NncUE2a2tC

[riot-devel] Updated Invitation: Biweekly virtual meeting @ Every 2 weeks from 2pm to 3pm on Wednesday from Wed Apr 8, 2015 to Wed Dec 28, 2016 (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 TZNA

Re: [riot-devel] New Event: CANCELLED @ Every 2 weeks from 2pm to 3pm on Wednesday (RIOT Events)

FYI, we decided yesterday to create a new kind of regular meeting after the release and cancel all further bi-weekly meetings for now, since their attendance was low to begin with. Cheers, Martine 2017-01-10 11:17 GMT+01:00 Martine Lenders : > more details » > <https://www.google.com

Re: [riot-devel] Socket #0

Hi Sam, can you try with PR #6004 which ports POSIX sockets from conn to sock? There are still some kinks in this PR, but I plan to fix them until the release. On another note: the conn implementation of sockets was never tested with TCP (since there was no TCP implementation then), but feel free t

Re: [riot-devel] Socket #0

Hi Sam, 2017-01-12 14:06 GMT+01:00 Sam Kumar : > Hi Martine, > I will work on testing it with sock and PR #6004, but it may take some > time since I might need to port the interface from conn to sock. > It seems to me that conn is deprecated and that sock is its replacement > moving forward. Am I

Re: [riot-devel] Release 2017.01

Hi, congrats to all for the release and thanks to Peter for the great release managing work! Cheers, Martine 2017-02-02 10:19 GMT+01:00 Oleg Hahm : > Great, finally we have an Enterprise[1] release! ;-) > > Thanks a lot for the wonderful efforts, everybody, and, of course, > particular > Peter f

[riot-devel] netdev2 is now netdev

Hi, with the last network device based on gnrc_netdev removed we were now able to rename netdev2 to netdev [1], which is now the only (network stack independent) API to access a network device. The only pitfall that might be a problem I was able to identify when porting is that the adaption layer

Re: [riot-devel] netdev2 is now netdev

Hi, 2017-03-15 11:54 GMT+01:00 Oleg Hahm : > Hi Martine! > > Thanks for the info. Just a short clarification question: > > On Wed, Mar 15, 2017 at 11:46:47AM +0100, Martine Lenders wrote: > > The only pitfall that might be a problem I was able to identify when > > p

Re: [riot-devel] Socket #0

hind the original check that I am not > aware of. Could someone more familiar with the sock code please take a look? > > Thanks, > Sam > > On Thu, Jan 12, 2017 at 5:19 AM, Martine Lenders > wrote: >> >> Hi Sam, >> >> 2017-01-12 14:06 GMT+01:00 Sam Ku

Re: [riot-devel] Sending the udp packets does not work with the xbee module

Hi Friedrich, the xbee module has some tricky restrictions on sent packets. Did you make sure that the (link-layer) payload fits these? Regarding debugging: Try compiling with CFLAGS_OPT=-O0 and CFLAGS="-g3 -gdwarf-3". This usually leads to more satisfying results. I don't have an xbee module at ha

Re: [riot-devel] Sending the udp packets does not work with the xbee module

gliche Nachricht- > Von: devel [mailto:devel-boun...@riot-os.org] Im Auftrag von Martine Lenders > Gesendet: Montag, 20. März 2017 15:08 > An: RIOT OS kernel developers > Betreff: Re: [riot-devel] Sending the udp packets does not work with the xbee > module > > Hi Fried

Re: [riot-devel] Sending the udp packets does not work with the xbee module

riot-os.org] Im Auftrag von Martine Lenders > Gesendet: Montag, 20. März 2017 17:07 > An: RIOT OS kernel developers > Betreff: Re: [riot-devel] Sending the udp packets does not work with the xbee > module > > Hi Friedrich, > on what board are you using the xbee? Is there an o

Re: [riot-devel] Sending the udp packets does not work with the xbee module

Hi, 2017-03-21 11:09 GMT+01:00 Wiegel, Friedrich (IAI) : > […] I try to get my hands on the hardware, and try it out myself. > Is there a way to avoid the failed assertion when I increase the number of > interfaces to 2 but use one or is it only one interfaces available? if there is enough mem

Re: [riot-devel] Neighborhood detection - some general questions

Hi, if you really want to use vanilla NDP (6LoWPAN-NDP assumes the link-local IP address was automatically generated from the hardware address) in a LoWPAN, compile gnrc_networking with the following modules instead of `gnrc_ipv6_router_default`: ``` USEMODULE += gnrc_sixlowpan USEMODULE += gnrc_s

Re: [riot-devel] RFC: packaging "start_network.sh" on IoT-LAB

Hi Gaëtan, This sounds great! Would it be possible to merge this with the current version of the script (say with an additional parameter), so we can use it in the `iotlab-term` target version of the border router [1]? Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc

Re: [riot-devel] RFC: packaging "start_network.sh" on IoT-LAB

Hi, 2017-04-20 10:23 GMT+02:00 Alexandre Abadie : > Then it should be quite straightforward but not very useful since the > command on its own is already very simple. > Besides that the command can already been used from A8 nodes. > I think it's even simpler if I don't have to think about loggi

Re: [riot-devel] Notification: Hack'n'ACK @ Tue Apr 25, 2017 5pm - 10pm (RIOT Events)

e.com/calendar/event?action=VIEW&eid=bGJrNG1mdWNxZG9tY2Y3YzhvOWNnNGNtc2dfMjAxNzA0MjVUMTUwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn> > Hack'n'ACK > > *When* > Tue Apr 25, 2017 5pm – 10pm Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://maps.google.com/maps?q=FU+Berlin;+

[riot-devel] Buffer Overflow in ipv6_addr_from_str() fixed

Hi, the maintainers of RIOT were made aware of a potential vulnerability in the ipv6_addr module a few days back. An off-by-2 and off-by-4 error caused a buffer overflow in ipv6_addr_from_str() allowing a potential attacker to overwrite the return address of the surrounding frame. This occured due

Re: [riot-devel] RIOT Research Seminar: a short report

Hi Ken, there used to be OpenWSN support in RIOT but due to a missing maintainer on our side (we did not find the time to adapt it to our rapidly changing APIs for timers and networking) we had to remove it for now [1]. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/pull/6359 2017-04-29 15:

Re: [riot-devel] Auto init in OpenThread

Hi Jose, that is exactly the same problem Shugou currently has with lwMAC [1] and I had when porting lwIP and emb6. When we originally wrote the auto-initialization we had cases like this (different stacks, different MAC protocols) in mind, but refrained from providing a solution since it simply wa

Re: [riot-devel] Auto init in OpenThread

Hi, 2017-05-03 0:27 GMT+02:00 Jose Alamos : > […] > What's your opinion on how to deal with this? (e.g #ifdef > MODULE_OPENTHREAD in auto_init_ file?) > For now this would be the solution (that Shugou is going for as well), but as I said: let's come up with a better one soon-ish. ___

[riot-devel] Ladies That FOSS 2.0

Hi, For those of you who don't know, last October we participated at the "Ladies that FOSS" Hackathon intended to bring women into Free and Open Source Software projects. This was rather successful as we got an implementation of the SNTP protocol out of it. For the last few month we weren't able to

Re: [riot-devel] Ladies That FOSS 2.0

Hi, sadly this month's Ladies That FOSS (the one tomorrow) was canceled, but let's wait and see what next month will bring. Kind Regards, Martine 2017-05-15 11:47 GMT+02:00 Martine Lenders : > Hi, > For those of you who don't know, last October we participated at th

Re: [riot-devel] Support for cc3200

Hi, 2017-05-19 8:00 GMT+02:00 Härtinger Markus : > Hi > > We are currently developing an WIFI support in RIOT-OS for the CPU cc3200. > > Our implementation is based on the code of Attilio Donà and the vendor > libraries of Texas Instruments. > Great! Thanks for picking that up. > > > After the

Re: [riot-devel] Support for cc3200

0) to the riot network stack. > > > > Best Regards > > > > Markus > > > > *Von:* devel [mailto:devel-boun...@riot-os.org] *Im Auftrag von *Martine > Lenders > *Gesendet:* Freitag, 19. Mai 2017 09:11 > *An:* RIOT OS kernel developers > *Betreff:* Re: [rio

Re: [riot-devel] Minimal MCU clock speed for using it as a border-router.

Hi Neo, regarding clock speed I'm not aware of any restrictions on the `gnrc_border_router` example (though there are some on space, which most STM32 MCUs should fulfill). It might get slower and depending on the traffic it might get overwhelmed, but I think no one ever made any experiments for th

Re: [riot-devel] 2017.07 feature freeze

Hi, I took it upon me to make the 2017.10 tag a proper annotated tag using `git tag -a` (`git describe` on current master no returns `2017.10-devel`). The last real annotated tag was 2017.04-devel, so for the last two releases our master counted commits from 2017.01 ;-). Cheers, Martine 2017-06-3

Re: [riot-devel] Help needed for porting to stm32l4

Hi Nazmul, have you seen the Porting Guide [1]? It should provide you with all information you need. Best Regards, Martine [1] https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide 2017-07-05 6:40 GMT+02:00 Nazmul Alam : > Hi Rioters, > I want to port RIOT to stm32L4discovery device, the cpu is co

Re: [riot-devel] where to put bootloader?

Hi, gut feeling says `dist/tools/bootloader` (maybe something more unique than just bootloader?), since it isn't really part of the system and not really an example, but a quite specific application. Then again, for the same reasons I could argue to put it in the root folder, that IMHO should be k

Re: [riot-devel] IPv4 support

Hi Oleg, 2017-08-18 15:37 GMT+02:00 Oleg Hahm : > Dear Ameya! > > On Fri, Aug 18, 2017 at 06:38:31PM +0530, Ameya Joshi wrote: > > Does the latest version of RIOT support IPv4? > > RIOT supports the lwip network stack which supports IPv4. However, AFAIK > there > is no IPv4 support for applicatio

Re: [riot-devel] gnrc_border_router in native

Hi, I assume you want to use it with the xbee (otherwise it does make little sense, since this is the only non-Ethernet device we support for native, AFAIK)? If so, please don't use `ethos` as the second interface, but just `netdev_tap` (which is pulled in by default). If you want to be experimenta

Re: [riot-devel] gnrc_border_router in native

Ethernet-based. > > Is it clearer? > > Cheers, > > 2017-08-24 16:56 GMT+02:00 Martine Lenders : > > Hi, > > I assume you want to use it with the xbee (otherwise it does make little > > sense, since this is the only non-Ethernet device we support for native, > &

Re: [riot-devel] 6lowpan is not answering address ff02::2

Hi, can you try with the new neighbor discovery? [1] Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/pull/7479 2017-09-04 20:09 GMT+02:00 Baptiste Clenet : > Hi, > > I've flashed gnrc_networking on two samr21-xpro. I've noticed that > they do not answer to router solicitation because "pack

Re: [riot-devel] native target, adc and encx24j600

Hi Temmu, actually, there is no `periph_adc` implementation on native. But if you don't care about the return value, a simple mock-up should be easily ported. Just adapt the `periph_conf.h` of native accordingly and add the implementation to `cpu/native/periph/adc.c`. For the encxj600 problem: jus

[riot-devel] Updated invitation: Hack'n'ACK @ Tue Oct 10, 2017 5pm - 10pm (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 TZNA

Re: [riot-devel] gnrc: MAC layer selection

Hi Joakim, Hi Shuguo, First of all: We know of this problem and I try to come up with a solution for this for a long time, so thanks for picking this up. A step into that direction (but not the final solution) was the refactoring of GNRC's interface layer (aka gnrc_netif2, see [1], should also sim

Re: [riot-devel] On the State of RIOT's IEEE 802.15.4 Support

Hi, this will be discussed tomorrow at the T2TRG meeting preceeding the RIOT summit [1]. Will anyone of you who discussed this be there? The premise is that 6LoWPAN was designed to run on even on a minimized, non-compliant IEEE 802.15.4, so the question is: other than PAN bootstrapping and MAC: is

Re: [riot-devel] Graphing build sizes

Hi Koen, Wow, +1! Cheers, Martine 2017-10-11 16:59 GMT+02:00 Koen Zandberg : > Hello, > > One of the issues from the CI discussion at the RIOT summit was the > tracking and graphing of the nightly build sizes. After some > instructions from Kaspar for getting the JSON files I got something > wo

<    1   2   3   4   5   >