| 11 Mar 2025 |
 @elvishjerricco:matrix.org | unless it wants to allocate that close to the 4G boundary I guess? | 18:08:54 |
| @elvishjerricco:matrix.org | no idea why it would | 18:09:01 |
| @elvishjerricco:matrix.org | i mean that might actually just be randomness or board specificness | 18:10:46 |
| @elvishjerricco:matrix.org | "EFI says to allocate here" and systemd-boot says "but I WANTED it behind there!" | 18:11:28 |
| @elvishjerricco:matrix.org | sidenote, I'm extremely annoyed by andre4ik3's comment claiming to show the answer clearly when it's anything but clear | 18:13:13 |
 aloisw | If xmalloc_initrd_pages is the correct function, then it asks the firmware to allocate anywhere below 4G: https://github.com/systemd/systemd/blob/7fa3b5018bfffa176c77a2a5794dce792eebadcb/src/boot/util.h#L111-L115 | 18:15:59 |
| @elvishjerricco:matrix.org | yes | 18:16:15 |
| @elvishjerricco:matrix.org | so why should 358M be hard to allocate below 4G? | 18:16:28 |
| aloisw | It just asks the firmware to do that and it fails, ask the firmware I guess. | 18:16:48 |
