Dear Tom, In message <20140407174936.GJ23803@bill-the-cat> you wrote: > > > OK. So if this basically the same what we do when booting XIP from > > parallel NOR, then maybe we should rename CONFIG_NOR_BOOT into a more > > generic name, like CONFIG_XIP_BOOT ? > > Nope, not everything for NOR is required for QSPI nor correct, so we'll > still need NOR/QSPI boot options (CONFIG_ENV_IS_IN.. then > size/location).
I think CONFIG_ENV_IS_IN.. is an independent thing. Even when booting from NOR you can have the environment anywhere else. As for the differences between NOR and QSPI... IIRC we cannot execute any code directly on QSPI, we have to load it to some memory first, right? So QSPI is not much different from loading the code from any other storage device - or am I missing something? How is XIP from QSPI working? 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: w...@denx.de "No matter where you go, there you are..." - Buckaroo Banzai _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot