On Fri, Oct 5, 2018 at 12:48 PM Maxime Ripard wrote:
> > What about the idea of keeping the current dt for the most featureful
> > variant and creating new dts for the other two?
> >
> > That would make it so that no one's device stops working and would
> > have mailine support for all three
On Fri, Oct 5, 2018 at 12:48 PM Maxime Ripard wrote:
> > What about the idea of keeping the current dt for the most featureful
> > variant and creating new dts for the other two?
> >
> > That would make it so that no one's device stops working and would
> > have mailine support for all three
On Tue, Oct 2, 2018 at 10:13 AM Maxime Ripard wrote:
>
> On Sat, Sep 29, 2018 at 01:51:02PM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Sat, Sep 29, 2018 at 12:47 PM Maxime Ripard
> > wrote:
> > > > We can't even remove a node from a device tree? Remov
On Tue, Oct 2, 2018 at 10:13 AM Maxime Ripard wrote:
>
> On Sat, Sep 29, 2018 at 01:51:02PM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Sat, Sep 29, 2018 at 12:47 PM Maxime Ripard
> > wrote:
> > > > We can't even remove a node from a device tree? Remov
On Sat, Sep 29, 2018 at 12:47 PM Maxime Ripard
wrote:
>
> On Thu, Sep 27, 2018 at 11:49:20AM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Thu, Sep 27, 2018 at 5:17 AM Maxime Ripard
> > wrote:
> > >
> > > On Tue, Sep 25, 2018 at 02:47:59PM -0300, Rodr
On Sat, Sep 29, 2018 at 12:47 PM Maxime Ripard
wrote:
>
> On Thu, Sep 27, 2018 at 11:49:20AM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Thu, Sep 27, 2018 at 5:17 AM Maxime Ripard
> > wrote:
> > >
> > > On Tue, Sep 25, 2018 at 02:47:59PM -0300, Rodr
On Thu, Sep 27, 2018 at 5:17 AM Maxime Ripard wrote:
>
> On Tue, Sep 25, 2018 at 02:47:59PM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Tue, Sep 25, 2018 at 6:01 AM Maxime Ripard
> > wrote:
> > > We can't really do that, unfortunately. If the device tr
On Thu, Sep 27, 2018 at 5:17 AM Maxime Ripard wrote:
>
> On Tue, Sep 25, 2018 at 02:47:59PM -0300, Rodrigo Exterckötter Tjäder wrote:
> > On Tue, Sep 25, 2018 at 6:01 AM Maxime Ripard
> > wrote:
> > > We can't really do that, unfortunately. If the device tr
The PHY found on the A64-OLinuXino requires a TX delay in order to
operate properly. Olimex uses a 600ps second delay in their BSP, and
that has been found to work, so let's use that value in the current
DT.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
arch/arm64/boot/dts/allwinner/sun50i-a64
The PHY found on the A64-OLinuXino requires a TX delay in order to
operate properly. Olimex uses a 600ps second delay in their BSP, and
that has been found to work, so let's use that value in the current
DT.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
arch/arm64/boot/dts/allwinner/sun50i-a64
On Wed, Sep 26, 2018 at 6:46 AM Maxime Ripard wrote:
> There's no need to be so specific though :)
>
> Something like that would work:
>
> arm64: dts: allwinner: a64-olinuxino: set the PHY TX delay
>
> The PHY found on the A64-Olinuxino requires a TX delay in order to
> operate properly. Olimex
On Wed, Sep 26, 2018 at 6:46 AM Maxime Ripard wrote:
> There's no need to be so specific though :)
>
> Something like that would work:
>
> arm64: dts: allwinner: a64-olinuxino: set the PHY TX delay
>
> The PHY found on the A64-Olinuxino requires a TX delay in order to
> operate properly. Olimex
On Tue, Sep 25, 2018 at 6:01 AM Maxime Ripard wrote:
> We can't really do that, unfortunately. If the device tree name was to
> change for a given board, we'd break all the build systems, boot
> scripts and distros out there.
What if we keep the device tree for the version without WiFi and eMMC
On Tue, Sep 25, 2018 at 6:01 AM Maxime Ripard wrote:
> We can't really do that, unfortunately. If the device tree name was to
> change for a given board, we'd break all the build systems, boot
> scripts and distros out there.
What if we keep the device tree for the version without WiFi and eMMC
On Fri, Sep 21, 2018 at 11:30 AM Maxime Ripard
wrote:
> On Wed, Sep 19, 2018 at 11:19:36AM -0300, Rodrigo Exterckötter Tjäder wrote:
> > Without "allwinner,tx-delay-ps = <600>;" on the DTP it can receive packets
> > but not send.
> >
> > Signed-off
On Fri, Sep 21, 2018 at 11:30 AM Maxime Ripard
wrote:
> On Wed, Sep 19, 2018 at 11:19:36AM -0300, Rodrigo Exterckötter Tjäder wrote:
> > Without "allwinner,tx-delay-ps = <600>;" on the DTP it can receive packets
> > but not send.
> >
> > Signed-off
On Fri, Sep 21, 2018 at 11:28 AM Maxime Ripard
wrote:
> Expanding a bit more that commit log would be helpful. What is the
> eMMC connected to that board? Do all versions have it? Which modes are
> supposed to be supported, and which one have been tested?
The terseness of the commit message was
On Fri, Sep 21, 2018 at 11:28 AM Maxime Ripard
wrote:
> Expanding a bit more that commit log would be helpful. What is the
> eMMC connected to that board? Do all versions have it? Which modes are
> supposed to be supported, and which one have been tested?
The terseness of the commit message was
Without "allwinner,tx-delay-ps = <600>;" on the DTP it can receive packets
but not send.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
arch/arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/allw
Without "allwinner,tx-delay-ps = <600>;" on the DTP it can receive packets
but not send.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
arch/arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/allw
Copied snippet from A64-TERES I.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
.../arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts
b/arch/arm64/boot/dts/allwinner/sun50i
Copied snippet from A64-TERES I.
Signed-off-by: Rodrigo Exterckötter Tjäder
---
.../arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-olinuxino.dts
b/arch/arm64/boot/dts/allwinner/sun50i
22 matches
Mail list logo
