Just in case you guys _really_ and _truly_ are so unable to think
outside the box that you can't come up with something reasonable, I'll
get you started with two ideas:
1) A special "chipset" dummy netdev that a special class of ethtool
commands can run on to set these things.
2) A "chipset" genetlink family with suitable operations and
attributes.
In both cases appropriate mechanisms are added to make for keys that
are used for chipset matching, and device drivers simply register
a notifier handler that is called on two occaisions:
1) When settings are changed.
2) Upon initial handler registry, to acquire the initial settings.