From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout.kundenserver.de ([217.72.192.74]) by metis.ext.pengutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cC1nA-000327-PY for ptxdist@pengutronix.de; Wed, 30 Nov 2016 11:07:08 +0100 Received: from idefix.home.lespocky.de ([178.24.63.108]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPSA (Nemesis) id 0MKcX1-1cAeTh2Eel-001wdM for ; Wed, 30 Nov 2016 11:07:03 +0100 Received: from falbala.home.lespocky.de ([10.182.63.94]) by idefix.home.lespocky.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1cC1mh-0003zm-I8 for ptxdist@pengutronix.de; Wed, 30 Nov 2016 11:06:52 +0100 Date: Wed, 30 Nov 2016 11:06:33 +0100 From: Alexander Dahl Message-ID: <20161130100628.GC9535@falbala.home.lespocky.de> References: <1480328492-29475-1-git-send-email-post@lespocky.de> <1480328492-29475-2-git-send-email-post@lespocky.de> <20161128164626.dz57wdql74a64nts@pengutronix.de> <54014cd5-74ef-3901-9459-953cb6b80d57@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <54014cd5-74ef-3901-9459-953cb6b80d57@pengutronix.de> Subject: Re: [ptxdist] [PATCH 1/2] kernel: pass loadaddr for building uImage List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0511820122==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============0511820122== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B4IIlcmfBL/1gGOG" Content-Disposition: inline --B4IIlcmfBL/1gGOG Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, On Tue, Nov 29, 2016 at 10:04:19AM +0100, Marc Kleine-Budde wrote: > What happens if you build a older kernel and don't configure > PTXCONF_KERNEL_LOADADDR via ptxdist? Does it break while it used to work > with an older ptxdist? If I understood you correctly, that's not the case. Older kernels don't need this passed, but somehow determine it. For example with ptxdist 2015.10 and kernel 2.6.36.4 for at91sam9g20ek the loadaddr in the final uImage is 0x20008000. The code for generating the image is in arch/arm/boot/Makefile but I could not find out, where the actual address comes from, if I don't pass LOADADDR. If I pass it (e.g. with the backported patch) the address I pass is used (tried this with another address). So while LOADADDR needs to be passed for newer kernels, the build is successful on older kernels with or without passing LOADADDR. Without it is somehow determined by the kernel make files I suppose. When passing LOADADDR the result is the same as for newer kernels. Does this answer your question? =CD'm not sure how the patch would have to be extended, though. Greets Alex --=20 =BBWith the first link, the chain is forged. The first speech censured,=20 the first thought forbidden, the first freedom denied, chains us all=20 irrevocably.=AB (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 *** --B4IIlcmfBL/1gGOG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJYPqSjAAoJEDStzQByIVzG7ywP/30TDb8+p5t/v7d+AuMzpy+i +KUPZaLgK3lTOHrocwMX2+OOTUeOf/G8SonF3ewB03oUVhpCqoeY8WZlJyWmsrFw eErS36cf/ztVDeLjfOu+6OP0vygmULKCrtsQoQ2la8VgxS3USypGbi3Tdhe1Hv1s Oa82GhUHjbfXzY1yWAIKnushW6fUEpFUwjy7beT5UY0LEQZgbvFVkR883YijmLBI iS3NzTO1Vc029VxmMz8kragdqxtaBQDlQc1BrMJHaUETwj1lRnns1EQQErc1vNNz PJ70IdWle5c1/gjbFVcV9CSZPr9JOfDRo2RCXn0qIonP8AkPzdgGNeof3OKWxxLS xGLIuntJ4rKcVqMN/iqV0a4U+2YTp4YY64U/2wZ26L3K8aUZzLeCYxPjEsU3eXnn 9LS7hg5OzZHAdkgUJi9gY4RZ1tNM9LTujSTtrwS58RpiwzUimkR99DZpziNZcpU1 f2j+eODfbSwro/l58kd/27d9L3qWvBWoSTc8+sWHy4UAkHLzBVd9Wi06g79tlv81 hV5CXmePqCmpwmIgbYyfBMx9mMlJGwozkNsxLrTfP06MVqzbaogBh8tIUkE6IGKe xvEDfy2zQsPdV9sbEAAAt+Q8RCb2vdwHoHVKU4AyYs0QA90BLLrmasWMvKNYc6+s VqF0fCqC1592PXvKPel1 =yM1X -----END PGP SIGNATURE----- --B4IIlcmfBL/1gGOG-- --===============0511820122== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0511820122==--