From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Rui Carmo In-Reply-To: Date: Tue, 2 Jan 2018 14:31:36 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3894BD22-87BA-4D9F-9A82-721BEDCA73BD@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Inferno on microcontrollers Topicbox-Message-UUID: c83b2d10-ead9-11e9-9d60-3106f5b1d025 > On 31 Dec 2017, at 21:05, hiro <23hiro@gmail.com> wrote: >=20 >> I started porting a 9p library and writing an fs for esp8266 using >> espressif sdk, but stopped once I found out tls1.2 isn't supported = (not >> fixable; bug in firmware). >> I think esp32 is a better choice, but then, why not use rpi-zero or = other >> ARM, MIPS devices. Arguments for esp32 for power budget reasons might = be >> exaggerated a little (see >> https://www.youtube.com/watch?v=3DDDpuBJYFJ7Y&t=3D131s >> ) >> there is also proprietary firmware involved. >>=20 >> In my opinion, esp8266 should be categorized as an "attractive = nuisance". >=20 > what about esp8266's power usage? is *that* lower? why does it take 4! > seconds to send data?! I honestly don=E2=80=99t see it as slow, or as a nuisance, but then = again I have several around the house, some incorporated into commercial = products like the Sonoff S20 outlets, which I control over MQTT with = open source firmware. Where it relates to power consumption, I have sensors running in = low-power mode powered by AA batteries that last me many months, since = the ESP8266 only consumes 40 _micro_ amperes of power in deep sleep, and = waking up every 5 minutes to read a sensor and pushing out a single data = packet isn=E2=80=99t especially taxing on the batteries. R.