Description
Checklist
- Checked the issue tracker for similar issues to ensure this is not a duplicate
- Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
- Tested with the latest version to ensure the issue hasn't been fixed
How often does this bug occurs?
always
Expected behavior
Select driver/sccb-ng.c or driver/sccb.c should be configurable.
Not depends on the IDF version.
Actual behavior (suspected bug)
The esp32-camera library now uses new i2c drvier (driver/sccb-ng.c) if build with IDF-5.4+.
However, the new i2c drvier will not co-exist with old driver.
There are some libraries still use old i2c driver, as a result this forces
people stick on old SDK now.
Similar issue was reported on:
UncleRus/esp-idf-lib#667
And according to below reply:
espressif/esp-idf#15566 (comment)
Other 3rd component will rely on community.
Which means it's difficult to know the timeline for converting to use new driver in 3rd component.
Since the i2c legacy driver is still working on IDF-5.4, I think it should
be configurable to allow select using driver/sccb-ng.c or driver/sccb.c.
Error logs or terminal output
Steps to reproduce the behavior
Build esp32-camera with esp-idf-lib.
Project release version
espressif/esp32-camera v2.0.15
System architecture
Intel/AMD 64-bit (modern PC, older Mac)
Operating system
Linux
Operating system version
ubuntu 24.04
Shell
ZSH
Additional context
No response