From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout.kundenserver.de ([217.72.192.73]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1dYSR4-0007p7-MA for ptxdist@pengutronix.de; Fri, 21 Jul 2017 09:33:18 +0200 Received: from idefix.home.lespocky.de ([79.205.217.47]) by mrelayeu.kundenserver.de (mreue101 [212.227.15.183]) with ESMTPSA (Nemesis) id 0MZUcf-1dJwO52emT-00LFh2 for ; Fri, 21 Jul 2017 09:33:12 +0200 Received: from falbala.home.lespocky.de ([192.168.243.94]) by idefix.home.lespocky.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1dYSQm-00019Q-Ma for ptxdist@pengutronix.de; Fri, 21 Jul 2017 09:33:11 +0200 Date: Fri, 21 Jul 2017 09:32:58 +0200 From: Alexander Dahl Message-ID: <20170721073257.GE1946@falbala.home.lespocky.de> MIME-Version: 1.0 Subject: [ptxdist] rc kernel from tarball 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="===============1124476845==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============1124476845== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vv4Sf/kQfcwinyKX" Content-Disposition: inline --vv4Sf/kQfcwinyKX Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, I tried to use the current v4.13-rc1 kernel today, but apparently this does not work out of the box just setting PTXCONF_KERNEL_VERSION to 4.13-rc1. On https://www.kernel.org/ you can get a gz packed tarball =66rom the URL https://git.kernel.org/torvalds/t/linux-4.13-rc1.tar.gz or if you go to the kernel.org cgit from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/snapshot= /linux-4.13-rc1.tar.gz but both are gz, not xz. Additionally looking at rules/kernel.make there seems to be some script magic to get a kernel tarball from some mirror, so I can not simply add one of those URLs to the make rule. I will use a custom kernel tree like described in doc chapter 6.1 for now, but I would appreciate a simpler solution for using rc kernels just from a tarball. Any hints on that? 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 *** --vv4Sf/kQfcwinyKX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJZca4pAAoJEDStzQByIVzGSD8P/05EuUAYFPRjxU4udq1PEsuY RJfaElOrQAnJU2Wzu39aTi51e7+QWNNG/yyCxB/sr6bQ2So0nNnKZv9AMHE08Crh +B8dES2o64jXh4MvpTHdsAP3nUJAwEKoFy0AkwUw24ZUq8dDGPq81xyjAGEDEtif w4KBEvLrho/C3y8AEW8hdJ+SnR8P2yaBQ6RnUZBNwVLFd5zaklkmdZ83+Ci6GLo8 MUrvDGgqmScrLNqDtJ63o0vjrTSrFWAmrx2Dl+t/hcauEnWbmgOpVesmu8+YeubK 1hqlVTD6Nfs2nciKvuLBYE2wOIyyJ5VHdZEo6KddQfElNOPjjc9X/IATkjMtq4Zy mDNFq+YxLpO3E566AIt6nbPUXD3ViRu2HjTVPwHNlYL2FYQBS15wvfK4y79Yvajv HiiXMLwtueMk6+3rsie8q6DLJxQEqBF08/O2nb+m+NOr3sA8/YgFCPLO6nOVQWR4 yUVrRP6As2pi2992LjW1eShj/HT4bKNj5TUhYHJ1l7lv+SAyc2B7ns/5NCRSkfnm iWkJEd1bz/0fp7nsJtszMxmqQ6FYq70WtkuwiiiIBY0ezAdY2loslpUdSAKOQv7z BhrAeMXNpCyP5BtTuKrT1yFV5/SEc+TEW+Bf8HKvQkjvRbUyeYcLE1Ge5/pvL2HJ Yro19k+22RusbdkpGJ3k =PkFS -----END PGP SIGNATURE----- --vv4Sf/kQfcwinyKX-- --===============1124476845== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1124476845==--