From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: distrokit@pengutronix.de
Subject: [DistroKit] [PATCH 0/2] v7a: fix beaglebone networking
Date: Sat, 8 Jan 2022 08:57:21 +0100 [thread overview]
Message-ID: <20220108075723.432333-1-a.fatoum@pengutronix.de> (raw)
Upstream device tree changed TI CPSW (network controller) node our kernel
and barebox to a new one with a compatible we don't match against.
Fix this up for kernel and barebox and while at it import one more
beaglebone fix from barebox master.
Ahmad Fatoum (2):
v7a: kernel: enable new TI CPSW switchdev driver
v7a: barebox: cherry-pick CPSW/Linux reboot fixes from master
configs/platform-v7a/kernelconfig | 9 +-
...port-for-new-binding-in-Linux-v5.15-.patch | 210 ++++++++++++++++++
...-beaglebone-init-MPU-speed-to-800Mhz.patch | 45 ++++
.../patches/barebox-2021.11.0/series | 2 +
4 files changed, 263 insertions(+), 3 deletions(-)
create mode 100644 configs/platform-v7a/patches/barebox-2021.11.0/0001-net-cpsw-add-support-for-new-binding-in-Linux-v5.15-.patch
create mode 100644 configs/platform-v7a/patches/barebox-2021.11.0/0002-Revert-ARM-beaglebone-init-MPU-speed-to-800Mhz.patch
create mode 100644 configs/platform-v7a/patches/barebox-2021.11.0/series
--
2.30.2
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next reply other threads:[~2022-01-08 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 7:57 Ahmad Fatoum [this message]
2022-01-08 7:57 ` [DistroKit] [PATCH 1/2] v7a: kernel: enable new TI CPSW switchdev driver Ahmad Fatoum
2022-01-08 8:01 ` Ahmad Fatoum
2022-01-08 7:57 ` [DistroKit] [PATCH 2/2] v7a: barebox: cherry-pick CPSW/Linux reboot fixes from master Ahmad Fatoum
2022-01-08 9:37 ` [DistroKit] [PATCH 0/2] v7a: fix beaglebone networking Robert Schwebel
2022-01-09 5:45 ` Sohaib Mohamed
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=20220108075723.432333-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.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