On 21-09-2012 17:13, Tom Rini wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/21/12 08:52, Wolfgang Denk wrote:
Dear José Miguel Gonçalves,
In message <505c21bb.7000...@inov.pt> you wrote:
It is very important to me that we do NOT include any
architectures, SoCs, or board specifc parts in the names
because this will cause major PITA for all kind of automatic
test suites etc.
To me this seems also a cleaner solution, as any end user, that
simply takes the u-boot sources and performs a make, would
easily find the appropriate file to burn on his boot media.
But in that case, as the NAND image format (for instance) is
architecture and/or SoC dependant, what do you suggest is to add
conditionals in the Makefile that adequate the 'u-boot-nand.bin'
file to the target SoC?
SoC specific make rules can probably be added to the respective SoC
specific makefiles, thus still avoiding to clutter the top level
Makefile with lots of conditionals.
Ideally? Yes, Possible today? Not sure. I have a hazy recollection
that it wasn't so easy when I tried adding some build rules to one of
the config.mk files. When I post SPI SPL for am335x support I'll try
again since for that I need to add a rule to generate a byte-swapped
MLO file. If that can go somewhere other than spl/Makefile that would
be nice (but needs to be visible to a number of TI SoCs is an issue).
So what is your suggestion for my patch?
Can I push it with a new "u-boot-with-spl.bin" target and you'll handle the
unification of all NAND targets later?
Best regards,
José Gonçalves
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
