Hi Kyle, > On Sep 03, 2010, at 00:00, Peter Tyser wrote: > >> --- a/Makefile > >> +++ b/Makefile > >> @@ -2499,6 +2499,10 @@ P2020DS_36BIT_config \ > >> P2020DS_config: unconfig > >> @$(MKCONFIG) -t $(@:_config=) P2020DS ppc mpc85xx p2020ds freescale > >> > >> +HWW_1U_1A_36BIT_config \ > >> +HWW_1U_1A_config: unconfig > >> + @$(MKCONFIG) -t $(@:_config=) HWW_1U_1A ppc mpc85xx hww-1u-1a > >> exmeritus > >> + > > > > The new way to add a board is via boards.cfg. You shouldn't need to > > modify this Makefile. > > Is there some appropriate documentation on how boards.cfg is supposed to work?
Not that I'm aware of. Its a relatively recent change to U-Boot. > The latest u-boot.git still seems to have the P2020DS lines that I referenced > in "Makefile", and it has no references at all to "P2020DS" in the > "boards.cfg" file. It looks like the top-level Makefile is still required for boards that support multiple configs, eg 'make P2020DS_36BIT' will configure U-Boot to compile a 36-bit addressable U-Boot image while 'make P2020DS' will configure a 32-bit addressable U-Boot image, but they both use the same Makefile rule with some fancy parsing. So I guess if you have a need for both a 32 and 36bit version of U-Boot you'll to modify the Makefile like your original patch did unfortunately. If you don't need to support both U-Boot configs, you can go the route of other similar boards that are only in boards.cfg, eg P4080DS, P1022DS, XPedite5370, etc. Best, Peter _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
