No subject

code copmplexity explode when it comes to handling different SoC and
board combinations within a single U-Boot image. I would like to point
out that we should not go the way that is currently being used in the
ARM Linux kernel. We will not duplicate the MACH_ID concepts used
there and the resulting code methods. Instead, when we need to add
such flexible configuration, we will go the device tree way. 

I hope such comment still comes in time to help you taking the right
turns.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
panic: kernel trap (ignored)