Re: [riot-devel] [riot-users] Release 2019.10

Woohoo! Congratulations to everyone and thanks Ken for the great work! Best regards, Martine Am Do., 31. Okt. 2019 um 14:29 Uhr schrieb Emmanuel Baccelli < emmanuel.bacce...@inria.fr>: > Yay! Congrats to all involved, and thanks a bunch Ken for managing this > release! > Cheers > Emmanuel > >

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

Hi Kaspar, The official start is still 5pm. Berlin and Paris just start early at 3pm due to varying reasons. Best regards, Martine PS: "Central European Time - Berlin" is the timezone indicator in the quoted case ;-). Am Mo., 28. Okt. 2019 um 20:13 Uhr schrieb Kaspar Schleiser <

[riot-devel] Deprecation of `gnrc_nettest`

Hi there, Jose and I proposed to deprecate `gnrc_nettest` [1]. It was originally introduced to allow for integration tests of single GNRC modules, but it never really got used and it is most often easier to just use `gnrc_netreg_register()/unregister()` directly for that. In the very unlikely

[riot-devel] Deprecation of emb6

Hello, I just proposed to deprecate emb6 [1] (the OS-independent version of Contiki's uIP). Is anyone using this package? If yes, please speak up! Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/pull/12389 ___ devel mailing list

Re: [riot-devel] Updated invitation: Monthly RIOT developer meeting @ Monthly from 4pm to 5pm on the last Monday from Mon Oct 31, 2016 to Sun Sep 29 (CET) (RIOT Events)

last Monday from Mon Oct 31, > 2016 to Sun Sep 29 Central European Time - Berlin > > *Where* > Online (map <https://www.google.com/maps/search/Online?hl=en>) > > *Calendar* > RIOT Events > > *Who* > • > Martine Lenders - creator > > Invitation from Google Cale

Re: [riot-devel] devel Digest, Vol 79, Issue 14

467 >> >> Skype: adnanrashidpk >> >> --- >> -- next part -- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.ri

Re: [riot-devel] How to Proceed?

Hi Adnan, Can you refer us to the tutorial you are following? I'm not aware of any that describes VMware integration. Kind Regards, Martine Adnan Rashid schrieb am Mi., 25. Sep. 2019, 12:50: > Hi Support Team, > > I want to simulate by using RIOT OS. What is the way forward? I had > followed

Re: [riot-devel] Remote Shell Commands

Hi, I'm not sure we should migrate the shell to a completely structured output. Though I can see the benefit of that wrt remote execution via CoAP/CBOR, a shell should be primarily human readable. However, maybe there is some middle ground to be found for that. Another interesting read with

Re: [riot-devel] Fragmentation in RIOT

Hi Adel, And welcome to the RIOT community! Adel Fuchs schrieb am Mi., 4. Sep. 2019, 16:13: > Hi, > > * Does RIOT support fragmentation in IPv6? > With https://github.com/RIOT-OS/RIOT/pull/11596 and https://github.com/RIOT-OS/RIOT/pull/11623 merged, fragmentation is supported by RIOT's

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

n;+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 peterschme...@gmail.com > because you

[riot-devel] Deprecate NHDP module?

Hi, I just proposed to deprecate the `nhdp` module [1], due to a stale code base. If anyone is still using it or interested in maintaining it, please let us know. Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/pull/11987 ___ devel mailing

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

m – 10pm Central European Time - Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://www.google.com/maps/search/FU+Berlin;+HAW+Hamburg?hl=en>) > > *Calendar* > RIOT Events > > *Who* > • > Martine Lenders - creator > > Invitation from Google Calenda

Re: [riot-devel] [riot-users] Release 2019.07

Hi, Congretulations! Cheers, Martine Am Do., 25. Juli 2019 um 11:46 Uhr schrieb Kevin Weiss < kevin.we...@haw-hamburg.de>: > Dear RIOTers, > > we are happy to announce the 20th official release of RIOT: > > --- * RIOT 2019.07 * --- > > The 2019.07

Re: [riot-devel] How to wait for a thread to end?

Hi, not 100% sure if this can be done generally (apart from the state checks it should AFAICS), but have a look how the pthread implementation how it implements `pthread_join()` [1] which is essentially what you are trying to do (see pthread_join(3)). Cheers, Martine [1]

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

Q> > *When* > Tue Jun 25, 2019 5pm – 10pm Central European Time - Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://www.google.com/maps/search/FU+Berlin;+HAW+Hamburg?hl=en>) > > *Calendar* > RIOT Events > > *Who* > • > Martine Lenders

Re: [riot-devel] Release 2019.07 - dates and feature requests

Hi, would also be nice to add IPv6 fragmentation [1] and reassembly [2]. I think the feature will be finished today for the most part (only tests for fragmentation are missing). However, 6LoWPAN NHC adaption for extension headers (on which IPv6 fragmentation is based on) is still missing. This

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

+Berlin;+HAW+Hamburg=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 peterschme...@gmail.com > because you are s

Re: [riot-devel] Release 2019.04

Congratulations, everyone! Am Mo., 29. Apr. 2019 um 16:02 Uhr schrieb Daniel Petry < daniel.pe...@fu-berlin.de>: > Dear RIOTers, > > we are happy to announce the 19th official release of RIOT: > > --- * RIOT 2019.04 * --- > > The 2019.04 release includes a

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

Code+Lounge=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 peterschme...@gmail.com > because you are s

[riot-devel] Updated invitation: Hack'n'ACK @ Tue Mar 26, 2019 5pm - 10pm (CET) (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] Clocksync in RIOT OS

Hi Nitin, Am Mi., 30. Jan. 2019 um 09:25 Uhr schrieb Nitin Shivaraman < nitin.shivara...@tum-create.edu.sg>: > Hello, > > > > I’m working on implementing a custom clock synchronization protocol on > Riot OS. > > I saw that the earlier branch having well-known protocols (FTSP, GTSP, > etc)

Re: [riot-devel] RIOT-OS assembly @ 35C3

Hi, In case you are searching for us. We were switched around a little: https://35c3.c3nav.de/l/c:0:438.09:481.89/@0,439.08,482.83,5 Kind Regards, Martine Am Di., 25. Dez. 2018, 21:10 hat Martine Lenders geschrieben: > Oops forgot the link: https://35c3.c3nav.de/l/riotos/ > > Am Di.

Re: [riot-devel] RIOT-OS assembly @ 35C3

Oops forgot the link: https://35c3.c3nav.de/l/riotos/ Am Di., 25. Dez. 2018, 21:07 hat Martine Lenders geschrieben: > Hi everyone, > > We now have a location for the RIOT assembly @ 35C3. See you there! > > Regards, > Martine > _

[riot-devel] RIOT-OS assembly @ 35C3

Hi everyone, We now have a location for the RIOT assembly @ 35C3. See you there! Regards, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Neighbor solicitations (NS) from border router (6lo ND)

See [1] for a fix. [1] https://github.com/RIOT-OS/RIOT/pull/10627 Am Mo., 17. Dez. 2018 um 12:21 Uhr schrieb Martine Lenders < m...@martine-lenders.eu>: > Hi Thomas, > > Am Mo., 17. Dez. 2018 um 11:57 Uhr schrieb Thomas C. Schmidt < > t.schm...@haw-hamburg.de>: > &g

Re: [riot-devel] Neighbor solicitations (NS) from border router (6lo ND)

Hi Thomas, Am Mo., 17. Dez. 2018 um 11:57 Uhr schrieb Thomas C. Schmidt < t.schm...@haw-hamburg.de>: > Hi Martine, > > On 17/12/2018 11:17, Martine Lenders wrote: > > > at first glance this seems to be indeed a bug. If the prefix > > `2001:db8::/64` is configured

Re: [riot-devel] Neighbor solicitations (NS) from border router (6lo ND)

Hi, at first glance this seems to be indeed a bug. If the prefix `2001:db8::/64` is configured for one interface, this should be hint enough for the NDP to use that interface to multicast the NS there. I'll investigate that. However, I have to add that RFC 6775 (which applies for the border

[riot-devel] Updated invitation: Hack'n'ACK @ Monthly from 5pm to 10pm on the last Tuesday from Tue Mar 29, 2016 to Mon Nov 26 (CEST) (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

[riot-devel] Updated invitation: Hack'n'ACK @ Tue Dec 18, 2018 5pm - 10pm (CET) (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:VEVENT DTSTART:20181218T16Z DTEND:20181218T21Z DTSTAMP:20181116T142748Z

[riot-devel] New event: Hack'n'ACK @ Tue Dec 18, 2018 5pm - 10pm (CET) (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:VEVENT DTSTART:20181218T16Z DTEND:20181218T21Z DTSTAMP:20181116T142602Z

Re: [riot-devel] 35C3 CfP

Mi., 10. Okt. 2018 um 21:18 Uhr schrieb Martine Lenders < m...@martine-lenders.eu>: > Hi, > > to everyone interested FYI: The presale dates are set: > https://events.ccc.de/2018/10/10/35c3-tickets-presale/ > > Regards, > Martine > > Am Mo., 24. Sep. 2018 u

Re: [riot-devel] Preparing release 2018.10

Hi Gunar, Am Sa., 6. Okt. 2018 um 13:56 Uhr schrieb Gunar Schorcht : > Hi Jose, > > is it necessary to tell you also features that were merged into master > since last release or are they included automatically, e.g., the ESP8266 > platform? > Usually the features added during a release cycle

Re: [riot-devel] 35C3 CfP

. ;) > > Cheers Simon > > Am 2018-09-19 18:04 schrieb Martine Lenders: > > Hi, > > > > FYI, the CfP for 35C3 is out [1] since last week. > > > > My current plan is to represent the RIOT community there with an > > high-level introductory talk on ICN w

Re: [riot-devel] Lifting the 50 characters commit first line limit?

Hi Pekka, feel free to change the check script [1] to whatever is most comfortable to you :-) (sorry today I'm very busy so I can't do it myself; but I'm happy to review it once ready). Regards, Martine [1] https://github.com/RIOT-OS/RIOT/blob/master/dist/tools/commit-msg/check.sh Am Mi., 10.

Re: [riot-devel] Lifting the 50 characters commit first line limit?

Hi Pekka, the 50 chars is just the warning bound. You can go up to 70 until the commit message check fails on you. Longer will make GitHub break the commit message in the webview with the dreaded […] ;-). My usual approach is to boil down the summary to the bare minimum within these constraints

Re: [riot-devel] Unit test code coverage using gcov

Hi, as there is some discussion to split the unittests into several applications [1] and some stuff isn't included into them for good reasons (driver test e.g.), I'm not sure if this should be constrained to unittests (though they are indeed a good starting point). Regards, Martine PS: I'm not

Re: [riot-devel] Git submodule in RIOT-OS/applications

Hi Jose, while I agree that this would be easier for new users, I don't see how this would help with applications being in a working state. First of all, continuous integration is missing for those applications anyways (IMHO we should change that), so a working state isn't guaranteed in the

[riot-devel] Murdock compiling with LLVM now for several Cortex-M boards

Dear RIOTers, with #9809 [1] merged we now we also test compiling (and running the resulting binary) with LLVM, so please if your PR has some build older than the merge date (2018-09-25 18:40 +02:00), re-run the build on Murdock (by un- and re-setting the "CI: ready for build" label), to make

[riot-devel] Updated invitation: Monthly RIOT developer meeting @ Monthly from 4pm to 5pm on the last Monday (CET) (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

[riot-devel] Livestream @ RIOT-Summit

Hi, we have a livestream this year [1]. It's our first try so please forgive is there are some hick-ups. Cheers, Martine (miri64) & Sebastian (smlng) [1] https://www.youtube.com/watch?v=FFvJANMkShg ___ devel mailing list devel@riot-os.org

Re: [riot-devel] Activation of modules by make command line

Hi Gunar, Of course it is possible to do it from command-line. You were pretty close, but you don't need an intermediate variable. Just set the variable USEMODULE in your environment: USEMODULE="sdcard_spi mrf24j40" BOARD=... make ... Regards, Martine Am Do., 6. Sep. 2018 um 10:33 Uhr

[riot-devel] A general fragmentation/reassembly library for GNRC

Hi, Triggered by an issue a short while ago [1], and the necessity for IPv6 fragmentation/reassembly that crystalized out of that, I remembered that Cenk and Jose were in the talks of a general fragmentation/reassembly library for GNRC. Is this still on the table? If yes, I think we should

[riot-devel] Canceled event: Hack'n'ACK @ Tue Dec 25, 2018 5pm - 10pm (CET) (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

[riot-devel] Canceled event: Monthly RIOT developer meeting @ Mon Dec 31, 2018 5pm - 6pm (CET) (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

[riot-devel] Updated invitation: Monthly RIOT developer meeting @ Mon Sep 23, 2019 5pm - 6pm (CEST) (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] TCP on RIOT OS

Hi Theresa, were you using link local addresses (i.e. are they prefixed `fe80::/64`) for your trials? If yes, newer versions require to also provide an interface with that (as it is the case e.g. also on Linux) so this might be your problem. The client and server needs to be fixed then of course

Re: [riot-devel] PIC programmer with Linux support?

Hi, if its still needed and if it helps: I have a PICkit3 (my property) at my office that I don't really need and am willing to donate to the cause. I needed it years ago for a private project that I gave away (and was able to confirm that it is still running after all those years during my

Re: [riot-devel] Porting RIOT to ESP8266

(or, since I just saw that you provide ports for several board variations, several PRs) 2018-04-07 14:49 GMT+02:00 Martine Lenders <m...@martine-lenders.eu>: > Hi Gunar, > > Cool, do you think you can get it in a state where you can provide a PR? > > Cheers, > Martine >

Re: [riot-devel] Porting RIOT to ESP8266

Hi Gunar, Cool, do you think you can get it in a state where you can provide a PR? Cheers, Martine 2018-04-07 14:00 GMT+02:00 Gunar Schorcht : > Hello, > > I just want to inform that I have commited a first working version of > the RIOT port to ESP8266 to my fork at > >

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

s.google.com/maps?q=FU+Berlin;+HAW+Hamburg=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 peterschme...@gmail.com > b

Re: [riot-devel] RIOT integration options for Whitefield

Hi Rahul, (context for the rest of the list: we talked f2f today about this after lwig @ IETF101) I agree with Ludwig that option 2 is the best option to implement this. If you looking for a template to implement against netdev, have a look at `socket_zep` [1] (and ignore what I proposed at our

Re: [riot-devel] hwrnd how to implement

that random32 calls or any > calls to random are directed to hwrng_read > > Is this already done by just enabling the module when building with > FEATURES_REQUIRED = periph_hwrng ? > > > > > > *Von:* devel <devel-boun...@riot-os.org> <devel-boun...@riot-os.org> *Im

Re: [riot-devel] hwrnd how to implement

Hi Josua, when the RNG component of the at86rf2xx driver was provided in [1] we decided to not implement the `periph/hwnrg` with it. Main reasons are that it is 1. Not a `periph` (i.e. a CPU feature) 2. Hard to integrate when e.g. the CPU already provides a `hwnrg`. Hope this helps, Martine

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

ent?action=VIEW=bGJrNG1mdWNxZG9tY2Y3YzhvOWNnNGNtc2dfMjAxODAyMjdUMTYwMDAwWiBrM3FsOHNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn> > Hack'n'ACK > > *When* > Tue Feb 27, 2018 5pm – 10pm Berlin > > *Where* > FU Berlin; HAW Hamburg (map > <https://maps.google.com/maps?q=FU+Berlin;+HAW+Hamburg=en>) >

Re: [riot-devel] Timers

Hi, There might also be some kind of `offset` setter for the `now()` return value required, when considering that this new timer API should also be backended by RTC and/or RTT. This can come in handy to set the system time with time synchronization protocols like (S)NTP. Cheers, Martine

[riot-devel] Updated invitation: Monthly RIOT developer meeting @ Mon Mar 26, 2018 4pm - 5pm (CEST) (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] Notification: Monthly RIOT developer meeting @ Mon Feb 26, 2018 5pm - 6pm (CET) (RIOT Events)

ance for you attendance! > > Best, > > Francisco. > > > > On 25 February 2018 16:59:58 CET, Google Calendar < > calendar-notificat...@google.com> wrote: > >This is a notification for: > > > >Title: Monthly RIOT developer meeting > >When: Mon

Re: [riot-devel] Ceedling

Hi Francisco, as far as I know Cenk looked into that a few months back. I don't know however what came out of that? Cheers, Martine 2018-01-10 21:10 GMT+01:00 Francisco Molina : > Following up with Baptiste question. Has anyone integrated other testing > tools into

Re: [riot-devel] Pull request

Hi JP, First of all, welcome to the RIOT community and thank you for your contribution! There are two steps to our CI at the moment. The first one is Travis, which provides you with some preliminary static check regarding our coding conventions, documentation and also some static code analysis.

Re: [riot-devel] RIOT Code of Conduct

Hi all, with the Code of Conduct now merged, it is in effect now effective immediately. Keep being awesome to each other! Kind regards, Martine [1] https://github.com/RIOT-OS/RIOT/pull/8116 2017-11-24 15:30 GMT+01:00 Martine Lenders <mlend...@riot-os.org>: > Hi *, > > as so

Re: [riot-devel] 6lowpan Host with SLAAC, minimum ram

A... after five seconds of thinking I think I know what you mean: You can't pick-and-choose shell commands. Yes this would be nice (and I was thinking about something similar). Let me open an issue were we can discuss further on that. Cheers, Martine 2017-12-04 15:31 GMT+01:00 Martine

Re: [riot-devel] 6lowpan Host with SLAAC, minimum ram

Hi, 2017-12-04 15:14 GMT+01:00 Arndt, Josua : > Yes it is but then all shells are disabled, not only that which I don’t > need. > The shell should still be enabled. Just the commands pulled in by the modules should be disabled. Cheers, Martine

Re: [riot-devel] 6lowpan Host with SLAAC, minimum ram

Hi, This sounds awesome! 2017-12-04 15:05 GMT+01:00 Arndt, Josua : > If there is demand for separately enabled shells I could do a PR, but this needs to be also well documented and I’m not quite sure which is the best way. Maybe I've missed something, but this is

[riot-devel] Test

Dan Petry was reporting, that none of his mails got through to devel, so this is a test if there is a problem with this mailing list. Please ignore this message, if it comes through ;-) Cheers, Martine ___ devel mailing list devel@riot-os.org

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

n;+HAW+Hamburg=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 peterschme...@gmail.com > because you ar

Re: [riot-devel] Plans for switching over to a new network infrastructure in GNRC

t the top of the page. > > Some remarks: These are the diffs between the previous and the current > build size, not absolute numbers. Furthermore, this is a comparison between > nightlies, not from merge to merge, so all merges from yesterday are > included in this diff. > > Cheers, > Koen >

Re: [riot-devel] RIOT developers monthly meeting

Hi, as hinted yesterday, I usually need to go around 5:30pm. So I was wondering if we can move the meeting to 4pm. Cheers, Martine 2017-11-27 16:33 GMT+01:00 Francisco Javier Acosta Padilla < francisco.aco...@inria.fr>: > > RIOT developers monthly meeting > Scheduled: 27 Nov 2017 17:00 to

Re: [riot-devel] Updates to the build system - modules definition

Hi Daniel, 2017-11-24 16:47 GMT+01:00 Daniel Petry : > […] > > 1) Move build information concerning a particular module into that > module's Makefile > 2) Make the module makefiles able to be written with purely declarative > language > 3) Retain backwards

Re: [riot-devel] Updates to the build system - modules definition

Hi Gaëtan, I think most of us are happy about any more structural approach to the build system, and me personally would prefer if we can stick to GNU standard tools. So in my opinion: go ahead. Maybe - as discussed offline - also start drafting some GitHub issues, outlining the drawbacks you

[riot-devel] RIOT Code of Conduct

Hi *, as some of you might have noticed, I proposed an initial version of a Code of Conduct for the RIOT community [1]. I invite you to discuss this with us, as this effects the whole community. Kind Regards, Martine Lenders [1] https://github.com/RIOT-OS/RIOT/pull/8116

[riot-devel] Updated invitation: Monthly RIOT developer meeting @ Monthly from 5pm to 6pm on the last Monday (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

[riot-devel] New event: Monthly RIOT developer meeting @ Monthly from 5pm to 10pm on the last Monday (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] Notification: Hack'n'ACK @ Tue Nov 7, 2017 5pm - 10pm (RIOT Events)

n;+HAW+Hamburg=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 peterschme...@gmail.com > because you ar

[riot-devel] RIOT assembly at 34C3

Hi, I'm going to 34C3 [1] this year. Anyone interested forming a RIOT assembly [2] there this year? Cheers, Martine [1] https://www.ccc.de/en/updates/2017/34C3-in-leipzig [2] https://events.ccc.de/2017/11/04/people-34c3/ ___ devel mailing list

Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes

s! > > -- > Francisco Javier Acosta Padilla > Research Engineer at INRIA Saclay > INFINE Team > > On 1 November 2017 at 12:25:51, Martine Lenders (m...@martine-lenders.eu) > wrote: > > Hi Cenk, > > 2017-11-01 11:05 GMT+01:00 Cenk Gündoğan <list-r...@cgundogan.de&g

Re: [riot-devel] Plans for switching over to a new network infrastructure in GNRC

Hi, FYI there is a re-integration PR now: https://github.com/RIOT-OS/RIOT/pull/7925 Cheers, Martine 2017-10-27 17:56 GMT+02:00 Martine Lenders <m.lend...@fu-berlin.de>: > Hi all, > > after the release is before the release, so let's use the drive to > continue the good wor

Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes

Hi Cenk, 2017-11-01 11:05 GMT+01:00 Cenk Gündoğan : > > > On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > > > […] > > > > P.S: @Martine, can you set up the next Hack meeting? Thanks > > > > > > > Anything different to do than the usual ad-hoc placecam

Re: [riot-devel] [riot-maintainer] Monthly meetings for organisation purposes

Hi, 2017-11-01 8:52 GMT+01:00 Cenk Gündoğan : > On 17-10-31 18:03:01, Francisco Javier Acosta Padilla wrote: > […] > > P.S: @Martine, can you set up the next Hack meeting? Thanks > Anything different to do than the usual ad-hoc placecam set-up? Cheers, Martine

[riot-devel] Plans for switching over to a new network infrastructure in GNRC

Hi all, after the release is before the release, so let's use the drive to continue the good work. Some of you might have noticed, that we are currently working on a big switch-over for GNRC-internal APIs, so if you are not involved in any direct GNRC programming or need access to the network

Re: [riot-devel] Updated invitation: Hack'n'ACK @ Tue Nov 7, 2017 5pm - 10pm (RIOT Events)

FYI: Oct 31st is a Holiday in most of Germany, that is why we decided to move it by one week. Am 27.10.2017 2:53 nachm. schrieb "Martine Lenders" <authmille...@gmail.com >: > *This event has been changed.* > more details » > <https://www.google.co

Re: [riot-devel] Release 2017.10

Yay, congratz everyone  Am 27.10.2017 12:38 nachm. schrieb "Hauke Petersen" < hauke.peter...@fu-berlin.de>: > Dear RIOTers, > > we are happy to announce the 13th official release of RIOT: > > --- * RIOT 2017.10 * --- > > This release provides fixes, code

[riot-devel] Update to the coding conventions regarding names of standardized constants and variables

Dear all, FYI: I amended the coding convention with a statement about names in standardization documents (e.g. RFCs) [1]. It's a no-brainer: They should be used at least in Doxygen to allow for easy reference when cross-checking (or review) the implementation of the standard. Cheers, Martine

Re: [riot-devel] Ethernet communication initialization.

Hi Subhasis, 2017-10-12 11:36 GMT+02:00 subhasis : > > Please clarify how enc28j60 driver starts to communicate with connected > device. Specifically how the MAC address of connected device (Linux PC) is > known to the mote. I am using OpenBase with cc2358. > As far as

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

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:

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

[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

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:

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

Re: [riot-devel] gnrc_border_router in native

p in master, which is Ethernet-based. > > Is it clearer? > > Cheers, > > 2017-08-24 16:56 GMT+02:00 Martine Lenders <m...@martine-lenders.eu>: > > Hi, > > I assume you want to use it with the xbee (otherwise it does make little > > sense, since this is the o

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

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

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

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

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

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

Re: [riot-devel] Support for cc3200

library > (cc3200) 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 > *Betr

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

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 <m.lend...@fu-berlin.de>: > Hi, > For those of you who don't know, last October we

[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

  1   2   3   4   >