From: safae ouajih <souajih@baylibre.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de, glaroque@baylibre.com,
mkorpershoek@baylibre.com, khilman@baylibre.com,
r.stratiienko@gmail.com, sean.anderson@seco.com
Subject: Re: [PATCH 00/17] Support android boot image v3/v4
Date: Fri, 6 Jan 2023 12:04:27 +0100 [thread overview]
Message-ID: <e509a63e-6043-048d-5934-df2da9d30249@baylibre.com> (raw)
In-Reply-To: <CAPnjgZ2Tra6LukHg8U51iWoLUozaLqypbOCEMC1=K2_XA7KbJg@mail.gmail.com>
On 04/01/2023 21:01, Simon Glass wrote:
> Hi Safae,
>
> On Wed, 4 Jan 2023 at 02:02, safae ouajih <souajih@baylibre.com> wrote:
>>
>> On 30/12/2022 02:48, Tom Rini wrote:
>>> On Sat, 26 Nov 2022 17:59:14 +0100, Safae Ouajih wrote:
>>>
>>>> * This is based on Roman Stratiienko's work to support boot image header version 3 and 4.
>>>>
>>>> * This supports the new boot image headers v3, v4 and bootconfig feature.
>>>> https://source.android.com/docs/core/architecture/bootloader/boot-image-header
>>>> https://source.android.com/docs/core/architecture/bootloader/implementing-bootconfig
>>>>
>>>> - Tested on Amlogic Khadas vim3l, a reference board for Android Open Source Project
>>>> https://www.khadas.com/vim3l
>>>>
>>>> [...]
>>>
>>> This series causes the test/py/tests/test_android/test_abootimg.py tests to
>>> fail:
>>> FAILED test/py/tests/test_android/test_abootimg.py::test_abootimg - ValueError: U-Boot exite...
>>> and likely that test needs to be expanded for these new formats too.
>>>
>>
>> Hello Tom,
>>
>> Thank you for reporting the failure. This will be fixed in a v2.
>
> Please also update the test as requested.
>
> Regards,
> Simon
Hello Simon,
I am working on the test update. This will be in a v2.
Thank you.
Best Regards,
--
Safae
prev parent reply other threads:[~2023-01-06 11:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 16:59 [PATCH 00/17] Support android boot image v3/v4 Safae Ouajih
2022-11-26 16:59 ` [PATCH 01/17] android: boot: rename andr_img_hdr -> andr_boot_img_hdr_v0_v1_v2 Safae Ouajih
2022-11-28 16:08 ` Sean Anderson
2022-11-29 11:07 ` Safae Ouajih
2022-11-26 16:59 ` [PATCH 02/17] android: boot: support vendor boot image in abootimg Safae Ouajih
2022-11-26 16:59 ` [PATCH 03/17] android: boot: replace android_image_check_header Safae Ouajih
2022-11-26 16:59 ` [PATCH 04/17] android: boot: add boot image header v3 and v4 structures Safae Ouajih
2022-11-26 16:59 ` [PATCH 05/17] android: boot: add documentation for boot image header v3/v4 structure Safae Ouajih
2022-11-28 16:12 ` Sean Anderson
2022-11-26 16:59 ` [PATCH 06/17] android: boot: kcomp: support andr_image_data Safae Ouajih
2022-11-26 16:59 ` [PATCH 07/17] android: boot: move to andr_image_data structure Safae Ouajih
2022-11-26 16:59 ` [PATCH 08/17] android: boot: content print is not supported for v3, v4 header version Safae Ouajih
2022-11-26 16:59 ` [PATCH 09/17] android: boot: boot image header v3, v4 do not support recovery DTBO Safae Ouajih
2022-11-26 16:59 ` [PATCH 10/17] android: boot: add vendor boot image to prepare for v3, v4 support Safae Ouajih
2022-11-26 16:59 ` [PATCH 11/17] android: boot: update android_image_get_data to support v3, v4 Safae Ouajih
2022-11-26 16:59 ` [PATCH 12/17] android: boot: ramdisk: support vendor ramdisk Safae Ouajih
2022-11-26 16:59 ` [PATCH 13/17] android: boot: support extra command line Safae Ouajih
2022-11-26 16:59 ` [PATCH 14/17] drivers: fastboot: zImage flashing is not supported for v3, v4 Safae Ouajih
2022-11-26 16:59 ` [PATCH 15/17] android: boot: support boot image header version 3 and 4 Safae Ouajih
2022-11-26 16:59 ` [PATCH 16/17] lib: support libxbc Safae Ouajih
2022-11-28 16:02 ` Sean Anderson
2022-11-26 16:59 ` [PATCH 17/17] android: boot: support bootconfig Safae Ouajih
2022-11-28 9:43 ` [PATCH 00/17] Support android boot image v3/v4 Mattijs Korpershoek
2022-12-04 21:16 ` Simon Glass
2022-12-30 1:48 ` Tom Rini
2023-01-04 9:02 ` safae ouajih
2023-01-04 20:01 ` Simon Glass
2023-01-06 11:04 ` safae ouajih [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e509a63e-6043-048d-5934-df2da9d30249@baylibre.com \
--to=souajih@baylibre.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=mkorpershoek@baylibre.com \
--cc=r.stratiienko@gmail.com \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox