Dear Ben Warren,
In message 4A68E0C1.2000605@gmail.com you wrote:
Enabling or disabling a driver i ssomething that a dumb user can do, so it should be done using
CONFIG_<DRIVERNAME>
as in CONFIG_E1000, CONFIG_EEPRO100, etc.
Fine with me, although I understand the argument that it doesn't convey enough information, especially when dealing with devices that are more obscure than Intel E1000. CONFIG_SYS_APE is definitely wrong, I think
I understand the argument, too.
But then I find it extremely useful to use the very same config names as Linux, and Linux uses CONFIG_E100, CONFIG_NATSEMI, CONFIG_NE2K_PCI, CONFIG_8139CP, CONFIG_TLAN, CONFIG_ATP, CONFIG_E1000, ...
CONFIG_NET_APE should be for networking features such as selectable protocols. Maybe a compromise if one is needed would be CONFIG_NETDEV_APE ? Or is it too verbose?
I think we should remain compatible with Linux here, too.
Best regards,
Wolfgang Denk