From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Wed, 11 Feb 2009 17:57:15 -0500 Subject: [U-Boot] [PATCH 18/42] Blackfin: make sure autoconf.mk is generated early enough In-Reply-To: <20090211221638.53DC0832E893@gemini.denx.de> References: <1234246880-32438-1-git-send-email-vapier@gentoo.org> <200902111654.20726.vapier@gentoo.org> <20090211221638.53DC0832E893@gemini.denx.de> Message-ID: <200902111757.21416.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wednesday 11 February 2009 17:16:38 Wolfgang Denk wrote: > In message Mike Frysinger you wrote: > > > And you fail to explain why BF needs this, while all other > > > architectures don't. > > > > i explained it already when Ben asked. the processor variant is selected > > in the board config and the board config (and shared settings) can change > > based on that selection. and the top level build flags use that > > processor > > If you define the processor variant right at the beginning of the > board config file, then why would that not be visible in the > remainder of the board config so you'd have to re-run this? that's a string representation that defines (1) the variant and (2) the silicon revision. that gets turned into CFLAGS via -mcpu=... and the toolchain itself then sets up the proper defines which everything else uses. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090211/8732658a/attachment.pgp