From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add CONFIG_GMAC_TX_DELAY=4 for OlinuXino Lime2
Date: Thu, 17 Mar 2016 11:52:14 +0100 [thread overview]
Message-ID: <56EA8C5E.1070701@redhat.com> (raw)
In-Reply-To: <56EA4097.3010500@computerlinguist.org>
Hi,
On 17-03-16 06:28, Michael Haas wrote:
> Hello all,
>
>
> On 03/16/2016 09:36 PM, Karsten Merker wrote:
>> Michael, if you would like to try testing higher RX delay chain values
>> on the Lime2, I have attached a small patch that adds an appropriate
>> Kconfig option. Regards, Karsten
>
> I will be testing your patch along with Hans' patch. In fact, I have
> already compiled it - I'm just waiting for a new SD card reader to
> arrive tomorrow. Sorry for the delay.
>
> In the mean time, as I was trying to get the device to boot at all (not
> related to u-boot, just my broken sdcard setup), I did try my old SD
> card again to load the debian netinstaller. This should be the version
> with the TX_DELAY set to 4.
>
> Now I'm sitting in an ash shell and I can wget files from my desktop at
> around 100MB/s.
>
>
> ~ # wget http://192.168.1.170:8000/debian-8.3.0-i386-netinst.iso -O - |
> md5sum
> Connecting to 192.168.1.170:8000 (192.168.1.170:8000)
> - 100% |*******************************| 315M
> 0:00:00 ETA
> 37f329724a1c072cbe0ebda211fdeb88 -
> ~ # wget http://192.168.1.170:8000/debian-8.3.0-i386-netinst.iso -O - |
> md5sum
> Connecting to 192.168.1.170:8000 (192.168.1.170:8000)
> - 100% |*******************************| 315M
> 0:00:00 ETA
> 37f329724a1c072cbe0ebda211fdeb88 -
>
> ~ # date +%s; wget
> http://192.168.1.170:8000/debian-8.3.0-i386-netinst.iso -O /d
> ev/null; date +%s
> 1258
> Connecting to 192.168.1.170:8000 (192.168.1.170:8000)
> null 100% |*******************************| 315M
> 0:00:00 ETA
> 1261
>
> ~ # dmesg | grep -i link
> [ 1.504918] audit: initializing netlink subsys (disabled)
> [ 88.561822] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 90.547368] sun7i-dwmac 1c50000.ethernet eth0: Link is Up -
> 1Gbps/Full - flow control rx/tx
> [ 90.547424] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
> ~ # cat /etc/lsb-release
> DISTRIB_ID=Debian
> DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
> DISTRIB_RELEASE="9 (stretch) - installer build 20160316-00:13"
> X_INSTALLATION_MEDIUM=netboot
> ~ # uname -a
> Linux debian 4.4.0-1-armmp #1 SMP Debian 4.4.4-2 (2016-03-09) armv7l
> GNU/Linux
>
>
>
> It takes around three seconds (date +%s; time not set) to transfer the
> 315MB. The md5sum matches.
>
> Now, with the device sitting on my desk in a debian installer session
> and working gbit.. how do I proceed from here? I don't dare rebooting..
There are 3 things which would be interesting to save and compare
with a boot which does have the problem:
1) The gmc clk register, to do this download mmio_dump from:
https://fedorapeople.org/~jwrdegoede/mmio-dump
And as root run:
./mmio-dump 0x1c20164
And record the output
This is a statically linked binary (I use it on android) so it
should work fine. If you don't like running $random binaries
of the internet, you can find the c-code here:
https://fedorapeople.org/~jwrdegoede/mmio-dump.c
Compile this (on the arm-system) with:
gcc -o mmio-dump mmio-dump.c
2) The pmic settings for various ldo-s, etc. as root run:
i2cdump -f -y 0 0x34
And record the output. You may need to
install i2c-tools (or the deb. alternative) and
do "modprobe i2c_dev"
3) The phy settings, unfortunately I do not know of
a way to dump these, so lets just forget about these
and focus on the other 2.
Regards,
Hans
>
> Best
>
> Michael
>
>
>
>
>
next prev parent reply other threads:[~2016-03-17 10:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 5:41 [U-Boot] [PATCH] Add CONFIG_GMAC_TX_DELAY=4 for OlinuXino Lime2 Michael Haas
[not found] ` <20160315180914.GA1878@excalibur.cnev.de>
2016-03-15 20:41 ` Tom Rini
2016-03-16 8:32 ` Michael Haas
2016-03-16 9:29 ` Hans de Goede
2016-03-16 10:53 ` Hans de Goede
[not found] ` <20160316203642.GC1817@excalibur.cnev.de>
2016-03-17 5:28 ` Michael Haas
2016-03-17 10:52 ` Hans de Goede [this message]
2016-03-17 21:53 ` Michael Haas
2016-03-18 7:41 ` Hans de Goede
[not found] ` <20160318190220.GC1815@excalibur.cnev.de>
2016-03-18 19:06 ` Michael Haas
2016-03-20 8:36 ` Michael Haas
2016-03-20 10:05 ` François-David Collin
2016-03-18 20:32 ` Michael Haas
2016-03-18 21:53 ` Michael Haas
2016-03-19 8:39 ` François-David Collin
2016-03-19 9:32 ` Hans de Goede
2016-03-19 9:35 ` Michael Haas
2016-03-19 9:45 ` Michael Haas
2016-03-19 13:40 ` Michael Haas
2016-03-19 14:35 ` François-David Collin
2016-03-20 13:45 ` Hans de Goede
2016-03-20 15:28 ` Michael Haas
2016-03-20 18:51 ` Hans de Goede
[not found] ` <20160321154714.GA4751@excalibur.cnev.de>
2016-03-21 18:57 ` Michael Haas
2016-03-21 20:59 ` Hans de Goede
2016-03-21 21:01 ` Hans de Goede
2016-03-21 21:47 ` Michael Haas
2016-03-21 22:00 ` Hans de Goede
2016-03-22 5:12 ` Michael Haas
2016-03-22 8:46 ` Peter Korsgaard
2016-03-22 8:57 ` Hans de Goede
2016-03-22 9:01 ` Michael Haas
2016-03-22 9:50 ` Peter Korsgaard
[not found] ` <20160321173000.GD4751@excalibur.cnev.de>
2016-03-21 20:56 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2016-03-18 17:33 François-David Collin
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=56EA8C5E.1070701@redhat.com \
--to=hdegoede@redhat.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox