Quoting Jonas Smedegaard (2022-06-09 12:25:01)
> This bug was fixed since u-boot 2022.04 - specifically in git commit
> f11513d9: https://source.denx.de/u-boot/u-boot/-/commit/f11513d
Correction - the actual fix was the later git commit 85da5587:
Quoting Jonas Smedegaard (2019-04-26 09:54:37)
> Quoting Sunil Mohan Adapa (2019-04-25 21:30:03)
> > > Were your Lime2 boards connected with a cross-over cable or via a
> > > switch during those tests?
> >
> > Lime2 was connected to a laptop via a cross-over cable (actually
> > regular cable
Here's what I know (the "should work" entries need confirmation):
Lime2 rev.C
---
* Uses Realtek rev.C PHY
* Works fine in 1Gbit mode with Debian stable U-boot
* Works fine in 1Gbit mode with Debian stable kernel
* Possibly still sold as some no-eMMC no-flash options
Lime2 rev.G
On 27/04/19 2:46 am, Andreas B. Mundt wrote:
> Hi all,
>
> On Fri, Apr 26, 2019 at 09:54:37AM +0200, Jonas Smedegaard wrote:
>>
>> So a summary of the tests is this:
>>
>> Board, cable mode, patchset \ Measured speed in Mbit/sec
>> rev.G2 1Gbit mode pristine:14 & 722
>> rev.G2 1Gbit mode
Hi all,
On Fri, Apr 26, 2019 at 09:54:37AM +0200, Jonas Smedegaard wrote:
>
> So a summary of the tests is this:
>
> Board, cable mode, patchset \ Measured speed in Mbit/sec
> rev.G2 1Gbit mode pristine:14 & 722
> rev.G2 1Gbit mode TX_DELAY=4: 428 & 774
> rev.C 1Gbit pristine: 1 &
Quoting Jonas Smedegaard (2019-04-26 09:54:37)
> Would be good to have tests explicitly in master vs. slave mode.
Seems master/slave can at least be probed (and possibly forced) in linux
with ethtool, and in u-boot with mii
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
*
Quoting Sunil Mohan Adapa (2019-04-25 21:30:03)
> >
> > It seems you forgot to attach the mentioned Olimex report.
>
> The report is in the inline section "Report from Olimex team (with
> Rev.G2)". I used term 'attached' loosely.
Ahh: You _quoted_ Olimex from "Report from Olimex team (with
>
> It seems you forgot to attach the mentioned Olimex report.
The report is in the inline section "Report from Olimex team (with
Rev.G2)". I used term 'attached' loosely.
>
> Do I understand you correctly that the attached patch is what Olimex
> propose but that you do *not* recommended to use
The following is the patch Olimex has applied on u-boot for the images
that they build. It is meant to work for all hardware revisions of Lime2.
https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/a20-phy_1000_100-dram.patch
It does not seem suitable for
It seems mainline u-boot bootstrao all lime2 devices equally, whereas
Olimex fork of u-boot treats "newer than G and "newer than E" specially:
https://github.com/OLIMEX/u-boot/commit/6c32a3c9d31432884751966fcb0f15b1fd930446
* Realtek rev.C PHY (board rev.C) get no tweak (but see bug#845128)
Hi Sunil,
> Olimex team working with FreedomBox team have noticed a significant
> slowdown in Gigabit Ethernet when transmitting. Original report from
> Olimex team is attached. This is applicable for hardware Rev.G2 of the
> A20 OLinuXino Lime2 board.
It seems you forgot to attach the
Source: u-boot
Version: 2019.01+dfsg-4
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
Olimex team working with FreedomBox team have noticed a significant slowdown in
Gigabit Ethernet when transmitting. Original report from Olimex team is
attached. This is
12 matches
Mail list logo
