From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) by dpdk.org (Postfix) with ESMTP id 98A1B1396 for ; Thu, 2 Jul 2015 16:10:58 +0200 (CEST) Received: by qkhu186 with SMTP id u186so52445186qkh.0 for ; Thu, 02 Jul 2015 07:10:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=N1blNsTBDfv6F7N1jkjjhf7hADeWb0OPnVlLMrlyMPc=; b=AeZG7ik3Pk4rLHU645xsvl/j4KpUEnsXeRxQtm4mFM1faKYmiimrRvjc8N/AefE6nN kf5Q+TU5KrMkyb0Aju46OOMq8byzFRccq+95+A+5teGqz/uA/5WQWdo4zCWZye/rpXWv eAvee5MOgN+XRDqbgV39v0EPWNYQzCh9SZg9aMPaE1n221lDtpts93AWnE0GpGJWYQQE xWNzGoJA7K92X9WKJlpUBwq9/jMGCxOVh5ae5yuU2rul+xlFcHkgmpynFTmtyw+ZzfOV +jQvcYC4hiAmzTIoBMFMFotuyl6uTTmNvrtWmDbz9N5R9znpxjXNQideO5fPzx8nLDcR z8gg== MIME-Version: 1.0 X-Received: by 10.140.234.1 with SMTP id f1mr43386639qhc.48.1435846258168; Thu, 02 Jul 2015 07:10:58 -0700 (PDT) Received: by 10.140.28.101 with HTTP; Thu, 2 Jul 2015 07:10:58 -0700 (PDT) Date: Thu, 2 Jul 2015 17:10:58 +0300 Message-ID: From: Alexander Belyakov To: "dev@dpdk.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Intel bypass device 0x155C support? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2015 14:10:59 -0000 Hello, I have got my hands on Intel=C2=AE Ethernet Server Bypass Adapter X540-T2 (device_id 0x155C, copper). Unfortunately the only bypass device currently supported by DPDK is 0x155D (fiber). Does anyone know about the plans of adding 0x155C support? Thank you, Alexander Belyakov