On 13 September 2017 at 13:29, Philipp Tomsich
wrote:
> To better support bootin through an ATF or OPTEE, we need to
> streamline some of the logic for when the FDT is appended to an image:
> depending on the image type, we'd like to append the FDT not at
On 09/13/2017 03:11 PM, Dr. Philipp Tomsich wrote:
> York,
>
>> On 13 Sep 2017, at 23:24, York Sun wrote:
>>
>> On 09/13/2017 02:21 PM, Dr. Philipp Tomsich wrote:
>>> York,
>>>
On 13 Sep 2017, at 23:16, York Sun wrote:
On 09/13/2017 12:30 PM,
York,
> On 13 Sep 2017, at 23:24, York Sun wrote:
>
> On 09/13/2017 02:21 PM, Dr. Philipp Tomsich wrote:
>> York,
>>
>>> On 13 Sep 2017, at 23:16, York Sun wrote:
>>>
>>> On 09/13/2017 12:30 PM, Philipp Tomsich wrote:
To better support bootin through
On 09/13/2017 02:21 PM, Dr. Philipp Tomsich wrote:
> York,
>
>> On 13 Sep 2017, at 23:16, York Sun wrote:
>>
>> On 09/13/2017 12:30 PM, Philipp Tomsich wrote:
>>> To better support bootin through an ATF or OPTEE, we need to
>>> streamline some of the logic for when the FDT is
On 09/13/2017 12:30 PM, Philipp Tomsich wrote:
> To better support bootin through an ATF or OPTEE, we need to
> streamline some of the logic for when the FDT is appended to an image:
> depending on the image type, we'd like to append the FDT not at all
> (the case for the OS boot), to the
To better support bootin through an ATF or OPTEE, we need to
streamline some of the logic for when the FDT is appended to an image:
depending on the image type, we'd like to append the FDT not at all
(the case for the OS boot), to the 'firmware' image (if it is a
U-Boot) or to one of the loadables
6 matches
Mail list logo