On 4/1/20 10:37 AM, Patrick DELAUNAY wrote:
> Hi,
[...]
>>> When this file will be removed ? why kept this file.
>>> I propose to completely remove this file (no device tree for same
>>> board)
>>
>> Backward compatibility, I'd keep it in for a release or two.
>> But if removing it is fine, t
Hi,
> From: Marek Vasut
> Sent: mardi 31 mars 2020 18:38
>
> On 3/31/20 4:59 PM, Patrick DELAUNAY wrote:
> > Hi,
>
> Hi,
>
> >> It is also highly recommended to configure the board for the DHCOM
> >> make stm32mp15_dhcom_basic_defconfig make
> >> DEVICE_TREE=stm32mp15xx-dhcor-
> >> avenger96
>
On 3/31/20 4:59 PM, Patrick DELAUNAY wrote:
> Hi,
Hi,
>> It is also highly recommended to configure the board for the DHCOM make
>> stm32mp15_dhcom_basic_defconfig make DEVICE_TREE=stm32mp15xx-dhcor-
>> avenger96
>> as that permits reusing the board code for the DH components, like accessing
>>
Hi,
> From: Marek Vasut
> Sent: mardi 31 mars 2020 02:49
>
> The AV96 is in fact an assembly of DH Electronics DHCOR SoM on top of an
> AV96 reference board. Split the DTs to reflect that and make sure to DHCOR SoM
> can be reused on other boards easily.
>
> It is also highly recommended to con
Hi Marek
On 3/31/20 2:48 AM, Marek Vasut wrote:
> The AV96 is in fact an assembly of DH Electronics DHCOR SoM on top
> of an AV96 reference board. Split the DTs to reflect that and make
> sure to DHCOR SoM can be reused on other boards easily.
>
> It is also highly recommended to configure the boa
The AV96 is in fact an assembly of DH Electronics DHCOR SoM on top
of an AV96 reference board. Split the DTs to reflect that and make
sure to DHCOR SoM can be reused on other boards easily.
It is also highly recommended to configure the board for the DHCOM
make stm32mp15_dhcom_basic_defconfig
make
6 matches
Mail list logo
