From: Ender Hsieh <andhsieh@nvidia.com>
To: <linux-aspeed@lists.ozlabs.org>
Cc: Jacky Chou <jacky_chou@aspeedtech.com>,
Marc Olberding <molberding@nvidia.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: NVL32 BMC enablement — offering help on ftgmac100 work
Date: Tue, 28 Apr 2026 12:30:48 +0900 [thread overview]
Message-ID: <20260428033048.2694433-1-andhsieh@nvidia.com> (raw)
Hi Jacky, hi linux-aspeed,
I'm Ender Hsieh from NVIDIA, working on enabling the NVL32 BMC
platform (AST2600, msx4 design — the one Marc Olberding added in
commit f28674fab34f) on upstream OpenBMC.
I've been tracking the ftgmac100 cleanup work going on recently
(the 2025-07 .. 2026-02 batch around DT probe, MDIO setup, match
data refactoring) — looks like solid groundwork.
Could you share a summary of where the Aspeed networking stack
work is at right now? Happy to coordinate on-list or off-list,
whichever works for you.
Thanks,
Ender Hsieh
andhsieh@nvidia.com
next reply other threads:[~2026-04-28 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 3:30 Ender Hsieh [this message]
2026-04-28 3:40 ` 回覆: NVL32 BMC enablement — offering help on ftgmac100 work 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
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=20260428033048.2694433-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