Hi, > Regardless, this patch actually does not contain any code for EEPROM > support I have just mentioned it to give more context on why mikroBUS > manifest is the focus of this patch instead of DT overlay or something > else. Right, and I think this is the crux here. Why can't you use DT overlays? The manifest files, seem to be yet another hardware description (method) and we already have DT. Can't we have some kind of userspace helper that could translate them to DT overlays? That way, you could also handle the EEPROM vs non-EEPROM case, or have some other kind of method to load a DT overlay. Admittedly, I've never worked with in-kernel overlays, but AFAIK they work with some subsystems. -michael
Attachment:
signature.asc
Description: PGP signature
