> And we could introduce a new macro called AT24_CHIP_DATA_MASKED that > would automacially set the AT24_FLAG_MASKED_RANGE flag and take > another argument that would contain the address and size of the masked > register range (we'd put it into the "masked" resource)? I am all for generic solutions. One thing to consider here is that we need a generic way to detect the various types. I guess it will always(?) be decided on some memory locations having specific values?
Attachment:
signature.asc
Description: PGP signature
