Bootable image for Macchatobin Double Shot?

[greg at unrelenting.technology]

April 25, 2020 6:46 PM, "Mark Murray" <markm at freebsd.org> wrote:

>> On 25 Apr 2020, at 16:22, greg at unrelenting.technology wrote:
>> 
>> April 25, 2020 5:51 PM, "Mark Murray" <markm at freebsd.org> wrote:
>> 
>> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.bin
>> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image2.bin
>>> The second has the same binary bits as the one I downloaded from the link in my original post.
>> 
>> It should work then..
>> 
>> Unless I really screwed something up and *somehow* this is not a good image -
>> you can check by running (as root):
>> 
>> /usr/sbin/acpidump -t -d -o /dev/null | grep -a -C10 PNP0C02
> 
> # /usr/sbin/acpidump -t -d -o /dev/null | grep -a -C10 PNP0C02
> acpidump: FACS is corrupt
> 
>> that should find the PCIe controller in the DSDT table, its Memory32Fixed resource should
>> contain the address 0xE0000000, NOT 0xE0008000.
> 
> Not quite there yet :-)
> 
>> What does the pci command in the EFI Shell say? Run `pci 00 00 00 -i` to get info about a
>> particular device,
>> e.g. https://gist.github.com/myfreeweb/8b09f1c93ee9572aef01513ba9bf756f
> 
> Shell> pci
> Seg Bus Dev Func
> --- --- --- ----
> 00 00 00 00 ==> Network Controller - Ethernet controller
> Vendor 8086 Device 1521 Prog Interface 0
> 00 00 00 01 ==> Network Controller - Ethernet controller
> Vendor 8086 Device 1521 Prog Interface 0
> ASSERT [PciHostBridgeDxe]
> /home/mw/git/uefi-27/edk2-platforms/Silicon/Marvell/Armada7k8k/Library/Armada7k8kPciExpressLib/PciEx
> ressLib.c(78): Address < (0x0 + 1) * 0x00100000
> 
> Looks like something went badly wrong there :-(

Woah, "/home/mw/git/uefi-27" doesn't look like something that should appear in one of my builds..!

I guess flash-image2 is a reupload of an old build from the github wiki, and flash-image was my build,
but I might have overwritten it with a bad one. *facepalm*

Uploaded a new untested build that should work as
https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.bin
(sha256:8ae81d0cb07b36bd145ae56621e63c48c303641e1cf1a574714ca60211d66c66)

I really should finally get around to making this a proper "release", with a setting in the Setup screen
that would allow toggling the ECAM workaround on and off, and toggling the SPCR Linux workaround.
But first I'd like to switch to upstream TrustedFirmware, but my builds of it (using clang) don't work..
(This is currently using older Marvell-forked TF-A.)

>> Also, have you tried any other PCIe cards?
> 
> Nope - 'fraid not :-(.
> 
> My intention is to use this dual-port NIC until (if?) the on-board NICs are made to work, then I'll
> use them and then buy a cheapo PCIe video card to make a proper console I can use with a KVM
> switch. But I need to get the PCI going first :-)

I've started an attempt at porting the onboard NIC driver last summer:
https://github.com/myfreeweb/pepevtwo-kmod

Got as far as initializing stuff (except DMA) that's initialized before the ports.