X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 3F003DC00DB for ; Tue, 27 Jan 2015 07:07:37 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id pv20so11632470lab.7 for ; Mon, 26 Jan 2015 23:07:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=k4MxWMT4q0JhWkK0P2HpoCs1Pzhr6QSQiqQZKxElPLQ=; b=Q8zXG6GqLOCycnYjGdKAjrGeq0T0Cvo0ej9kkyiolEPvuBNxh9h2RrGypOQmwd88VE mBJCXclRasrNr27FHs8bP921/WvGpL944SN6pBIoJtato98Rj6Ke+evWre49AgJkiiIF Qs1yXB96H6TGbnyb6JymwaA7IOH9ONUJrMVZZ+eAvfJANOBZarQmtFn1Q4g/BBCwrPV6 83y1jgbCD76vtJ61ahu1obQ4+mOof0FaCTLwgV/Y8D+OCS70y21aOAFIJpXaHj7zIfyY brmhlUyoeaUnnbEkoOkQPOBVzhWdgK6H6ALzEFu5ksa9+et9jLyYMy0yfXO8hVuzm/EW ELHQ== X-Received: by 10.112.172.167 with SMTP id bd7mr2362365lbc.14.1422342455188; Mon, 26 Jan 2015 23:07:35 -0800 (PST) Received: from vostro ([83.145.235.202]) by mx.google.com with ESMTPSA id k1sm142898laf.19.2015.01.26.23.07.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jan 2015 23:07:34 -0800 (PST) Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= Date: Tue, 27 Jan 2015 09:07:08 +0200 From: Timo Teras To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] Alpine ARM images Message-ID: <20150127090708.75914d8d@vostro> X-Mailer: Claws Mail 3.11.0 (GTK+ 2.24.25; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I'm hoping that we can start generating ARM-images for other boards than Raspberry Pi soon. It seems this is a bit messy area, and many other distros just have a wiki + separate downloads for the boot loader. Though, I would like us to ship a single downloadable tarball. Also preparing the boot media seems to vary board by board. E.g. wandboard loads bootloader from fixed sectors of MMC, where as e.g. cubieboard seems to load it from the first partition (FAT). I've made now a test image with u-boot for wandboard (it also has cubieboard u-boot, but it's u-boot script is not updated for alpine). DTBs are for a bunch of boards, and it's a grsec kernel from edge. apks are from 3.1.1 release. http://dev.alpinelinux.org/~tteras/alpine-uboot-3.1.1-test-armhf.rpi.tar.gz If you have wandboard, I'd be happy to hear feedback. This is what I'm currently running on our wandboard builder. Patches to support more boards (kernel config and u-boot package/script) are welcome. I'm also wondering how we should do this in official releases. Just ship all u-boot images and dtbs in the tarball, and make setup-bootable to install also u-boot for arm? Other suggestions? /Timo --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---