Re: [PATCH v1 00/23] board: nxp: add the Free Mobile Nodebox v3 CPU Module (LX2160A)

On Thu, 20 Aug 2026 at 13:27, Simon Glass <[email protected]> wrote:
>
> Hi Peter,
>
> On Thu, 20 Aug 2026 at 05:52, Peter Robinson <[email protected]> wrote:
> >
> > Hi Vincent,
> >
> > > > > This series adds the Free Mobile Nodebox v3 CPU Module, an NXP
> > > > > LX2160A based board (16x Cortex-A72, DPAA2). U-Boot is the BL33
> > > > > payload of TF-A: BL2 trains the DDR, BL31 hands over, and U-Boot
> > > > > boots a FIT image (kernel + MC firmware + DPC/DPL) from a single
> > > > > FlexSPI NOR. The module plugs onto several carrier boards (NBV30,
> > > > > NBV32, etc.) that share one kernel image but differ in their device
> > > > > tree and DPAA2 data path.
> > > >
> > > > Why just FIT and not UEFI?
> > >
> > > Because this layerscape platform shall not support UEFI by design.
> >
> > Really? I have a clearfog LX2 platform that boots and runs with UEFI
> > just fine. Generally this is where the Linux ecosystem is going so for
> > a new board going upstream I would expect it to at least be an option.
>
> Generally this is where certain people are pushing Embedded Linux to
> go, but that doesn't mean it makes any sense to do so. UEFI requires a
> lot of extra code and complexity, 100K+ in U-Boot alone, not to
> mention GRUB, etc. It doesn't support embedded things like FPGA
> images. FIT is a good solution and as an industry we should be
> innovating on that, not forcing UEFI everywhere. If you need OS
> selection, Boot Loader Specification (with FIT) is a good option.

Simon, I am well aware of all of that, I have been involved in the arm
ecosystem for well over 15 years.

> Note that I write this not as someone opposed to EFI protocols (which
> I have expended a lot of effort implementing and reviewing). Horses
> for courses.
>
> [..]
>
> Regards,
> Simon