From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout.kundenserver.de ([212.227.126.131]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cjBPD-00049J-Q3 for ptxdist@pengutronix.de; Wed, 01 Mar 2017 22:03:27 +0100 Received: from idefix.home.lespocky.de ([178.24.120.227]) by mrelayeu.kundenserver.de (mreue004 [212.227.15.167]) with ESMTPSA (Nemesis) id 0MPt6U-1ceDJz3q5a-0053nC for ; Wed, 01 Mar 2017 22:03:21 +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 1cjBP2-0000Zv-Ef for ptxdist@pengutronix.de; Wed, 01 Mar 2017 22:03:20 +0100 Date: Wed, 1 Mar 2017 22:03:06 +0100 From: Alexander Dahl Message-ID: <20170301205717.GM17911@falbala.home.lespocky.de> References: MIME-Version: 1.0 In-Reply-To: Subject: Re: [ptxdist] ptxdist with iMX6 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="===============0737054272==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============0737054272== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zgY/UHCnsaNnNXRx" Content-Disposition: inline --zgY/UHCnsaNnNXRx Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote: > Is someone using ptxdist with iMX6 based targets? I know phytec used > ptxdist in the past but now they seem to be using Yocto instead. We have a phytec i.MX6 dev board at work. They shipped a ptxdist based BSP in the first place before they switched to ptxdist. I had Distrokit working with it, I guess when Linux 3.18 was bleeding edge, but did not manage to send it upstream. So in general i.MX6 works, I guess it's basically getting your bootloader and kernel config working? > Re. toolchain: Any recommended version of OSELAS.Toolchain? Best > settings to finetune for Cortex A9 + VFPv3 + NEON ? I would recommend the latest release v2016.06.1 and go with arm-v7a-linux-gnueabihf_gcc-5.4.0_glibc-2.23_binutils-2.26_kernel-4.6-sanit= ized.ptxconfig 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 *** --zgY/UHCnsaNnNXRx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJYtzcIAAoJEDStzQByIVzGMsEP/jYJ/tFN4tcsEW8gyRa5sh5U qzzGwSI2OV6LQoOmuceYxqs9zT2CE9P+137U/Gx0bXcf8kIcoBrsxUtnbjeJn2cJ 4BZFZUnaGQZTuM8/wGCuERMQyyfAyVIFUuWV5lqoewkBEZsVQz0PBuRdUZ1ZyeZH 53ktDJujX/ZH0mjvZ/FMFRABAqyqP84FgVvZ9BpEC34Bus4NR3xZ4pAEJQNde1Qy G9vHLoR9HH9C9YS/45i7ychrI03pVymNlJ65HKcDG+mmKnFlvu0PIVn3bnAVKSgN ntxmWbzN90BZyil5++2HSNWzSCfrj8SdB0eKGmM2Zu6XFUtFMgquYEnm2jZRlj0z jsaLnX/YifeqW2bq3ppbRnTDSQPF7M8fLQIfKTjmzaTq+wRWUxRvJ3R0hZeX8U3R l/eZuPWeVUGXCOIOmeulxgbpqPzYB9oiLHV8MNydQy0Vvptkmeti6WZif94GpYjH Y/iTRCUN9dZujm+Y8y+9uWPYoSWUJvG7XmqJTXWLz38NF4ypJFH+jKu3fabQSneI ER++u1FLVs49pgyylT9aF3Hf4VJy9I9PouxXQqDFfQerOCtyGqlwsQjGtyZZcIRa hGLqF1zZDqQ58SBJnXU5xGQx+UlcrCQ9Zh/sxejbP7XNIyJb++UHWKedDDbA7P8k G0Nf/dOzRjSs8vjE3M3j =XG2Z -----END PGP SIGNATURE----- --zgY/UHCnsaNnNXRx-- --===============0737054272== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0737054272==--