From: "Leonidas P. Papadakos" <papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] arm64: dts: rockchip: Fix rk3328 rgmii high tx error rate
Date: Tue, 12 Mar 2019 04:13:43 +0200 [thread overview]
Message-ID: <1552356823.2607.2@gmail.com> (raw)
In-Reply-To: <1552356332.2607.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> I do have to say, This patch does fix my Link Reset issue reliably
> enough, so it does *something*
Well, I just tried the same things I did yesterday (iperf3 testts, GbE)
and it seems to work even without the patch. (?)
Using the defailt tx/rx delays though. (0x25,0x11)
next prev parent reply other threads:[~2019-03-12 2:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 18:20 [PATCH] arm64: dts: rockchip: Fix rk3328 rgmii high tx error rate Peter Geis
2019-03-09 18:20 ` Peter Geis
[not found] ` <20190309182013.22162-1-pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-10 0:47 ` Leonidas P. Papadakos
[not found] ` <20190310004722.5140-1-papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-12 2:05 ` Leonidas P. Papadakos
[not found] ` <1552356332.2607.1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-12 2:13 ` Leonidas P. Papadakos [this message]
[not found] ` <1552356823.2607.2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-12 12:23 ` Peter Geis
[not found] ` <CAMdYzYrn2eEr=JzNFe3wp-VjoVHwxcQkf98zc0MSMh4j=0ZDvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-03-13 1:53 ` Peter Geis
2019-03-12 1:21 ` Robin Murphy
2019-03-12 1:21 ` Robin Murphy
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 18:45 [PATCH] arm64: dts: rockchip: fix " Peter Geis
2019-03-13 18:45 ` Peter Geis
[not found] ` <20190313184535.15759-1-pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-16 20:00 ` Heiko Stuebner
2019-03-16 20:00 ` Heiko Stuebner
2019-04-03 0:07 ` Robin Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1552356823.2607.2@gmail.com \
--to=papadakospan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.