DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Renyong Wan" <wanry@yunsilicon.com>
To: <dev@dpdk.org>
Cc: "Na Na" <nana@yunsilicon.com>, "Rong Qian" <qianr@yunsilicon.com>,
	 <zhenghy@yunsilicon.com>, <weihg@yunsilicon.com>,
	<jacky@yunsilicon.com>
Subject: Yunsilicon XSC PMD roadmap for 25.11
Date: Thu, 21 Aug 2025 11:42:14 +0800	[thread overview]
Message-ID: <50ba16f1-3421-46e7-ac28-11907ec56b09@yunsilicon.com> (raw)

Please find below Yunsilicon XSC PMD roadmap for 25.11 release:

1. Supports link status and link event
2. Supports getting FW version
3. Supports TSO
4. Supports Promiscuous mode
5. Supports Module EEPROM dump
6. Supports FEC mode
7. Supports link speed configuration
8. Code optimiztions and bug fix

-- 
Best regards,
Renyong Wan

                 reply	other threads:[~2025-08-21  3:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50ba16f1-3421-46e7-ac28-11907ec56b09@yunsilicon.com \
    --to=wanry@yunsilicon.com \
    --cc=dev@dpdk.org \
    --cc=jacky@yunsilicon.com \
    --cc=nana@yunsilicon.com \
    --cc=qianr@yunsilicon.com \
    --cc=weihg@yunsilicon.com \
    --cc=zhenghy@yunsilicon.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;
as well as URLs for NNTP newsgroup(s).