Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-07-03 Thread Conor Dooley
On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley wrote: > The firmware on the Icicle is capable of providing a devicetree in a1 to > U-Boot, but until now the devicetree has been packaged in a "payload" [1] > alongside U-Boot (or other bootloaders/RTOSes) and appended to the image. > The

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-28 Thread Conor Dooley
On Fri, Jun 28, 2024 at 08:53:11AM +0300, Ilias Apalodimas wrote: > On Thu, 27 Jun 2024 at 23:27, Conor Dooley wrote: > > On Thu, Jun 27, 2024 at 11:50:33AM +0100, Simon Glass wrote: > > > On Thu, 27 Jun 2024 at 10:38, Conor Dooley > > > wrote: > > > > On Thu, Jun 27, 2024 at 09:36:49AM +0100,

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-28 Thread Conor Dooley
On Fri, Jun 28, 2024 at 07:22:35AM +0100, Simon Glass wrote: > On Thu, 27 Jun 2024 at 21:27, Conor Dooley wrote: > > OK, thanks for all the details. I suppose, to me, 128KB does not sound > that constrained :-) But I can see that messing with a bloblist can > add code. A static tool would help

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-28 Thread Simon Glass
Hi Conor, On Thu, 27 Jun 2024 at 21:27, Conor Dooley wrote: > > On Thu, Jun 27, 2024 at 11:50:33AM +0100, Simon Glass wrote: > > On Thu, 27 Jun 2024 at 10:38, Conor Dooley > > wrote: > > > On Thu, Jun 27, 2024 at 09:36:49AM +0100, Simon Glass wrote: > > > > On Tue, 25 Jun 2024 at 15:34, Tom

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-27 Thread Ilias Apalodimas
Hi Conor, On Thu, 27 Jun 2024 at 23:27, Conor Dooley wrote: > > On Thu, Jun 27, 2024 at 11:50:33AM +0100, Simon Glass wrote: > > On Thu, 27 Jun 2024 at 10:38, Conor Dooley > > wrote: > > > On Thu, Jun 27, 2024 at 09:36:49AM +0100, Simon Glass wrote: > > > > On Tue, 25 Jun 2024 at 15:34, Tom

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-27 Thread Conor Dooley
On Thu, Jun 27, 2024 at 11:50:33AM +0100, Simon Glass wrote: > On Thu, 27 Jun 2024 at 10:38, Conor Dooley wrote: > > On Thu, Jun 27, 2024 at 09:36:49AM +0100, Simon Glass wrote: > > > On Tue, 25 Jun 2024 at 15:34, Tom Rini wrote: > > > > On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-27 Thread Simon Glass
Hi Connor, On Thu, 27 Jun 2024 at 10:38, Conor Dooley wrote: > > On Thu, Jun 27, 2024 at 09:36:49AM +0100, Simon Glass wrote: > > > > On Tue, 25 Jun 2024 at 15:34, Tom Rini wrote: > > > > > > On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley wrote: > > > > > > > The firmware on the Icicle

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-27 Thread Conor Dooley
On Thu, Jun 27, 2024 at 09:36:49AM +0100, Simon Glass wrote: > > On Tue, 25 Jun 2024 at 15:34, Tom Rini wrote: > > > > On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley wrote: > > > > > The firmware on the Icicle is capable of providing a devicetree in a1 to > > > U-Boot, but until now the

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-27 Thread Simon Glass
Hi, On Tue, 25 Jun 2024 at 15:34, Tom Rini wrote: > > On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley wrote: > > > The firmware on the Icicle is capable of providing a devicetree in a1 to > > U-Boot, but until now the devicetree has been packaged in a "payload" [1] > > alongside U-Boot

Re: [PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-25 Thread Tom Rini
On Tue, Jun 25, 2024 at 10:08:06AM +0100, Conor Dooley wrote: > The firmware on the Icicle is capable of providing a devicetree in a1 to > U-Boot, but until now the devicetree has been packaged in a "payload" [1] > alongside U-Boot (or other bootloaders/RTOSes) and appended to the image. > The

[PATCH v1] board: mpfs_icicle: implement board_fdt_blob_setup()

2024-06-25 Thread Conor Dooley
The firmware on the Icicle is capable of providing a devicetree in a1 to U-Boot, but until now the devicetree has been packaged in a "payload" [1] alongside U-Boot (or other bootloaders/RTOSes) and appended to the image. The address of this appended devicetree is placed in a1 by the firmware. This