From: Ender Hsieh <andhsieh@nvidia.com>
To: <jacky_chou@aspeedtech.com>
Cc: Andrew Lunn <andrew@lunn.ch>, <linux-aspeed@lists.ozlabs.org>,
"Marc Olberding" <molberding@nvidia.com>
Subject: Re: NVL32 BMC enablement — offering help on ftgmac100 work
Date: Wed, 29 Apr 2026 00:14:16 +0900 [thread overview]
Message-ID: <20260428151416.1700609-1-andhsieh@nvidia.com> (raw)
In-Reply-To: <SEYPR06MB513489D0B8F5BC77258EA1FF9D372@SEYPR06MB5134.apcprd06.prod.outlook.com>
Hi Jacky,
Thanks for the update on the AST2700 ftgmac100 plans.
A bit of context from our side: we're working on the OpenBMC upstream
effort for nvl32 (the AST2600-based msx4 platform Marc Olberding
upstreamed in commit f28674fab34f). To get host networking working on
our test platform we currently carry a local kernel patch in the
OpenBMC layer that re-adds the mac0/mdio3/ethphy3 nodes, but holding
it there long-term goes against upstream-first principles and the
Gerrit reviewer has flagged it.
Given AST2600 ftgmac100 work is sequenced after the AST2700 series,
do you have any suggestions on how we could resolve this using
upstream resources — e.g. an interim path that's acceptable to the
community while we wait for the proper driver fix? Any pointer on
the right shape (RFC PATCH, openbmc/linux backport, something else)
would help us a lot.
Thanks,
Ender
next prev parent reply other threads:[~2026-04-28 15:15 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 [this message]
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
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=20260428151416.1700609-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