Hi, did we consider that Arduino support got broken, because the stack with security (which is mandatory in my mind) is just to large now for that device? How can we, ignoring that, just move on and try to use other small devices? Isn?t this a proof of concept - which now fails? Why did it break? Are we sure the stack can still fit? I think it is easy to say - it is broken - ok - lets remove that one and look instead for other small devices (thin ice in my mind) ,-)
thanks Christian > On 2 Mar 2017, at 17:51, Thiago Macieira <thiago.macieira at intel.com> wrote: > > On quinta-feira, 2 de mar?o de 2017 01:27:15 PST Philippe Coval wrote: >> I have observed that arduino support broke between 1.2-rel and master, >> I've tried to fix in in private branch (I can share WIP patches) , >> and ended to conclusion that 8KB of RAM is not enough for new introduced >> features, >> so instead of optimizing it too much, I thought about switching to ESP82266, >> latest version of modules are more powerful, and eventually get back to >> Arduino mega later. > > Arduino hasn't supported 1.2 features, even most of 1.1: it does not support > OCF security. It's been broken (under that definition) for a year. > >> ESP8266 platform was proposed for iotivity 1.3-rel, >> while iotivity-constrained is more relevant for constrained devices, >> I still think it's good to keep building CSDK for MCUs >> to at least detect compilations issues >> (ie: detect types inconsistencies, like size_t and unit32_t). > > I disagree. Why do we want to detect that if it's not a target? > >> So I would suggest to preserve the arduino macros (and jenkins) >> and but remove mega2560 of supported hardware 1.3-rel, >> while 1.2-rel could be branched for MCU supports (1.2.1 is working on mega). > > Still disagree. Move ESP8266 support to iotivity-constrained instead. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
