DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Howard Wang <howard_wang@realsil.com.cn>, dev@dpdk.org
Cc: pro_nic_dpdk@realtek.com,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2] r8125: add r8125 ethernet poll mode driver
Date: Fri, 5 Jul 2024 22:12:37 +0100	[thread overview]
Message-ID: <9860873a-8071-4348-a3cc-62b192cc210e@amd.com> (raw)
In-Reply-To: <20240613033650.5521-1-howard_wang@realsil.com.cn>

On 6/13/2024 4:36 AM, Howard Wang wrote:
> r8125 is for Realtek 2.5 Gigabit Ethernet NICs.
> 
> Signed-off-by: Howard Wang <howard_wang@realsil.com.cn>
>

Hi Howard,

Thanks for contributing to DPDK. I remember Realtek drivers mentioned a
few times in the past, it is great to see it will be publicly available.

Can you please give some more details which devices, SoC or specific
boards etc supported with these driver(s) (r8125 & r8126 in other patch)?
What is the motivation for the upstreaming, like is this for a customer
or to enable people experiment DPDK on boards with Realtek NICs etc..?


Btw, there were some offline suggestions from David & Thomas, let me try
to summurise them first here:

- Can r8125 & r8126 drivers combined into single driver, perhaps with
some common code? Assuming two drivers are common enough to put together.

- Can you please split the patch into multiple commits, so that it
becomes easier to review and analyze later. There is another driver
upstreaming in progress, you can check it as sample:
https://patches.dpdk.org/project/dpdk/list/?series=32313&state=%2A&archive=both

- Use a real person as maintainer, and in .mailmap file instead of alias


Also I can see some binary data in the driver, are they necessary to
keep in the driver, like:
mcu_patch_code_8125a_2()
rtl8125_real_set_phy_mcu_8125a_1()
rtl8125_real_set_phy_mcu_8125a_2()
phy_mcu_ram_code_8125b_1
...
phy_mcu_ram_code_8125d_1_1
...

They are taking space and as they are binary there is no way for driver
to understand / update / fix them..


For both this one and r8126, I will wait for next version to review further.

Thanks,
ferruh



  reply	other threads:[~2024-07-05 21:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  6:15 [PATCH] " Howard Wang
2024-05-28 21:36 ` Stephen Hemminger
2024-05-29  2:11   ` 答复: " 王颢
2024-06-13  3:36 ` [PATCH v2] " Howard Wang
2024-07-05 21:12   ` Ferruh Yigit [this message]
2024-07-08  5:43     ` 答复: " 王颢
2024-07-10 10:23       ` Ferruh Yigit
2024-06-12  9:51 Howard Wang

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=9860873a-8071-4348-a3cc-62b192cc210e@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=howard_wang@realsil.com.cn \
    --cc=pro_nic_dpdk@realtek.com \
    --cc=thomas@monjalon.net \
    /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).