test suite reviews and discussions
 help / color / mirror / Atom feed
From: Song Jiale <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Song Jiale <songx.jiale@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/userspace_ethtool: modify dts script to support 82599 NIC
Date: Fri,  6 Jan 2023 11:28:11 +0000	[thread overview]
Message-ID: <20230106112812.324038-1-songx.jiale@intel.com> (raw)

in case on 82599 NIC to read the eeprom, please use 'length' parameter
to reduce size to 0x4000.

Signed-off-by: Song Jiale <songx.jiale@intel.com>
---
 tests/TestSuite_userspace_ethtool.py | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/tests/TestSuite_userspace_ethtool.py b/tests/TestSuite_userspace_ethtool.py
index d8db9073..b62e732f 100644
--- a/tests/TestSuite_userspace_ethtool.py
+++ b/tests/TestSuite_userspace_ethtool.py
@@ -406,6 +406,17 @@ class TestUserspaceEthtool(TestCase):
             self.dut.send_expect(
                 "ethtool --eeprom-dump %s raw on > %s" % (intf, ethtool_eeprom), "# "
             )
+            if self.kdriver == "ixgbe":
+                self.dut.send_expect(
+                    "ethtool --eeprom-dump %s length 0x4000 raw on > %s"
+                    % (intf, ethtool_eeprom),
+                    "# ",
+                )
+            else:
+                self.dut.send_expect(
+                    "ethtool --eeprom-dump %s raw on > %s" % (intf, ethtool_eeprom),
+                    "# ",
+                )
             # wait for file ready
             time.sleep(2)
             # dpdk userspcae tools dump eeprom file size different with kernel ethtool dump
-- 
2.25.1


             reply	other threads:[~2023-01-06  3:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 11:28 Song Jiale [this message]
2023-01-06 11:28 ` [dts] [PATCH V1 2/2] test_plans/userspace_ethtool: add note Song Jiale

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=20230106112812.324038-1-songx.jiale@intel.com \
    --to=songx.jiale@intel.com \
    --cc=dts@dpdk.org \
    /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).