On 10/6/21 09:58, Heinrich Schuchardt wrote:
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 cal
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
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 i
On Okt 05 2021, Heinrich Schuchardt wrote:
> Which firmware did you use? U-Boot or EDK II? Which version?
U-Boot.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
__
On 10/5/21 12:05, Andreas Schwab wrote:
On Okt 05 2021, Heinrich Schuchardt wrote:
Do you think this problem is RISC-V specific
No, I don't think so.
and related to the series?
Since network download of the kernel works, this seems to be related to
the use of the LoadFile2 protocol.
An
On Okt 05 2021, Heinrich Schuchardt wrote:
> Do you think this problem is RISC-V specific
No, I don't think so.
> and related to the series?
Since network download of the kernel works, this seems to be related to
the use of the LoadFile2 protocol.
Andreas.
--
Andreas Schwab, sch...@linux-m68
On 9/23/21 14:18, Andreas Schwab wrote:
That appears to have issues with loading the initrd over network. I can
see the RRQ packet for the initrd arriving at the tftp server, the first
DATA packet sent out by the sever, which is acknowleged by the client.
But all subsequent DATA packages are n
That appears to have issues with loading the initrd over network. I can
see the RRQ packet for the initrd arriving at the tftp server, the first
DATA packet sent out by the sever, which is acknowleged by the client.
But all subsequent DATA packages are never acknowleged by the client,
which just t
From: Ard Biesheuvel
Recent Linux kernels will invoke the LoadFile2 protocol installed on
a well-known vendor media path to load the initrd if it is exposed by
the firmware. Using this method is preferred for two reasons:
- the Linux kernel is in charge of allocating the memory, and so it can
i
