Expand description
Sensor identity and register tables — as data.
esp32-camera carries one C driver per sensor. Janus carries the facts
those drivers encode — product ids, bus addresses, register widths,
maximum geometry, and the register sequences that configure the part —
and leaves the state machine that applies them to rusty_esp_image-esp
(I1), where a real bus and a real clock exist.
The OV2640 and OV5640 tables are derived mechanically from esp32-camera
(Apache-2.0, attributed in LICENSE-THIRD-PARTY.md): macro names resolved,
terminators dropped, nothing else changed.
Modules§
- ov2640
- OV2640 register tables (8-bit registers, bank-switched through
0xFF). - ov5640
- OV5640 register tables (16-bit registers).
Structs§
- Mode
- What a firmware asks a sensor for.
- Register
- One register write.
- Sensor
Desc - What a driver needs to find and address a sensor.
Enums§
- Frame
Size - The standard frame sizes esp32-camera names.
- RegOp
- One step of a register sequence.
- Sensor
Id - The sensors esp32-camera knows, with their product ids.
Constants§
- SENSORS
- The sensors with a complete descriptor today: the OmniVision parts whose id registers and bus addresses are documented in esp32-camera. Others get theirs when their register tables land.
Functions§
- describe
- Find the descriptor for a sensor.