Can the EEPROM on BB capes generate a Device Tree Overlay without one being present first on the BB?

According to the SRM (8.2.4&5) the EEPROM of capes contains information to mux all of the pins needed for the cape.

But, I have found conflicting answers for my question.

Here (and in 2013) it says that it cannot but here (and more recently) it implies that it can.

Can anyone point me to a more definitive answer?

While it is in the spec, that feature ended up being never used in production.

Currently we just read the part_number and version from the eeprom and
read the matching overlay..

As i currently hack on u-boot, that "feature" would have been nice for
dependency tracking. :wink: