From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@armh.onmicrosoft.com header.s=selector1-arm-com header.b=hG1jJICo; spf=pass (domain: arm.com, ip: 40.107.8.71, mailfrom: supreeth.venkatesh@arm.com) Received: from EUR04-VI1-obe.outbound.protection.outlook.com (EUR04-VI1-obe.outbound.protection.outlook.com [40.107.8.71]) by groups.io with SMTP; Wed, 24 Apr 2019 11:23:43 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x9fEfmfw4aOtiedtmA1Zx4krMTxLtXJjd83GT1zOe9E=; b=hG1jJICodsHjAnoq89OuqXzdkmJEQkG7YtzohczTjnmgySNo8L2Hk/IMukVlKu3kbEcZsPhnQiWvFwLd+cJ80AdweYst9B6+nmEnhSF0KepM9xAMXtNoj/W3xOYiqlOZmtCfRGnXNvMolH3+jRqDAGilUtjrs+KCdygXJLSwzcY= Received: from VE1PR08MB5165.eurprd08.prod.outlook.com (20.179.30.215) by VE1PR08MB4925.eurprd08.prod.outlook.com (10.255.114.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.16; Wed, 24 Apr 2019 18:23:39 +0000 Received: from VE1PR08MB5165.eurprd08.prod.outlook.com ([fe80::79a9:1f16:48e8:2c28]) by VE1PR08MB5165.eurprd08.prod.outlook.com ([fe80::79a9:1f16:48e8:2c28%4]) with mapi id 15.20.1835.010; Wed, 24 Apr 2019 18:23:39 +0000 From: "Supreeth Venkatesh" To: Prakriti Chauhan , "devel@edk2.groups.io" CC: "Jin, Eric" Subject: Re: [edk2-test]Regarding using any shell command in SCT Thread-Topic: [edk2-test]Regarding using any shell command in SCT Thread-Index: AdT6xzZ9xMdFIZKHQc+V4ozjAMt4LQ== Date: Wed, 24 Apr 2019 18:23:39 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Supreeth.Venkatesh@arm.com; x-originating-ip: [217.140.111.135] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 4a2c1c81-50c6-4bf7-1209-08d6c8e1f945 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020);SRVR:VE1PR08MB4925; x-ms-traffictypediagnostic: VE1PR08MB4925: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-forefront-prvs: 00179089FD x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(376002)(346002)(136003)(396003)(366004)(39860400002)(40434004)(199004)(189003)(53936002)(55016002)(54896002)(6306002)(236005)(9686003)(2906002)(8936002)(110136005)(7736002)(26005)(2501003)(66066001)(316002)(33656002)(68736007)(86362001)(8676002)(81166006)(74316002)(606006)(97736004)(6506007)(102836004)(99286004)(53546011)(186003)(66946007)(7696005)(5024004)(66446008)(71200400001)(76116006)(256004)(64756008)(66556008)(71190400001)(14444005)(73956011)(66476007)(81156014)(52536014)(5660300002)(14454004)(229853002)(486006)(6436002)(4326008)(72206003)(6246003)(790700001)(478600001)(3846002)(966005)(6116002)(25786009)(476003);DIR:OUT;SFP:1101;SCL:1;SRVR:VE1PR08MB4925;H:VE1PR08MB5165.eurprd08.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:1;MX:1; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 80MslgH+xFv5AgS0TRcCxcBbfu4ZxW1wWNMLgGhHd5HbBmsMnNu1t/LK6eiBw5LSCdjduM6r2Av+Df16fojOtEppEVpBoUOP0tvRQvrNoBARS7u8HCtW3bUj3xZzsISjMJ9/3/L+t9MK21wXXJ8/6jefa/QkX0O4eUgMxPsYatmP4EEbjZEb7DLHb3cEZ9tG3Ibwobfmlu+eY3+y1u3Sadob7wd+GTcglvHpX0/WzRP0zd7frJ1/1298gMwymQChYzGxvXo8ZIZ1G6ahqF7rIZ2mEzHBLimnnobIr3ZodeUEqe22quPhsBlQtAS9SIwF/MIE4rMCwnSNBUj8NbIIyIwsHRgEg+cHhj2YgCG7ze0MYX9R4G4qjqWfuROk7vps0EAdQVSHxsdxNZwNAjmI/IJG2sx0Opi/m4zEdkmHS0A= MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-Network-Message-Id: 4a2c1c81-50c6-4bf7-1209-08d6c8e1f945 X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Apr 2019 18:23:39.3183 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1PR08MB4925 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_VE1PR08MB51656D95DFBC1DB2120C7E2B803C0VE1PR08MB5165eurp_" --_000_VE1PR08MB51656D95DFBC1DB2120C7E2B803C0VE1PR08MB5165eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Changing subject line to include [edk2-test]. + Eric Prakriti, With the disclaimer that UEFI SCT is intended for testing against UEFI spec= ification, I will try to answer your question in the way I interpreted it. I am not sure whether you are asking how to test EFI_SHELL_PROTOCOL or is i= t related to a non uefi standard device interface you want to test? Assuming it as the latter and with the limited information you mentioned ab= out your requirement, I am assuming you will have a non-standard Protocol/D= river for your device and want to test those APIs. With the above assumption, you can follow any of the standard test cases as= reference for implementing your own test. Example below: https://github.com/tianocore/edk2-test/tree/master/uefi-sct/SctPkg/TestCase= /UEFI/IHV/Protocol/DeviceIo/BlackBoxTest Eric can provide more information based on detailed explanation of your req= uirements. Thanks, Supreeth From: Prakriti Chauhan Sent: Wednesday, April 24, 2019 4:28 AM To: Supreeth Venkatesh ; devel@edk2.groups.io Subject: Regarding using any shell command in SCT Hi, I want to test if my interface is working or not using SCT framework, like = give IP address to interface and then run ping command. Any pointers how can I achieve same? Thanks, Prakriti IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you. --_000_VE1PR08MB51656D95DFBC1DB2120C7E2B803C0VE1PR08MB5165eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Changing subject line to include [edk2-test].

+ Eric

 

Prakriti,

With the disclaimer that UEFI SCT is intended for te= sting against UEFI specification, I will try to answer your question in the= way I interpreted it.

 

I am not sure whether you are asking how to test EFI= _SHELL_PROTOCOL or is it related to a non uefi standard device interface yo= u want to test?

Assuming it as the latter and with the limited infor= mation you mentioned about your requirement, I am assuming you will have a = non-standard Protocol/Driver for your device and want to test those APIs.

With the above assumption, you can follow any of the= standard test cases as reference for implementing your own test. Example b= elow:

https://github.com/tianocore/edk2-test/tree/master/uefi-sct/SctPkg/TestCas= e/UEFI/IHV/Protocol/DeviceIo/BlackBoxTest

 

Eric can provide more information based on detailed = explanation of your requirements.

 

Thanks,

Supreeth

 

From: Prakriti Chauhan <prakriti.chauhan@n= xp.com>
Sent: Wednesday, April 24, 2019 4:28 AM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; devel@edk= 2.groups.io
Subject: Regarding using any shell command in SCT

 

Hi,

 

 

&nb= sp;

I want t= o test if my interface is working or not using SCT framework, like give IP = address to interface and then run ping command.

 

Any poin= ters how can I achieve same?

 

 

 

Thanks,

Prakriti

IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in any medium. Thank you. --_000_VE1PR08MB51656D95DFBC1DB2120C7E2B803C0VE1PR08MB5165eurp_--