From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v6 12/12] test: efi: boot: Add a test for the efi bootmeth
Date: Mon, 14 Oct 2024 15:11:50 -0600 [thread overview]
Message-ID: <20241014211150.GX53053@bill-the-cat> (raw)
In-Reply-To: <CAFLszTiVsoTdKiKmPVugc9cLk-A+XM2EdiPUE0AFK=g8RPx+0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, Oct 14, 2024 at 01:13:41PM -0600, Simon Glass wrote:
[snip]
> Or perhaps just have a way to turn it off? I first sent this patch
> last November. It is just wrong to generate output like this which we
> don't want. There isn't even a test for it, so just add a way to
> disable it, and be done!
I don't know that it's unwanted. As I'm trying to get Heinrich to
explain, _why_ does efi_setup_console_size need to exist, and do what it
does? This isn't the case of color-coding the output of tests as they
happen, there must be a reason we care about knowing the console size.
At that point we can figure out if the right answer is:
- Don't generate that check on serial ports, it's somewhere between
misleading to wrong.
- text-based tests just need to expect and skip it because there's a
good reason to need to know the console size and not just assume
80x24.
- Something else we won't know until it's clearly explained why we do
this.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-14 21:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 22:02 [PATCH v6 08/12] efi_loader: Disable ANSI output for tests Simon Glass
2024-09-26 22:02 ` [PATCH v6 09/12] efi_loader: Add a test app Simon Glass
2024-09-27 13:50 ` Ilias Apalodimas
2024-09-27 16:50 ` Simon Glass
2024-09-30 12:00 ` Heinrich Schuchardt
2024-09-30 14:12 ` Simon Glass
2024-09-26 22:02 ` [PATCH v6 10/12] sandbox: virtio: Disable the sandbox virtio blk device Simon Glass
2024-09-27 0:22 ` Tom Rini
2024-09-26 22:02 ` [PATCH v6 11/12] test: efi: boot: Set up an image suitable for EFI testing Simon Glass
2024-09-26 22:02 ` [PATCH v6 12/12] test: efi: boot: Add a test for the efi bootmeth Simon Glass
2024-10-11 22:32 ` Tom Rini
2024-10-13 19:33 ` Simon Glass
2024-10-14 3:51 ` Tom Rini
2024-10-14 7:00 ` Heinrich Schuchardt
2024-10-14 14:32 ` Tom Rini
2024-10-14 19:13 ` Simon Glass
2024-10-14 21:11 ` Tom Rini [this message]
2024-10-15 10:19 ` Mark Kettenis
2024-10-15 11:36 ` Heinrich Schuchardt
2024-10-15 13:25 ` Simon Glass
2024-10-15 14:16 ` Tom Rini
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=20241014211150.GX53053@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--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.