G'day flashrom'ers,
The reasoning is that a lot of board_enable changes would be required to allow for the drivers entry-point to be passed configuration and other data. The driver is a single exception to every other driver in the tree that either has a direct driver entry from the driver table (programmer_table) or via the specalised "internal" programmer that directs entry via a chipset_enable dispatch. It would be preferably for board_enable not to have a deep CFG going right though it to driver entry-points for one very specific case especially if the driver isn't even used anymore?
Interested to hear your thoughts or users?
Cheers,
Edward.