Hello!
First of all: I have no idea who wrote the original rockchip-u-boot.dtsi,
but all the time I've worked with Rockchips SoCs, it;s always been like
this : BL31 is provided by Rockchips in form of .elf file, that binman
successfully process, and BL32 (AKA OP-TEE) is provided as a pre-compiled
On 2023-04-03 15:33, Peter Robinson wrote:
> On Mon, Apr 3, 2023 at 2:30 PM Mark Kettenis wrote:
>>
>>> From:
>>> Date: Mon, 3 Apr 2023 12:27:36 +0300
>>>
>>> Hi!
>>>
>>>Trying to build mainline U-Boot for Rockchip RK3568-based board (Forlinx
>>> RK3568), but I think it;s can be reproduced on
On Mon, Apr 3, 2023 at 2:30 PM Mark Kettenis wrote:
>
> > From:
> > Date: Mon, 3 Apr 2023 12:27:36 +0300
> >
> > Hi!
> >
> >Trying to build mainline U-Boot for Rockchip RK3568-based board (Forlinx
> > RK3568), but I think it;s can be reproduced on all RK35 chips. The main
> > problem is that
> From:
> Date: Mon, 3 Apr 2023 12:27:36 +0300
>
> Hi!
>
>Trying to build mainline U-Boot for Rockchip RK3568-based board (Forlinx
> RK3568), but I think it;s can be reproduced on all RK35 chips. The main
> problem is that BL32 (AKA OP-TEE) is provided by Roch-Chips as a
> pre-compiled blob
Hi!
Trying to build mainline U-Boot for Rockchip RK3568-based board (Forlinx
RK3568), but I think it;s can be reproduced on all RK35 chips. The main
problem is that BL32 (AKA OP-TEE) is provided by Roch-Chips as a
pre-compiled blob and binman fails to implement that scenario. Used .dtsi
file an
5 matches
Mail list logo