Dear community,
The ongoing I2C refactoring effort has been on track for a whole week. I
think it will take a little more time than I expect.
You can have a look at [1] to see how this is evolving.
All the changes are done on a dedicated branch (new_I2c_if) right now. Once
everything will be done,
Hi Jose,
for me it still makes sense to have commands to say "is it hardware
supported" and a different one for "the board have enough memory when
compiled in the reference environment".
The first one is a hard constraint and should never change (except by
adding hardware support implementa
Yes Martine, thanks for the info!
Unfortunately the pad we opened yesterday was removed :-( if someone kept a copy
of it I would be super thankful if you can share it.
Otherwise, I want just to point out the resolutions from the meeting:
- We need to open an issue to track Hardware In the Loop
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
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
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
Hi Paco,
2018-05-28 14:05 GMT+02:00 Francisco Acosta :
> Hi devs! Hi maintainers! Welcome to the new maintainers btw!
>
> I already sketched some ideas for today’s meeting [1]. Unfortunately the
> last month
> meeting couldn’t be held because of some confusions and a (uncommon?)
> situation on
>
Hi Janna,
just in case, note that the examples you gave in the iot-lab wiki were
written for the iot-lab nodes port for Contiki.
So will not directly apply to RIOT for the macro names.
I understand that you can need both limiting power and increasing the
threshold when you want to have a lo
