On 28.05.19 14:55, Kever Yang wrote:
> Hi Christoph and Mark,
>
> Does this patch ready for rk3399-puma?
Hi Kever,
yes, this commit is ready for mainline.
However, there are more (not Puma specific) commits needed to make get
mainline ATF working. I haven't got time recently to work on
Hi Christoph and Mark,
Does this patch ready for rk3399-puma?
Thanks,
- Kever
On 05/07/2019 05:18 PM, Christoph Müllner wrote:
> Hi Mark,
>
> On 07.05.19 10:57, Mark Kettenis wrote:
>>> From: Christoph Muellner
>>> Date: Tue, 7 May 2019 10:39:54 +0200
>>>
>>> This reverts commit
Hi Mark,
On 07.05.19 10:57, Mark Kettenis wrote:
>> From: Christoph Muellner
>> Date: Tue, 7 May 2019 10:39:54 +0200
>>
>> This reverts commit c869d63f2785ccde22582f96cf40cb8809f838ba.
>>
>> Mainline ATF already supports fdt-parsing, which allows us to
>> pass rk3399-puma specific data to setup
> From: Christoph Muellner
> Date: Tue, 7 May 2019 10:39:54 +0200
>
> This reverts commit c869d63f2785ccde22582f96cf40cb8809f838ba.
>
> Mainline ATF already supports fdt-parsing, which allows us to
> pass rk3399-puma specific data to setup things like the correct
> UART. Therefore we can
This reverts commit c869d63f2785ccde22582f96cf40cb8809f838ba.
Mainline ATF already supports fdt-parsing, which allows us to
pass rk3399-puma specific data to setup things like the correct
UART. Therefore we can re-enable platform parameterss again.
Signed-off-by: Christoph Muellner
---
5 matches
Mail list logo