From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Nikita Ermakov <arei@altlinux.org>,
GRUB development mailing list <grub-devel@gnu.org>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Atish Patra <Atish.Patra@wdc.com>,
Daniel Kiper <dkiper@net-space.pl>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 3/7] efi: implemented LoadFile2 initrd loading protocol for Linux
Date: Wed, 6 Oct 2021 09:58:47 +0200 [thread overview]
Message-ID: <94bf1f95-c9a8-fd91-2473-dcbb452db835@gmx.de> (raw)
In-Reply-To: <871r4zjxqb.fsf@igel.home>
On 10/5/21 17:30, Andreas Schwab wrote:
> On Okt 05 2021, Heinrich Schuchardt wrote:
>
>> Before the 'boot' command the communication via TFTP seems to work fine.
>> The init command can identify which file exists on the TFTP server.
>>
>> The boot command calls ShutDown() and Stop() on the SNP protocol and
>> closes it. And then tries to open it again for the LOAD_FILE2 protocol.
>>
>> The question remains why the protocol cannot be reopened. It is unclear
>> if this is a GRUB or a U-Boot issue.
>
> The strange thing is that the first two packets+ACK still get through.
> Maybe related to the size of the following DATA packet?
When the initrd command is issued it checks that the file exists. It is
after the boot command that things run awry.
There are multiple bugs in efinet.c. I am working on a patch.
Best regards
Heinrich
next prev parent reply other threads:[~2021-10-06 7:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 21:12 [PATCH v2 0/7] Add LoadFile2 and riscv Linux loader Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 1/7] loader: drop argv[] argument in grub_initrd_load() Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 2/7] efi: add definition of LoadFile2 protocol Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 3/7] efi: implemented LoadFile2 initrd loading protocol for Linux Nikita Ermakov
2021-09-23 12:18 ` Andreas Schwab
2021-10-05 9:45 ` Heinrich Schuchardt
2021-10-05 10:05 ` Andreas Schwab
2021-10-05 14:57 ` Heinrich Schuchardt
2021-10-05 15:07 ` Andreas Schwab
2021-10-05 15:30 ` Andreas Schwab
2021-10-06 7:58 ` Heinrich Schuchardt [this message]
2021-10-08 17:39 ` Heinrich Schuchardt
2021-06-02 21:12 ` [PATCH v2 4/7] linux: ignore FDT unless we need to modify it Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 5/7] loader: Move arm64 linux loader to common code Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 6/7] RISC-V: Update image header Nikita Ermakov
2021-06-02 21:12 ` [PATCH v2 7/7] RISC-V: Use common linux loader Nikita Ermakov
2021-06-26 18:07 ` [PATCH v2 0/7] Add LoadFile2 and riscv Linux loader Andreas Schwab
2021-06-27 21:01 ` Heinrich Schuchardt
2021-06-27 22:07 ` Andreas Schwab
2021-06-29 13:44 ` Heinrich Schuchardt
2021-10-08 17:34 ` Heinrich Schuchardt
2021-06-28 21:24 ` Heinrich Schuchardt
2021-06-29 19:13 ` Atish Patra
2021-06-30 7:26 ` Ard Biesheuvel
2021-07-02 18:48 ` Atish Patra
2021-08-27 16:22 ` Atish Patra
2021-08-27 16:29 ` Fu Wei
2021-08-28 12:21 ` Nikita Ermakov
2021-08-29 2:30 ` Fu Wei
2021-08-29 12:44 ` Nikita Ermakov
2021-08-30 1:43 ` Heinrich Schuchardt
2021-10-08 17:46 ` Heinrich Schuchardt
2021-10-14 18:49 ` Daniel Kiper
2021-10-16 13:39 ` Nikita Ermakov
2021-10-18 9:27 ` Heinrich Schuchardt
2021-10-18 18:04 ` Daniel Kiper
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=94bf1f95-c9a8-fd91-2473-dcbb452db835@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=Atish.Patra@wdc.com \
--cc=ard.biesheuvel@arm.com \
--cc=arei@altlinux.org \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
--cc=leif.lindholm@linaro.org \
--cc=schwab@linux-m68k.org \
/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.