On Wed, Sep 19, 2001 at 02:10:38PM -0400, Dan Malek wrote: > > Well, do you forsee the need to put in board-specific defines? > > This isn't the right way. If you notice the way the ports work, > everything 4xx (or 8xx, or 6xx, or whatever), include the single > header file, in this case ppc4xx.h. This include file will select > the proper board specific file. The board specific file, contains, > well, the stuff specific to a board.
Er, yes. But if there's nothing specific to the CPCI405, why add in an empty file and the #ifdef CONFIG_CPCI405 #include <asm/cpci405.h> /* Empty */ #endif in ppc4xx.h? -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
