On 18. 02. 19 14:03, Vinod Koul wrote:
On 18-02-19, 12:54, Michal Vokáč wrote:
On 18. 02. 19 11:45, Vinod Koul wrote:
On 15-02-19, 16:23, Andrew Lunn wrote:
On Fri, Feb 15, 2019 at 04:01:08PM +0100, Michal Vokáč wrote:
Hi,
networking on my boards [1], which are currently in linux-next, sudde
On 18-02-19, 12:54, Michal Vokáč wrote:
> On 18. 02. 19 11:45, Vinod Koul wrote:
> > On 15-02-19, 16:23, Andrew Lunn wrote:
> > > On Fri, Feb 15, 2019 at 04:01:08PM +0100, Michal Vokáč wrote:
> > > > Hi,
> > > >
> > > > networking on my boards [1], which are currently in linux-next,
> > > > sudde
On 18. 02. 19 11:45, Vinod Koul wrote:
On 15-02-19, 16:23, Andrew Lunn wrote:
On Fri, Feb 15, 2019 at 04:01:08PM +0100, Michal Vokáč wrote:
Hi,
networking on my boards [1], which are currently in linux-next, suddently
stopped working. I tracked it down to this commit 5ecdd77c61c8 ("net: dsa:
q
On 15-02-19, 16:23, Andrew Lunn wrote:
> On Fri, Feb 15, 2019 at 04:01:08PM +0100, Michal Vokáč wrote:
> > Hi,
> >
> > networking on my boards [1], which are currently in linux-next, suddently
> > stopped working. I tracked it down to this commit 5ecdd77c61c8 ("net: dsa:
> > qca8k: disable delay f
On Fri, Feb 15, 2019 at 04:01:08PM +0100, Michal Vokáč wrote:
> Hi,
>
> networking on my boards [1], which are currently in linux-next, suddently
> stopped working. I tracked it down to this commit 5ecdd77c61c8 ("net: dsa:
> qca8k: disable delay for RGMII mode") [2].
>
> So I think the rgmii-id m
Hi,
networking on my boards [1], which are currently in linux-next, suddently
stopped working. I tracked it down to this commit 5ecdd77c61c8 ("net: dsa:
qca8k: disable delay for RGMII mode") [2].
So I think the rgmii-id mode is obviously needed in my case.
I was able to find a couple drivers tha
