From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AB6DEC05027 for ; Wed, 8 Feb 2023 08:54:35 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id C4F3D85D8C; Wed, 8 Feb 2023 09:54:32 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=baylibre.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (2048-bit key; unprotected) header.d=baylibre-com.20210112.gappssmtp.com header.i=@baylibre-com.20210112.gappssmtp.com header.b="nrIYbhWz"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 0491085E68; Wed, 8 Feb 2023 09:54:30 +0100 (CET) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id B07D38586B for ; Wed, 8 Feb 2023 09:54:26 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=none (p=none dis=none) header.from=baylibre.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=mkorpershoek@baylibre.com Received: by mail-wm1-x32f.google.com with SMTP id k8-20020a05600c1c8800b003dc57ea0dfeso916796wms.0 for ; Wed, 08 Feb 2023 00:54:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=YpnkONu4MqIAEKNtBOqzfkJG9ppgo3/NZkI2Rm0wUIM=; b=nrIYbhWzso2UfWvnB6RY4+xn/HFlEyuEhcI4DQXCVzKAVeWkyMuLSRh2u2FGtCZUkc ivDu3TnpkyEy3KtQ2Catl1aXw8caSpCbkpUSpkIP91D7U3hkT6hIabxkGSPz7GqPRAtz 9RoZ8OHOEQEE4DDTLA1zf5U+PJt+A0scX3uCaR/br+oAiS5SRuafkrO7pRviSiNje6HQ ZtJnIufMxb6h7/wpOprntuNSujcuxu363K5rRvNF3hDjPsc7m4w1R1THvB8BdM4m8wwH ACfO3G0t9HOzl7xazBBBTKiszmthiUWMRVDAG0L0QM+C7Il870+jCHj2HNSZ1+dB0Tpe ASkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YpnkONu4MqIAEKNtBOqzfkJG9ppgo3/NZkI2Rm0wUIM=; b=TJVLUJeFXk83h2+kH4dSOtvn8a3OHYo3K1WyYtbR3y2A07uhn+cQ/+ZuTFZSR0Bkb5 i/C9jgdvrZBYmshetkf5aak8hVFOd17Tp/53Wl2ayWvrIE12tZiTmqNHO2+zjZudYXKs ujsiZ74Cqh9OBW0O8VJ4oInlpFCr+8gMZizNsBWrCNxkgUazJYaa1ODnREV6kpkHVnMJ h9jJ1xE81MgNTtMl6nzoKJMfLsh2JDwxfmHCOhAHinNa97S9GCTIVMS2EdlsvJs9JKBn uoODgYxCN3LU003p2C52oSFTUyBhIN4lzIuOgoqlBRsgh+6RuS7Ofkary+QIp9//Ioo6 REiw== X-Gm-Message-State: AO0yUKV5YAxQGvCRuYG2Slb24G2KiNKsqqNK76zG/yHpDYDAZtta/sAm J3BnO0C1zypiHWAyGF7lgIxUZw== X-Google-Smtp-Source: AK7set8k75lr0ZmtfuQAA6qC7+41v+6+ZSf3vOXRBGzjVquB73GpOTa1SLEfH8/DMElsF3faLVliPg== X-Received: by 2002:a05:600c:1d8b:b0:3dc:198c:dde with SMTP id p11-20020a05600c1d8b00b003dc198c0ddemr5553340wms.41.1675846466178; Wed, 08 Feb 2023 00:54:26 -0800 (PST) Received: from localhost ([2a01:cb19:85e6:1900:2bf7:7388:731d:c4e1]) by smtp.gmail.com with ESMTPSA id p24-20020a05600c1d9800b003dd1bd0b915sm1235524wms.22.2023.02.08.00.54.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Feb 2023 00:54:25 -0800 (PST) From: Mattijs Korpershoek To: Safae Ouajih , sjg@chromium.org Cc: u-boot@lists.denx.de, sean.anderson@seco.com, r.stratiienko@gmail.com, glaroque@baylibre.com, khilman@baylibre.com Subject: Re: [PATCH v3 17/19] doc: android: add documentation for v3,v4 boot image header In-Reply-To: <20230205235021.355410-18-souajih@baylibre.com> References: <20230205235021.355410-1-souajih@baylibre.com> <20230205235021.355410-18-souajih@baylibre.com> Date: Wed, 08 Feb 2023 09:54:25 +0100 Message-ID: <87v8kc5ygu.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean On lun., f=C3=A9vr. 06, 2023 at 00:50, Safae Ouajih = wrote: > Update the Android documentation to describe version 3 and 4 of boot > image header. > > Signed-off-by: Safae Ouajih > --- Reviewed-by: Mattijs Korpershoek > doc/android/boot-image.rst | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/doc/android/boot-image.rst b/doc/android/boot-image.rst > index 71db02521b..c719b4d711 100644 > --- a/doc/android/boot-image.rst > +++ b/doc/android/boot-image.rst > @@ -27,11 +27,21 @@ next image headers: > * v2: used in devices launched with Android 10; adds ``dtb`` field, which > references payload containing DTB blobs (either concatenated one after= the > other, or in Android DTBO image format) > +* v3: used in devices launched with Android 11; adds ``vendor_boot`` par= tition > + and removes the second-stage bootloader and recovery image support. Th= e new > + ``vendor_boot`` partition holds the device tree blob (DTB) and a vendo= r ramdisk. > + The generic ramdisk in ``boot`` partition is loaded immediately follow= ing > + the vendor ramdisk. > +* v4: used in devices launched with Android 12; provides a boot signatur= e in boot > + image header, supports multiple vendor ramdisk fragments in ``vendor_b= oot`` > + partition. This version also adds a bootconfig section at the end of t= he vendor > + boot image, this section contains boot configuration parameters known = at build time > + (see [9]_ for details). >=20=20 > v2, v1 and v0 formats are backward compatible. >=20=20 > The Android Boot Image format is represented by > -:c:type:`struct andr_img_hdr ` in U-Boot, and can be seen = in > +:c:type:`struct andr_image_data ` in U-Boot, and can be= seen in > ``include/android_image.h``. U-Boot supports booting Android Boot Image = and also > has associated command >=20=20 > @@ -153,3 +163,4 @@ References > .. [6] :doc:`avb2` > .. [7] https://source.android.com/devices/bootloader > .. [8] https://connect.linaro.org/resources/san19/san19-217/ > +.. [9] https://source.android.com/docs/core/architecture/bootloader/impl= ementing-bootconfig > --=20 > 2.34.1