test suite reviews and discussions
 help / color / mirror / Atom feed
From: Jin Ling <jin.ling@intel.com>
To: dts@dpdk.org
Cc: Jin Ling <jin.ling@intel.com>
Subject: [DTS][PATCH V1 01/10] conf/crbs.cfg: add parameters
Date: Sun, 16 Jul 2023 17:07:45 +0800	[thread overview]
Message-ID: <20230716090753.1590148-2-jin.ling@intel.com> (raw)
In-Reply-To: <20230716090753.1590148-1-jin.ling@intel.com>

    Add parameters to connect mev and acc via serial port

Signed-off-by: Jin Ling <jin.ling@intel.com>
---
 conf/crbs.cfg | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/conf/crbs.cfg b/conf/crbs.cfg
index a12e60a4..051c5d9e 100644
--- a/conf/crbs.cfg
+++ b/conf/crbs.cfg
@@ -19,6 +19,10 @@ dut_user=root
 dut_passwd=
 os=linux
 dut_arch=
+dut_acc_port = 
+dut_acc_baudrate = 
+dut_imc_port = /dev/ttyUSB2 
+dut_imc_baudrate = 460800
 tester_ip=xxx.xxx.xxx.xxx
 tester_passwd=
 ixia_group=
-- 
2.34.1


  reply	other threads:[~2023-07-16  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16  9:07 [DTS][PATCH V1 00/10] add functions to test MEV Jin Ling
2023-07-16  9:07 ` Jin Ling [this message]
2023-07-16  9:07 ` [DTS][PATCH V1 02/10] execution.cfg: add parameters to choose datapath and create vport when running test scripts Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 03/10] framework/config: save the serial port connection info of imc and acc to the self.crb Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 04/10] framework/crb:modify code when pexpect contains '#', replace '#' with 'mev-acc' Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 05/10] framework/dts: add global variables Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 06/10] framework/dut: add new functions to set up test mev env Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 07/10] framework/pmd_output: optimize function start_testpmd Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 08/10] framework/project_dpdk: optimize code Jin Ling
2023-07-16  9:07 ` [DTS][PATCH V1 09/10] framework/settings: add drivers and NICs for mev Jin Ling

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=20230716090753.1590148-2-jin.ling@intel.com \
    --to=jin.ling@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).