lmp/jobserv: Bring lmp-base distro build back for LTS

[angolini]

Based on [1] bring back the DISTRO=lmp-base build for scarthgap/lts branch, but using the current machine list.

7c58dc7

[mike-scott]

LGTM

[quaresmajose]

Is the qemuarm64-secureboot fixed? The last test I did, it was still broken.

NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v2.10.4(release):lts-v2.10.4-dirty
NOTICE:  BL1: Built : 16:23:33, Apr 26 2024
NOTICE:  BL1: Booting BL2
NOTICE:  BL2: v2.10.4(release):lts-v2.10.4-dirty
NOTICE:  BL2: Built : 16:23:33, Apr 26 2024
NOTICE:  BL1: Booting BL31
NOTICE:  BL31: v2.10.4(release):lts-v2.10.4-dirty
NOTICE:  BL31: Built : 16:23:33, Apr 26 2024


U-Boot 2024.04+fio+g30cd2b39fb4 (Oct 15 2024 - 17:57:22 +0000)

DRAM:  1 GiB
Core:  51 devices, 14 uclasses, devicetree: board
Flash: 32 MiB
Loading Environment from Flash... *** Warning - bad CRC, using default environment

In:    serial,usbkbd
Out:   serial,vidconsole
Err:   serial,vidconsole
Bus xhci_pci: Register 8001040 NbrPorts 8
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 3 USB Device(s) found
Net:   eth0: virtio-net#32
Hit any key to stop autoboot:  0 
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
Missing TPMv2 device for EFI_TCG_PROTOCOL
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'virtio 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev '[email protected]':
warning: no initrd available
loading kernel to address 40400000 size 92e464
  1  qfw          ready   qfw          0  qfw                       
** Booting bootflow 'qfw' with qfw
Bad Linux ARM64 Image magic!
zimage: Bad magic!
Boot failed (err=-5)
scanning bus for devices...
Scanning bootdev 'virtio-blk#35.bootdev':
  2  extlinux     ready   virtio       1  virtio-blk#35.bootdev.par /extlinux/extlinux.conf
** Booting bootflow 'virtio-blk#35.bootdev.part_1' with extlinux
1:      Yocto
Retrieving file: /Image
Skipping Yocto for failure retrieving kernel
Boot failed (err=-14)
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
Scanning bootdev 'virtio-net#32.bootdev':
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
*** Warning: no boot file name; using '0A00020F.img'
Using virtio-net#32 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename '0A00020F.img'.
Load address: 0x40400000
Loading: *
TFTP error: 'File not found' (1)
Not retrying...
No more bootdevs
---  -----------  ------  --------  ----  ------------------------  ----------------
(3 bootflows, 3 valid)
=> 

[angolini]

Is the qemuarm64-secureboot fixed? The last test I did, it was still broken.

I only test the build for the machines built on CI. I haven't boot tested any - So I don't know

[quaresmajose]

If everyone is already building, that's enough, because otherwise it would break the overall build.

[quaresmajose]

LGTM

[angolini]

@ricardosalveti can we merge? If there is anything else, please, let me know