| Message ID | 589093c285ba2ea7cac546779dc985ddd8cb5b17.1391432821.git.kibo@prevas.dk |
|---|---|
| State | Rejected |
| Delegated to: | Esben Haabendal |
| Headers | show |
Kim Bøndergaard <kibo@prevas.dk> writes: > LOADADDR required by newer kernels able to directly build uImage's In which cases is this needed? I believe it should normally be set up by kconfig in the kernel, and only needed when we run mkimage manually. If we can avoid it, we really don't want to keep this address in sync between kernel source and oe-lite recipe / configuration... /Esben > --- > classes/kernel.oeclass | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/classes/kernel.oeclass b/classes/kernel.oeclass > index 9ab7756..154285a 100644 > --- a/classes/kernel.oeclass > +++ b/classes/kernel.oeclass > @@ -132,8 +132,11 @@ do_compile_kernel () { > else > oe_runmake include/linux/version.h > fi > - oe_runmake ${USE_kernel_imagetype} > - > + if [ -n "$USE_kernel_uimage_loadaddress" ] ; then > + oe_runmake LOADADDR=$USE_kernel_uimage_loadaddress ${USE_kernel_imagetype} > + else > + oe_runmake ${USE_kernel_imagetype} > + fi > if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then > oe_runmake modules > else
diff --git a/classes/kernel.oeclass b/classes/kernel.oeclass index 9ab7756..154285a 100644 --- a/classes/kernel.oeclass +++ b/classes/kernel.oeclass @@ -132,8 +132,11 @@ do_compile_kernel () { else oe_runmake include/linux/version.h fi - oe_runmake ${USE_kernel_imagetype} - + if [ -n "$USE_kernel_uimage_loadaddress" ] ; then + oe_runmake LOADADDR=$USE_kernel_uimage_loadaddress ${USE_kernel_imagetype} + else + oe_runmake ${USE_kernel_imagetype} + fi if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then oe_runmake modules else