From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Warren Date: Thu, 23 Jul 2009 15:14:25 -0700 Subject: [U-Boot] [PATCH 2/2] document network driver framework In-Reply-To: <20090723220650.74C9B832E416@gemini.denx.de> References: <4A5F6524.7040909@gmail.com> <1247965449-23375-2-git-send-email-vapier@gentoo.org> <20090723214946.GE9480@game.jcrosoft.org> <20090723220650.74C9B832E416@gemini.denx.de> Message-ID: <4A68E0C1.2000605@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > Dear Jean-Christophe PLAGNIOL-VILLARD, > > In message <20090723214946.GE9480@game.jcrosoft.org> you wrote: > >>> +And to control whether your driver is even enabled, you should use: >>> + CONFIG_SYS_NET_ >>> >> In my proposition CONFIG_SYS_ will be not use for driver enabling but for >> hardware specific information >> > > Enabling or disabling a driver i ssomething that a dumb user can do, > so it should be done using > > CONFIG_ > > 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 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? regards, Ben