Don't warn if chip version is greater than CONFIG_ESP32_REV_MIN (IDFGH-1778)

[ecc1]

The whole point of this configuration variable is that it's a minimum revision. There's no need to warn if the actual version is greater, and indeed "suggest to upgrade it" is not only bad English, it's bad software engineering advice.

https://github.com/espressif/esp-idf/blob/master/components/esp32/cpu_start.c#L411-L418

[suda-morris]

Thanks @ecc1 for your suggestion. We will change it to normal information log ASAP.

[jimmo]

@ecc1 I thought the idea was that by setting a higher minimum version (i.e. to match your chip revision) then fewer workarounds for old revisions need to be enabled. That sounds like good advice, especially if the workarounds cost performance or code size.

[negativekelvin]

It's a good hint, although better to receive this info at compile time like "This build supports ESP32 REV:0+". Also helpful would be if app binary header had this minimum rev and esptool or OTA would not flash an incompatible binary (@projectgus). Ideally workarounds would be selectively available by compile time config but dynamically enabled at runtime based on detected chip version. Some do have runtime checks, I think.

[igrr]

Also helpful would be if app binary header had this minimum rev and esptool or OTA would not flash an incompatible binary

You seem to have gained access to our internal repository somehow :) This has been merged recently, should be on Github soon.