AW: AW: Re: Broken ethernet on SolidRun cubox-i // plaintext re-send

Christoph Mattheis christoph.mattheis at arcor.de
Wed Jan 27 15:46:02 EST 2021




Von: christoph.mattheis at arcor.de
Gesendet: 27.01.2021 21:38
An: Christoph Mattheis <christoph.mattheis at arcor.de>,Russell King - ARM Linux admin <linux at armlinux.org.uk>,Michael Walle <michael at walle.cc>
Kopie: <acmattheis at gmx.net>,<linux-arm-kernel at lists.infradead.org>,Matus Ujhelyi <ujhelyi.m at gmail.com>
Betreff: AW: Re: Broken ethernet on SolidRun cubox-i

Dear all, justed wanted to check if my email from 12.Jan 2021 has been received as I never got any reply
- or did I said anything in that email that offended anybody? - if so, I'm sorry, pls accept my sincere apologies BR Chris


Von: Christoph Mattheis <christoph.mattheis at arcor.de>
Gesendet: 12.01.2021 01:15
An: Russell King - ARM Linux admin <linux at armlinux.org.uk>,Michael Walle <michael at walle.cc>
Kopie: <acmattheis at gmx.net>,<linux-arm-kernel at lists.infradead.org>,Matus Ujhelyi <ujhelyi.m at gmail.com>
Betreff: Re: Broken ethernet on SolidRun cubox-i

Hello Russell, sorry for not coming back to you earlier - but creating a DT-File for a non-kernel-developing mortal human being turned out to be a bit more difficult than expected - amplified by things like dtc has a command-line switch for "include" path but does not understand the #include directive - however, after a few more hours I finally made it and can confirm your patch is fixing the issue.
proof:

[ 19.608738] Qualcomm Atheros AR8035 2188000.ethernet-1:04: attached PHY driver [Qualcomm Atheros AR8035] (mii_bus:phy_addr=2188000.ethernet-1:04, irq=POLL)
[ 22.689922] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 22.689962] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 33.249092] brcm_reg: disabling
chris at cubox-i:~$ uname -a
Linux cubox-i 5.9.14-imx6 #20.11.3 SMP Fri Dec 11 20:57:51 CET 2020 armv7l GNU/Linux

can you pls make this permanent ?
and if I may comment on your statement:
>>Kernel development is fundamentally a difficult, frustrating and depressing activity.
I was never complaining about anything nor blamed anybody - the exact opposite is true, I honestly admire your work and feel thankful for everything Linux and people like you brought to us / the world - every time I switch on my TV, start my car, grab my Android phone - every thing where Linux is inside - I can imagine the hours of lifetime which have gone into it to make it what it is today - especially you Russell, I found some files with your name in it stating 1995-2002 (!) - where the master of ceremony, Linus, might be a technical genius but is also known for lacking basic social skills and empathy. As one out of million nameless users who benefit from your work ... I would like to send you a big "Thank you", you really make a difference -
As a Linux (heavy) user I found my *first* bug in kernel 2.2 in a tape driver which was already fixed in 2.4 - and 17years later I found a *second" issue, this one you just fixed - don't ask for the number of bugs I reported to M$ in the time in between
@Michael - also thanks for your support in this issue !
Thanks again & regards Chris 





More information about the linux-arm-kernel mailing list