Re: [ptxdist] [PATCH 1/2] kernel: pass loadaddr for building uImage

2016-11-28 Thread Michael Olbrich
On Mon, Nov 28, 2016 at 11:21:31AM +0100, Alexander Dahl wrote: > On newer kernels (4.x ?) kernel build fails when building an uImage > unless you provide LOADADDR as kernel make var, which is put in the > resulting uImage header. You could append it to > PTXCONF_KERNEL_EXTRA_MAKEVARS but this

[ptxdist] systemd 232

2016-11-28 Thread Clemens Gruber
Hi, did you already start working on updating systemd to version 232? Thanks, Clemens PS: Any comments on the nginx patch yet? :) ___ ptxdist mailing list ptxdist@pengutronix.de

Re: [ptxdist] [PATCH] nginx: new package

2016-11-28 Thread Juergen Borleis
Hi Clemens, just one comment for now: On Sunday 06 November 2016 20:12:18 Clemens Gruber wrote: > [...] > +if NGINX > + > +menu "Base settings " > + > +config NGINX_OPENSSL > + bool > + prompt "OpenSSL support" > + help > + Include OpenSSL support, which is

[ptxdist] [PATCH 1/2] kernel: pass loadaddr for building uImage

2016-11-28 Thread Alexander Dahl
On newer kernels (4.x ?) kernel build fails when building an uImage unless you provide LOADADDR as kernel make var, which is put in the resulting uImage header. You could append it to PTXCONF_KERNEL_EXTRA_MAKEVARS but this would be just a workaround. This patch extends the menu if uImage is

[ptxdist] [PATCH 2/2] image_kernel: new options for "appended DT" images

2016-11-28 Thread Alexander Dahl
On a platform where we can not load a separate device tree binary blob with the old bootloader we use the kernel option CONFIG_ARM_APPENDED_DTB to load the DT blob. This requires creating a zImage, concatenate the dtb file and put this back to an uImage. This patch extends the image generation

[ptxdist] [PATCH 0/2] kernel image generation extensions

2016-11-28 Thread Alexander Dahl
Hei hei, for an older at91sam9g20 based platform I recently updated the kernel from ancient without DT to 4.x with DT. This patch series has two patches. The first is quite small and I consider it useful for everybody. The second depends on the first and covers a special usecase and may not be of