Hi Janna,
welcome to RIOT! Short answer: Yes and no, but we could need more people
working on it :-). Maybe the authors can share further insights. Please
have a look at the following efforts:
https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking_mac
Hi all,
Can we add Koen's mail [1] about easing maintainer burden to the agenda? I
think there are some points RIOT could benefit from.
Kind regards,
Bas Stottelaar
[1] https://lists.riot-os.org/pipermail/devel/2018-February/005627.html
2018-02-25 20:08 GMT+01:00 Francisco Acosta
Hi everyone,
sorry for the late reply. The remodeling of the I2C (master) API should
indeed be tackled ASAP (as every newly merged implementation just adds
to the work)... But this is not new and I/we have been talking about
this for ages now...
I won't be able to drive this nor to spend
Hi again,
fixup to my previous mail: the new proposed API is better presented in
#6576 [1]...
Cheers,
Hauke
[1] https://github.com/RIOT-OS/RIOT/pull/6576
On 02/26/2018 10:07 AM, Hauke Petersen wrote:
Hi everyone,
sorry for the late reply. The remodeling of the I2C (master) API
should
Hi,
when are we finally moving up the meeting to 16:00 CET? I'll need to leave
again at 17:30.
Best,
Martine
2018-02-25 20:08 GMT+01:00 Francisco Acosta :
> Hi devs!
>
> Just a gentle reminder for our next developers meeting which will take
> place this Monday
Hi,
I think that giving more precise APIs and removing the low level
implementation detail from it is a good thing.
It means that the library can adapt to the current hardware and PM
constraints.
I have questions regarding the transition to new timers.
As several modules have dependencies
Hi!
Thanks for your answers.
I wasn’t aware that Koen is not in the devel mailing list. I’d suggest to
subscribe :)
For the meeting start, we can actually try to move it at 16:00 CET today, I’ve
already asked in the planning of the previous meeting and no one refused so
far, thus today’s
Hi Paco,
so the meeting is at 4PM (now) right?
What is the exact zoom.us meeting point?
Best,
Emmanuel
On Mon, Feb 26, 2018 at 11:03 AM, Martine Lenders
wrote:
> Hi,
>
> when are we finally moving up the meeting to 16:00 CET? I'll need to leave
> again at 17:30.
>
>
Hi! Yes, it’s happening now.
The link is: https://zoom.us/j/235153205
Francisco Javier Acosta Padilla
Research Engineer at INFINE team
Inria Saclay Ile-de-France
On 26 February 2018 at 16:04:14, Emmanuel Baccelli (emmanuel.bacce...@inria.fr)
wrote:
> Hi Paco,
>
> so the meeting is at 4PM
Hi Gunar,
That sounds great. I'm really looking forward to your port and can't
wait to upgrade some older ESP-projects to RIOT finally.
Thanks for working on that and letting us know. Feel free to ping me
when the PR is ready and I'll try to help with testing.
Cheers
Michel
On
Hi,
I just want to let the community to know that I'm trying an ESP8266
port. At the moment
- the core's thread interface is implemented and tested,
- the core's irq interface is implemented and tested,
- GPIO handling module periph_gpio is implemented and tested,
- small applications like
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
This may or may not be useful, but a company called Whitecat have done a
port of FreeRTOS to the ESP8266:
https://github.com/whitecatboard/Lua-RTOS-ESP8266
Dan.
On 26.02.2018 13:00, Gunar Schorcht wrote:
Hi,
I just want to let the community to know that I'm trying an ESP8266
port. At the
Hi again!
Well, it seems I misunderstood what Bas was proposing. I just thought Koen was
not in the list (but actually he is), but it was just to propose Koen’s topic
in the meeting.
So, if Bas and/or Koen want to talk about the idea it would be great. We might
define some first steps and
14 matches
Mail list logo