Even if you hard-code addresses in the U-Boot image you would be violating the GPL. A non-GPL standalone application must be really what the name suggests: standalone. It gets only a very narrow, stricltly limited set of services - just enough to ger some early initialization and debugging done. All the rest, including drivers and services, mut be re-implemented in your own proprietary image.
Is there any way of passing some data from outside of u-boot to u-boot without violating the GPL? Should the data be released as part of GPL? So if u-boot accesses some memory the content of that memory outside of its control should be released as GPL? Looks odd..
-- View this message in context: http://u-boot.10912.n7.nabble.com/u-boot-command-for-standalone-application-... Sent from the U-Boot mailing list archive at Nabble.com.