From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
Simon Glass <sjg@chromium.org>, Lukasz Majewski <lukma@denx.de>,
Marek Vasut <marex@denx.de>,
Joe Hershberger <joe.hershberger@ni.com>,
Ramon Fried <rfried.dev@gmail.com>, Bin Meng <bmeng@tinylab.org>,
Ion Agorria <ion@agorria.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Harald Seiler <hws@denx.de>,
Sean Anderson <sean.anderson@seco.com>,
Heiko Schocher <hs@denx.de>,
Dmitrii Merkurev <dimorinny@google.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/5] Implement fastboot multiresponce
Date: Thu, 09 Nov 2023 11:59:58 +0100 [thread overview]
Message-ID: <87y1f78a4x.fsf@baylibre.com> (raw)
In-Reply-To: <94E7D060-9388-4888-B7FF-EE911A179B2C@gmail.com>
Hi Svyatoslav,
On jeu., nov. 09, 2023 at 11:01, Svyatoslav Ryhel <clamor95@gmail.com> wrote:
> 9 листопада 2023 р. 10:41:30 GMT+02:00, Mattijs Korpershoek <mkorpershoek@baylibre.com> написав(-ла):
>>Hi Svyatoslav, Ion,
>>
>>Thank you for these series.
>>
>>On mar., nov. 07, 2023 at 14:42, Svyatoslav Ryhel <clamor95@gmail.com> wrote:
>>
>>> Currently u-boot fastboot can only send one message back to host,
>>> so if there is a need to print more than one line messages must be
>>> kept sending until all the required data is obtained. This behavior
>>> can be adjusted using multiresponce ability (getting multiple lines
>>> of response) proposed in this patch set.
>>>
>>> Implementation of multiresponce leads to ability to dump content of
>>> console buffer which, with use of "oem run", allows to entirely avoid
>>> need in UART.
>>
>
> Hello Mattijs!
> Thank you for your suggestions and so rapid responce!
>
>>I'm happy to fastboot getvar all implemented since it's standardly
>>supported on Android phones.
>>
>>fastboot oem console seems like a nice debug tool as well when no
>>console is available.
>>
>>I do have some concerns with the series, mainly because the introduction
>>of the "MORE" byte response.
>>"MORE" is not part of the fastboot specification [1].
>>
>>However, that specification documents "TEXT", which, per my
>>understanding, should allow to send multiple responses as well.
>>
>>Could we implement this using "TEXT" instead ?
>
> I see no issues with replacing MORE with TEXT whatsoever.
>
> These patches were mainly developed and used for our internal development needs but since they served extremely well, I have decided to push them upstream so other developers could benefit as well.
Thank you for taking the time to upstream.
>
> If you have no other suggestions then swap more > text, please send your reviewed-by to patch and I will reload v2 with swap included.
I will do a more thorough review in the coming days, I wanted to get
feedback on MORE->TEXT first.
>
> Best regards,
> Svyatoslav R.
>
>>[1] https://android.googlesource.com/platform/system/core/+/master/fastboot/#transport-and-framing
>>
>>>
>>> Ion Agorria (5):
>>> fastboot: multiresponse support
>>> fastboot: implement "getvar all"
>>> commonn: console: introduce overflow and isempty calls
>>> lib: membuff: fix readline not returning line in case of overflow
>>> fastboot: add oem console command support
>>>
>>> boot/bootmeth_extlinux.c | 2 +-
>>> common/console.c | 17 +++++--
>>> doc/android/fastboot-protocol.rst | 3 ++
>>> doc/android/fastboot.rst | 1 +
>>> drivers/fastboot/Kconfig | 7 +++
>>> drivers/fastboot/fb_command.c | 52 +++++++++++++++++++++
>>> drivers/fastboot/fb_getvar.c | 75 +++++++++++++++++++++++++------
>>> drivers/usb/gadget/f_fastboot.c | 29 ++++++++++++
>>> include/console.h | 14 ++++++
>>> include/fastboot-internal.h | 7 +++
>>> include/fastboot.h | 9 ++++
>>> include/membuff.h | 5 ++-
>>> lib/membuff.c | 4 +-
>>> net/fastboot_udp.c | 25 ++++++++---
>>> test/ut.c | 9 ++--
>>> 15 files changed, 226 insertions(+), 33 deletions(-)
>>>
>>> --
>>> 2.40.1
next prev parent reply other threads:[~2023-11-09 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 12:42 [PATCH v1 0/5] Implement fastboot multiresponce Svyatoslav Ryhel
2023-11-07 12:42 ` [PATCH v1 1/5] fastboot: multiresponse support Svyatoslav Ryhel
2023-11-14 9:21 ` Mattijs Korpershoek
2023-11-07 12:42 ` [PATCH v1 2/5] fastboot: implement "getvar all" Svyatoslav Ryhel
2023-11-14 9:32 ` Mattijs Korpershoek
2023-11-14 9:38 ` Svyatoslav Ryhel
2023-11-07 12:42 ` [PATCH v1 3/5] commonn: console: introduce overflow and isempty calls Svyatoslav Ryhel
2023-11-07 12:42 ` [PATCH v1 4/5] lib: membuff: fix readline not returning line in case of overflow Svyatoslav Ryhel
2023-11-07 12:42 ` [PATCH v1 5/5] fastboot: add oem console command support Svyatoslav Ryhel
2023-11-14 10:24 ` Mattijs Korpershoek
2023-11-14 10:30 ` Svyatoslav Ryhel
2023-11-14 12:14 ` Mattijs Korpershoek
2023-11-09 8:41 ` [PATCH v1 0/5] Implement fastboot multiresponce Mattijs Korpershoek
2023-11-09 9:01 ` Svyatoslav Ryhel
2023-11-09 10:59 ` Mattijs Korpershoek [this message]
2023-11-10 9:08 ` Svyatoslav Ryhel
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=87y1f78a4x.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=bmeng@tinylab.org \
--cc=clamor95@gmail.com \
--cc=dimorinny@google.com \
--cc=hs@denx.de \
--cc=hws@denx.de \
--cc=ion@agorria.com \
--cc=joe.hershberger@ni.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=patrick.delaunay@foss.st.com \
--cc=rfried.dev@gmail.com \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.