[U-Boot] [PATCH v4 10/11] Add u-boot-pad.bin target to the Makefile

[Tom Rini <trini@ti.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/21/12 09:26, Jos? Miguel Gon?alves wrote:
> 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.7000209@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?

Having said I'm terrible at names already, Scott suggested that one
and Wolfgang didn't object, so yes, you add that target and the more
general problem falls to me.  I'll just outsource the naming parts of
it :)

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQXJf5AAoJENk4IS6UOR1W8XwQAJ1KTaHrr2F0w1/qvFZdIIOM
JJz9tWhYTiLRvrWhJfIgx3kwtflxzw6JQuLfwhOryf5/5W43ySRYPb+vHl1PBwq4
RlhwVdRUpPBZPWhuSrgajIi4P8z4OkaaW7v+YhkrNh1QQCbTQMO/RWYa66Xou6UJ
hAsnCKJkTqOjpCxc2JeYL/hK/EUba7o4zYAU1H8sdVtch4hOvAJEMT9C/D6/Vxsq
FyNB0+IMcomYavimjbTPLIVRUCpr2lt/8l5TTIPhjnqXUbSetrgysLn75ofKBU7Q
db/cf+Ry2bFTGnQ8OdPU2FCwsqA905EU/WCjjX6/yUwRR3OpnJVkPi0DTqvEJ0YR
gpADl5yy6VmCcZXRnPa1CGRyKv3vbRk333W4X2FgNCUES98BUM8L/qbbd29Tb5I7
KiaF6s5YoeDVCqMW7ER9a+BvvzD2YlHHcO4PwgOPu+xdkGbWxosxdKOgWRmTjR8X
HQnuzwqT0X36unC5HpLxmzqHHxTomP02dil7eT+XHMNA6d/Jd61ByZvd2Lk/getw
gALsACCcAZN/WtpA1s6DGYBX2/g/8pMul5Hf3tbAFseKumqeqd+ufcAEPgAQ/nKV
8sUz2DtFnmRsaukTkCl3aFexPr1upbQJh/EkopLq3uuHwKRxWymP2AQ/AAML7kYY
94pdwweLvRpb3AYvS5ZJ
=xeXW
-----END PGP SIGNATURE-----