All of lore.kernel.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: steve@sakoman.com
Cc: openembedded-core@lists.openembedded.org
Subject: [OE-core][scarthgap v2 2/8] linux-yocto/6.6: fix beaglebone ethernet
Date: Thu, 29 May 2025 12:57:48 -0400	[thread overview]
Message-ID: <20250529165754.264501-2-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20250529165754.264501-1-bruce.ashfield@gmail.com>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/6.6:

1/1 [
    Author: Colin Foster
    Email: colin.foster@in-advantage.com
    Subject: ARM: dts: am335x-bone-common: Increase MDIO reset deassert time
    Date: Fri, 31 May 2024 13:38:17 -0500

    Prior to commit df16c1c51d81 ("net: phy: mdio_device: Reset device only
    when necessary") MDIO reset deasserts were performed twice during boot.
    Now that the second deassert is no longer performed, device probe
    failures happen due to the change in timing with the following error
    message:

    SMSC LAN8710/LAN8720: probe of 4a101000.mdio:00 failed with error -5

    Restore the original effective timing, which resolves the probe
    failures.

    Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
    Link: https://lore.kernel.org/r/20240531183817.2698445-1-colin.foster@in-advantage.com
    Signed-off-by: Kevin Hilman <khilman@baylibre.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../linux/linux-yocto-rt_6.6.bb               |  2 +-
 .../linux/linux-yocto-tiny_6.6.bb             |  2 +-
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 22 +++++++++----------
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb
index c3f2c35b1f..e0006035fe 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb
@@ -14,7 +14,7 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "0588a366e1193d9ac23855c4a3c2c784d5ca512b"
+SRCREV_machine ?= "4c94a7140a0416421cd82fe18703e99d7c4eec8e"
 SRCREV_meta ?= "39d19bc9f333a0bfb88cd55befe70d5da87adcf8"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb
index ae0316dade..8c0617be10 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb
@@ -17,7 +17,7 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "93714069321a8e2f7d01f51038cc1d9afd64a57b"
+SRCREV_machine ?= "50111c8145a573a5eb34859736492d3914d74f26"
 SRCREV_meta ?= "39d19bc9f333a0bfb88cd55befe70d5da87adcf8"
 
 PV = "${LINUX_VERSION}+git"
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.6.bb b/meta/recipes-kernel/linux/linux-yocto_6.6.bb
index 55304a1929..061837ec88 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.6.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.6.bb
@@ -18,17 +18,17 @@ KBRANCH:qemux86-64 ?= "v6.6/standard/base"
 KBRANCH:qemuloongarch64  ?= "v6.6/standard/base"
 KBRANCH:qemumips64 ?= "v6.6/standard/mti-malta64"
 
-SRCREV_machine:qemuarm ?= "00f5a7d26256a6c96f4c624ed2fcc2915baf69ed"
-SRCREV_machine:qemuarm64 ?= "44c07335c9354d22e1059b773cc5acc6d5997acb"
-SRCREV_machine:qemuloongarch64 ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
-SRCREV_machine:qemumips ?= "6f7f7ea73242088f08c504a73144e7c3649548f8"
-SRCREV_machine:qemuppc ?= "af203c26b7349967003580d373f7bb4e32b53c5a"
-SRCREV_machine:qemuriscv64 ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
-SRCREV_machine:qemuriscv32 ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
-SRCREV_machine:qemux86 ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
-SRCREV_machine:qemux86-64 ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
-SRCREV_machine:qemumips64 ?= "98b3401fbd220385715648e6bea870482419e7c1"
-SRCREV_machine ?= "aa6b73545c4594842542c8943dce67fe397e91cc"
+SRCREV_machine:qemuarm ?= "c7fc26b463b6d492177ab4f3133ac709f72959e6"
+SRCREV_machine:qemuarm64 ?= "a2123abde1b536e17d6f8b41c07006b1b78fc14e"
+SRCREV_machine:qemuloongarch64 ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
+SRCREV_machine:qemumips ?= "441ff4147581f8866ccb145ee1fcecb418543a46"
+SRCREV_machine:qemuppc ?= "c186535e4a16fe6524c963f40744f56d56cc37ae"
+SRCREV_machine:qemuriscv64 ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
+SRCREV_machine:qemuriscv32 ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
+SRCREV_machine:qemux86 ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
+SRCREV_machine:qemux86-64 ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
+SRCREV_machine:qemumips64 ?= "ef983636bee26dd17055fbff877a6ca4cd10e4ed"
+SRCREV_machine ?= "6a5b2ed821525dac9e4f3f5283376f02965d3a7b"
 SRCREV_meta ?= "39d19bc9f333a0bfb88cd55befe70d5da87adcf8"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
-- 
2.39.2



  reply	other threads:[~2025-05-29 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 16:57 [OE-core][scarthgap v2 1/8] linux-yocto/6.6: update to v6.6.85 bruce.ashfield
2025-05-29 16:57 ` bruce.ashfield [this message]
2025-05-29 16:57 ` [OE-core][scarthgap v2 3/8] linux-yocto/6.6: update to v6.6.86 bruce.ashfield
2025-05-29 16:57 ` [OE-core][scarthgap v2 4/8] linux-yocto/6.6: update to v6.6.87 bruce.ashfield
2025-05-29 16:57 ` [OE-core][scarthgap v2 5/8] linux-yocto/6.6: update to v6.6.88 bruce.ashfield
2025-05-29 16:57 ` [OE-core][scarthgap v2 6/8] linux-yocto/6.6: update to v6.6.89 bruce.ashfield
2025-05-29 16:57 ` [OE-core][scarthgap v2 7/8] linux-yocto/6.6: update to v6.6.91 bruce.ashfield
2025-05-29 16:57 ` [OE-core][scarthgap v2 8/8] linux-yocto/6.6: update to v6.6.92 bruce.ashfield

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=20250529165754.264501-2-bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.com \
    /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.