public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dario <dario86@tutamail.com>
To: u-boot@lists.denx.de
Subject: Old regression possibly affecting many devices with build options in Kconfig files
Date: Thu, 23 Apr 2020 19:27:23 +0200 (CEST)	[thread overview]
Message-ID: <M5c45j_--3-2@tutamail.com> (raw)

Hello,

On 2017/02/07 commit af2cbfd6b982f7a52414ea50b2ece0290d4b748f broke gigabit ethernet for Olimex A20-OLinuXino-LIME2. This commit likely prevents the activation of the option CONFIG_RTL8211X_PHY_FORCE_MASTER needed for proper gigabit networking on this device. Since the only modification introduced by this commit was moving Kconfig files, I suspect this change may affect many more devices as well for which proper build options may not be enabled.

Apart from how this went unnoticed for such a long time, what really puzzles me is commit 8728c97eff5bd95f58320f886ae305f17931a374 submitted on 2017/03/13 which removes CONFIG_RTL8211X_PHY_FORCE_MASTER from configs/A20-OLinuXino-Lime2_defconfig altogether.

I think it is not by chance that Arch Linux ARM kept the package uboot-a20-olinuxino-lime2 at version 2017.01-2 which is the last working version before the aforementioned commit broke gigabit ethernet for this board.

My A20-OLinuXino-Lime2 is the only device I have available for testing. My fear is that many more devices may be affected since this same option was removed from A20-Olimex-SOM-EVB_defconfig as well along with several other options from many other devices.

             reply	other threads:[~2020-04-23 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 17:27 Dario [this message]
2020-04-24 11:54 ` [PATCH] sunxi: A20-OLinuXino-Lime2: enable PHY config to fix broken ethernet Anatolij Gustschin
2020-05-01 16:46   ` Jagan Teki
2020-05-01 16:55     ` Anatolij Gustschin
2020-04-24 12:04 ` Old regression possibly affecting many devices with build options in Kconfig files Anatolij Gustschin
2020-04-24 15:45   ` Tom Rini
2020-04-24 15:47   ` Dario

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=M5c45j_--3-2@tutamail.com \
    --to=dario86@tutamail.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