From patchwork Sat Jan 27 05:59:07 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bin Chen X-Patchwork-Id: 866711 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=lists.denx.de (client-ip=81.169.180.215; helo=lists.denx.de; envelope-from=u-boot-bounces@lists.denx.de; receiver=) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="S/xkIXdt"; dkim-atps=neutral Received: from lists.denx.de (dione.denx.de [81.169.180.215]) by ozlabs.org (Postfix) with ESMTP id 3zT4qf4kz1z9sPk for ; Sat, 27 Jan 2018 16:59:57 +1100 (AEDT) Received: by lists.denx.de (Postfix, from userid 105) id A1982C21FE4; Sat, 27 Jan 2018 05:59:47 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lists.denx.de X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_IN_DNSWL_BLOCKED, RCVD_IN_MSPIKE_H2, T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.0 Received: from lists.denx.de (localhost [IPv6:::1]) by lists.denx.de (Postfix) with ESMTP id BDA3EC21E52; Sat, 27 Jan 2018 05:59:44 +0000 (UTC) Received: by lists.denx.de (Postfix, from userid 105) id 19FD7C21E41; Sat, 27 Jan 2018 05:59:43 +0000 (UTC) Received: from mail-pf0-f196.google.com (mail-pf0-f196.google.com [209.85.192.196]) by lists.denx.de (Postfix) with ESMTPS id 6A0ACC21DA9 for ; Sat, 27 Jan 2018 05:59:42 +0000 (UTC) Received: by mail-pf0-f196.google.com with SMTP id i66so1551883pfd.7 for ; Fri, 26 Jan 2018 21:59:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=VhSQ2DJaNvWl3alD3lOP951O9xsfa7pU8Dv2GMln+QU=; b=S/xkIXdtCSbZSIoBAGmSKkstAFGI2i8F6jACWnVIGwu+YXzGrOS1lkCFhyraTGvjB/ 55Z10XLZzyOtK3w+s9fS/UykpEaDtR4Ujy/VtKiXsKPmKoohdE10QZK05saqJKyryMQo 0ZWXHKeo8sXv/IcVxqyjgUg9NGjqvEK0t2izU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=VhSQ2DJaNvWl3alD3lOP951O9xsfa7pU8Dv2GMln+QU=; b=cQ4ciaC+3rXAqefNpT4drQLT1pgok6aXjfSge/CoLWB440RxEDS2Nrz6f6dm+oTr1p fcFw4ZsCPCcP0/33m+sSh/CE7RUYYjRgXGUV3rw6LdWHZ2lFNUSNnGVpAWnk5mzO8Ttc /Lz6BzQXugTNbbc3H1heAtsDZBFhFxFMDoP+GgRfylic6+1+wDAb0gOkVBMK+2h4hw7y fAbk96gYqhrUfO3xIVpOhkjW627MT20IjwXLcA8Ui8RIKyhBawD0Pfb9QyM0IYQvQT3w BRKZycnl6g37HE0zsPTu8pvAND89CzlOnMZvNViszPkEQtAiJWG4V0qPV8d80z4G5WhP Xu2Q== X-Gm-Message-State: AKwxytfvWUXjNQEnunuaFaAHURMlu/0+8UDzoFY4eVYQpCAVIyCjzfVk S0aHlHHNfgaIHKpaznWlbtSQYTKonHQ= X-Google-Smtp-Source: AH8x227kLRMWcbl8399FKpkEN3KcY3Yz+YenaCm2cvHuojzbTZp8LgVj1nM5L8W9BEXkiaHA6RGIIQ== X-Received: by 10.101.99.131 with SMTP id h3mr15174873pgv.381.1517032780538; Fri, 26 Jan 2018 21:59:40 -0800 (PST) Received: from localhost.localdomain (c27-253-115-177.carlnfd2.nsw.optusnet.com.au. [27.253.115.177]) by smtp.gmail.com with ESMTPSA id 184sm18395035pfg.87.2018.01.26.21.59.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 26 Jan 2018 21:59:39 -0800 (PST) From: Bin Chen To: u-boot@lists.denx.de, trini@konsulko.com Date: Sat, 27 Jan 2018 16:59:07 +1100 Message-Id: <20180127055909.12962-1-bin.chen@linaro.org> X-Mailer: git-send-email 2.15.0 Cc: rob.herring@linaro.org Subject: [U-Boot] [PATCH 0/2] Android and arm64 improvement X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.18 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" I rebased the two patches submitted (quite )a while ago on top of current U-boot master fb4413295c765aa8c013650984dc2d908964c81d (and there were no conflicts). The first patch added the support of parsing the second area of Android image so that it can be used for good. On Poplar board, we are using that area for dtb. The first patch shouldn't impact any functionality since it is new. The second patch moves the booti_setup out of booti.c. It was the result of a discusion[1] how to better support the arm64 Android image. I have boot tested it on Poplar board[2] with additional patch[3] that is built on top of the booti. I have hacked version of using bootm but it seems quit mess up - need lots of changes in different places ("Shotgun Surgery") to handle Android specific and/or arm64 specific code. Now, I feel a separate bootandroid command might be a cleaner solution. That being said, the second patch doesn't depend on or impact any change we might have in the future for better Android support. [1] https://lists.denx.de/pipermail/u-boot/2017-July/297933.html [2] https://github.com/96boards-poplar/Documentation [3] https://github.com/pierrchen/u-boot/commit/8463e6177654026746161487d0f0bd8998bb7a5b Bin Chen (2): parse the second area of android image move booti_setup to arch/arm/lig/image.c arch/arm/lib/Makefile | 2 +- arch/arm/lib/image.c | 76 +++++++++++++++++++++++++++++++++++++++++ cmd/booti.c | 92 +++++++------------------------------------------- common/image-android.c | 19 +++++++++++ include/image.h | 11 ++++++ 5 files changed, 120 insertions(+), 80 deletions(-) create mode 100644 arch/arm/lib/image.c