Hi,
On 7 August 2017 at 07:54, Tom Rini wrote:
> On Thu, Aug 03, 2017 at 12:48:30PM -0400, Rob Clark wrote:
>
>> Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
>> u-boot build. This allows the board to patch the fdt, etc.
>>
>> In the specific case of dragonboard 410c, we
On Thu, Aug 03, 2017 at 12:48:30PM -0400, Rob Clark wrote:
> Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
> u-boot build. This allows the board to patch the fdt, etc.
>
> In the specific case of dragonboard 410c, we pass the u-boot generated
> fdt to the previous stage
On Sun, Aug 6, 2017 at 1:16 AM, Simon Glass wrote:
> Hi Rob,
>
> On 3 August 2017 at 10:48, Rob Clark wrote:
>> Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
>> u-boot build. This allows the board to patch the fdt, etc.
>>
>> In the specific case of dragonboard 410c, we
Hi Rob,
On 3 August 2017 at 10:48, Rob Clark wrote:
> Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
> u-boot build. This allows the board to patch the fdt, etc.
>
> In the specific case of dragonboard 410c, we pass the u-boot generated
> fdt to the previous stage of boot
Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
u-boot build. This allows the board to patch the fdt, etc.
In the specific case of dragonboard 410c, we pass the u-boot generated
fdt to the previous stage of bootloader (by embedding it in the
u-boot.img that is loaded by lk/
5 matches
Mail list logo