hey wanna see somethng cursed

one part of this NIC is downloading UEFI boot options from another part of this NIC over HTTP. (well, failing to do it for some reason)

you're welcome

@whitequark oh no. oh no that implies multiple fucking processors
@freya yes it has two linuxes on it
@whitequark why. what. what. what
@freya second is AST2600
@whitequark what the fuuuuck, that's a wholeass BMC
@freya yup
@freya with 1 GB of RAM (256 MB of it is full of some crap)
@whitequark @freya would not be surprised if that was (reserved for) the (host's) video framebuffer
@vmp_ @whitequark yep, you would be exactly correct, the AST2600 is configured to prevent to be a Matrox MGA-G200 VGA chipset

@freya @vmp_ what

no that's not the case at all. what the hell are you talking about

@whitequark @vmp_ the Aspeed AST2600 uses a hunk of ram to be a VGA chipset because it's used as a BMC in servers, right?
@freya @vmp_ first, you need barely any RAM for a Matrox framebuffer (the Matrox card you're talking about came with eight megabytes of it. today you could put that in on-die SRAM if you wanted). second, i'm talking about Linux-accessible RAM, on the Linux kernel, that I have root on
@whitequark @freya ah well, just speculating. When it's bolted to an x86 as a PCIe endpoint, the AST2500 and AST2400 share a chunk of their DRAM with the PCIe host, as part of a VGA class device (the ones I've seen did declare themselves aspeed though
.. I've seen others declared as Matrox (Nuvoton?)). The aspeed side can then read it and implement "KVM over IP". This would be configured in aspeed's devicetree and, well, 256MB in not implausible.