From: Ender Hsieh <andhsieh@nvidia.com>
To: <andrew@lunn.ch>
Cc: <jacky_chou@aspeedtech.com>, <linux-aspeed@lists.ozlabs.org>,
<molberding@nvidia.com>
Subject: Re: NVL32 BMC enablement — offering help on ftgmac100 work
Date: Thu, 30 Apr 2026 01:31:17 +0900 [thread overview]
Message-ID: <20260429163117.2228665-1-andhsieh@nvidia.com> (raw)
In-Reply-To: <eac09481-0ba1-4ac2-ad8c-d859822ff0d5@lunn.ch>
> The quick and easy fix for getting patches merged into Mainline Linux
> is to patch the bootloader. Stop it enabling delays in the MAC. You
> can then use the correct phy-mode. If you go this way, place make it
> clear in the commit message you have modified the bootloader.
Thanks Andrew — and thanks Jacky for the earlier steer too.
We're already on this path. I have a local branch with both U-Boot and
kernel dts switched to phy-mode = "rgmii-id", and the &scu
mac0-clk-delay block removed from the U-Boot dts.
We'll validate end-to-end on hardware first, then send the patches.
I'll make sure the commit messages on both the U-Boot and kernel sides
clearly note that the bootloader has been modified to stop enabling
the MAC delays, so reviewers see the relationship between the two.
> If you decide you want to make changes to the MAC driver, do it,
> post patches, and they will get reviewed.
Appreciated — but unfortunately tight timelines on our side mean I
can't take on the smarter MAC driver work right now. I'll keep it on
my radar as a follow-up if bandwidth allows.
Thanks again,
Ender
prev parent reply other threads:[~2026-04-29 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 3:30 NVL32 BMC enablement — offering help on ftgmac100 work Ender Hsieh
2026-04-28 3:40 ` 回覆: " Jacky Chou
2026-04-28 15:14 ` Ender Hsieh
2026-04-29 2:08 ` 回覆: NVL32 BMC enablement ― " Jacky Chou
2026-04-29 12:57 ` 回覆: NVL32 BMC enablement — " Andrew Lunn
2026-04-29 16:31 ` Ender Hsieh [this message]
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=20260429163117.2228665-1-andhsieh@nvidia.com \
--to=andhsieh@nvidia.com \
--cc=andrew@lunn.ch \
--cc=jacky_chou@aspeedtech.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=molberding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox