From: Tom Rini Date: Wed, 6 May 2015 09:35:15 -0400 Subject: [U-Boot] loading environment from SATA In-Reply-To: <5633000.QZRW8OPHJ9@fnr-ben-pc> References: <47683292.Z98BvacQce@fnr-ben-pc> <5633000.QZRW8OPHJ9@fnr-ben-pc> Message-ID: <20150506133515.GO5267@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, May 06, 2015 at 07:20:20AM +0100, Ben Hewson wrote: > Hi Fabio, > > Sorry, kind of got side tracked a bit. > > Tom, in response to SATA off a PCI bus, that was my main concern with > just adding a SATA init. However after looking through the code I have > noticed that there is a CONFIG_SYS_EARLY_PCI_INIT which if declared > will call initr_pci before my initr_sata. Ho ever this got me to > thinking, would it be better to have someting like > CONFIG_SYS_EARLY_SATA_INIT and do > > > #if defined(CONFIG_CMD_SATA) && defined(CONFIG_SYS_EARLY_SATA_INIT) > initr_sata, > #endif Hmmm. I would condition it on CONFIG_CMD_SATA && CONFIG_ENV_IS_IN_SATA to start with and if we somehow have another early use for SATA we can always revisit. > Or is this just being too complicated. Is there a file some place > listing all of the various CONFIG_XXX and CONFIG_SYS_XXX ? There is not. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: