Dear Ben Warren, In message <4a68e0c1.2000...@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 -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Little known fact about Middle Earth: The Hobbits had a very sophi- sticated computer network! It was a Tolkien Ring... _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot