From: Michal Simek <michal.simek@amd.com>
To: Simon Glass <sjg@chromium.org>, Michal Simek <monstr@monstr.eu>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Tom Rini <trini@konsulko.com>,
Julius Werner <jwerner@chromium.org>,
Dan Handley <dan.handley@arm.com>,
Jose Marinho <jose.marinho@arm.com>,
Bin Meng <bmeng.cn@gmail.com>, Nikhil M Jain <n-jain1@ti.com>
Subject: Re: [PATCH 00/14] bloblist: Align to firmware handoff
Date: Mon, 30 Oct 2023 08:53:17 +0100 [thread overview]
Message-ID: <c75a188b-0bfc-44de-b4a2-0efd2dcb7f0e@amd.com> (raw)
In-Reply-To: <CAPnjgZ0hYHxc6HKd2wMu4jdTtDyNDxRmcSDMCs6azNwr=tstjA@mail.gmail.com>
On 10/28/23 07:35, Simon Glass wrote:
> Hi Michal,
>
> On Wed, 6 Sept 2023 at 12:22, Michal Simek <monstr@monstr.eu> wrote:
>>
>> Hi Simon,
>>
>> út 25. 7. 2023 v 23:36 odesílatel Simon Glass <sjg@chromium.org> napsal:
>>>
>>> In moving from v0.8 to v0.9 the Firmware Handoff specification made some
>>> changes, including:
>>>
>>> - Use a packed format for headers to reduce space
>>> - Add an explicit alignment field in the header
>>> - Renumber all the tags and reduce their size to 24 bits
>>> - Drop use of the blob header to specify alignment, in favour of a
>>> 'void' blob type
>>>
>>> This series attempts to align to that specification, including updating
>>> the API and tests. It is likely that refinements will be made as other
>>> projects implement the spec too.
>>>
>>> As before the code is dual-licensed, to permit use in projects with a
>>> permissive license.
>>>
>>>
>>> Simon Glass (14):
>>> bloblist: Update the tag numbering
>>> bloblist: Adjust API to align in powers of 2
>>> bloblist: Change the magic value
>>> bloblist: Set version to 1
>>> bloblist: Access record hdr_size and tag via a function
>>> bloblist: Drop the flags value
>>> bloblist: Drop the spare values
>>> bloblist: Change the checksum algorithm
>>> bloblist: Checksum the entire bloblist
>>> bloblist: Handle alignment with a void entry
>>> bloblist: Reduce blob-header size
>>> bloblist: Reduce bloblist header size
>>> bloblist: Add alignment to bloblist_new()
>>> bloblist: Update documentation and header comment
>>>
>>> arch/x86/lib/tables.c | 3 +-
>>> common/bloblist.c | 102 ++++++++++++++++++++-------------
>>> doc/develop/bloblist.rst | 4 +-
>>> include/bloblist.h | 121 +++++++++++++++++++--------------------
>>> test/bloblist.c | 53 +++++++++--------
>>> 5 files changed, 152 insertions(+), 131 deletions(-)
>>>
>>> --
>>> 2.41.0.487.g6d72f3e995-goog
>>>
>>
>> Would it be also possible to align names in the bloblist_hdr structure?
>> magic->signature
>> align_log2->alignment
>> alloced->size
>> size->max_size
>>
>> The same is for bloblist_rec.
>
> OK. I am not sure I like the size/max_size thing so I filed an issue for that.
Fine for me. At the end they should match with spec. Update in spec is fine.
>>
>> I don't know the history but spec is about transfer list and transfer entry.
>> Do you plan to rename it to avoid confusion?
>
> I don't really like transfer_list_xxx as an API. It is too
> long-winded. We used that name since it is unique and descriptive as
> to its purpose. But I think that 'bloblist' is a better name in the
> code base. Perhaps we could use xferlist instead of bloblist?
xferlist sounds good to me.
M
prev parent reply other threads:[~2023-10-30 7:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 21:36 [PATCH 00/14] bloblist: Align to firmware handoff Simon Glass
2023-07-25 21:36 ` [PATCH 01/14] bloblist: Update the tag numbering Simon Glass
2023-07-26 20:16 ` Julius Werner
2023-07-28 8:51 ` Ilias Apalodimas
2023-07-28 21:56 ` Julius Werner
2023-08-02 10:14 ` Jose Marinho
2023-07-25 21:36 ` [PATCH 02/14] bloblist: Adjust API to align in powers of 2 Simon Glass
2023-08-02 10:24 ` Jose Marinho
2023-07-25 21:36 ` [PATCH 03/14] bloblist: Change the magic value Simon Glass
2023-07-25 21:36 ` [PATCH 04/14] bloblist: Set version to 1 Simon Glass
2023-07-25 21:36 ` [PATCH 05/14] bloblist: Access record hdr_size and tag via a function Simon Glass
2023-07-25 21:36 ` [PATCH 06/14] bloblist: Drop the flags value Simon Glass
2023-07-25 21:36 ` [PATCH 07/14] bloblist: Drop the spare values Simon Glass
2023-07-25 21:36 ` [PATCH 08/14] bloblist: Change the checksum algorithm Simon Glass
2023-07-25 21:36 ` [PATCH 09/14] bloblist: Checksum the entire bloblist Simon Glass
2023-07-25 21:36 ` [PATCH 10/14] bloblist: Handle alignment with a void entry Simon Glass
2023-07-26 20:17 ` Julius Werner
2023-07-25 21:36 ` [PATCH 11/14] bloblist: Reduce blob-header size Simon Glass
2023-07-26 20:20 ` Julius Werner
2023-07-25 21:36 ` [PATCH 12/14] bloblist: Reduce bloblist header size Simon Glass
2023-08-02 10:15 ` Jose Marinho
2023-08-02 21:31 ` Simon Glass
2023-07-25 21:36 ` [PATCH 13/14] bloblist: Add alignment to bloblist_new() Simon Glass
2023-07-26 20:20 ` Julius Werner
2023-07-25 21:36 ` [PATCH 14/14] bloblist: Update documentation and header comment Simon Glass
2023-07-26 20:55 ` Julius Werner
2023-09-06 12:22 ` [PATCH 00/14] bloblist: Align to firmware handoff Michal Simek
2023-10-28 5:35 ` Simon Glass
2023-10-30 7:53 ` Michal Simek [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=c75a188b-0bfc-44de-b4a2-0efd2dcb7f0e@amd.com \
--to=michal.simek@amd.com \
--cc=bmeng.cn@gmail.com \
--cc=dan.handley@arm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jose.marinho@arm.com \
--cc=jwerner@chromium.org \
--cc=monstr@monstr.eu \
--cc=n-jain1@ti.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