From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by dpdk.org (Postfix) with ESMTP id 2288E58F7 for ; Wed, 14 Jan 2015 17:28:02 +0100 (CET) Received: by mail-wi0-f170.google.com with SMTP id bs8so27628811wib.1 for ; Wed, 14 Jan 2015 08:28:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=SRDFKVzhyZVVrIyNVWbz64MM6mYz0P4wAMzXpYTEqkc=; b=D237QsXDqW7D0jrofzIWM4BUo1qJrWbWtOBqlrEcdn5LW4rOorir+7bgFbpj3QPVgl HZv3kHyHe8Kjd7pcjH3vmrDiIdknJm/zRwaE83vlY++GiQHbqT7oYI8ySJirlXCaW4sh 2xEhWnMV2pFQFzzaU/K27yZrhG1dL6F4cMtBbotlten+nac+E4CTrjs47Yc20i3yF5kr m+UpkZPsFzg/r7oNQkZZCYtvi5tIwKj96qiNLm21TWEQ4BVQDNSvd98q9MQiY2AzOIMa eJlq2nSTOvtX1zdN0UXW7N1jj8StrvG4HOXN9vp/9ZHAgihovshrnp6es1RRtVdCAFps cWAA== X-Gm-Message-State: ALoCoQk8HVBgV48yVJ1b9AtGzMJqs4zjZhdGZLElLUFH2IiTkwb7v/KFdQXOwRitwiR9o9zfuijt X-Received: by 10.180.198.166 with SMTP id jd6mr10129477wic.18.1421252881004; Wed, 14 Jan 2015 08:28:01 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id g2sm22651746wjn.11.2015.01.14.08.27.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jan 2015 08:28:00 -0800 (PST) From: Thomas Monjalon To: Ravi Kerur Date: Wed, 14 Jan 2015 17:27:38 +0100 Message-ID: <3180122.JKDOmAPjoA@xps13> Organization: 6WIND User-Agent: KMail/4.14.3 (Linux/3.17.6-1-ARCH; KDE/4.14.3; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Q on Support for I217 and I218 Intel chipsets. 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: Wed, 14 Jan 2015 16:28:02 -0000 2015-01-09 04:41, Ravi Kerur: > Thomas, > > Please let me know how I can move forward on this. If i confine changes in > e1000/ directory to e1000_osdep.h file only and the rest in PMD will that > work? The reason I ask is because of following comment in README file. > > ... > Few changes to the original FreeBSD sources were made to: > - Adopt it for PMD usage mode: > e1000_osdep.c > e1000_osdep.h > ... This is an Intel driver so you should ask to the responsible of this code at Intel. The problem is that there is not really an identified responsible for this driver. The rule is to not change the base driver, even osdep files. But it would be better to have an exception here. PS: please avoid top-posting. > On Mon, Jan 5, 2015 at 8:40 AM, Ravi Kerur wrote: > > > Inline > > > > On Mon, Jan 5, 2015 at 12:55 AM, Thomas Monjalon < > > thomas.monjalon@6wind.com> wrote: > > > >> 2015-01-04 15:28, Ravi Kerur: > >> > We have a Gigabyte H97N motherboard which has I217 Intel chipset which > >> uses > >> > e100e drivers. I looked into lib/librte_pmd_e1000 directory and I do see > >> > that e1000e code is integrated but missing some support for read/write > >> from > >> > flash_address and other minor things. I have made changes shown below > >> and > >> > have done some testing with testpmd utility and now have following > >> questions > >> > > >> > 1. What amount of testing is required to qualify patch as successfully > >> > tested on new chipsets > >> > >> There is no good answer to this question. Generally, you must be sure that > >> you don't break anything. > >> So you must test the code paths you have changed. > >> > > > > yes I have done testing on Ubuntu for I217 using testpmd. > > > >> > >> > 2. FreeBSD testing, currently we have Ubuntu 14.04 installed on existing > >> > H97N motherboard and testing is done solely on Linux. We plan to get > >> > another motherboard which will have I218 chipset and still deciding > >> whether > >> > to go with FreeBSD or Ubuntu. So the question I have is what amount of > >> > testing should be done on FreeBSD? I don't think > >> setup.sh/dpdk_nic_bind.py > >> > works on FreeBSD yet hence the question on testing. > >> > >> FreeBSD testing is required when patching common EAL, scripts or > >> makefiles. > >> > >> > > lib/librte_pmd_e1000/e1000/e1000_api.c | 21 > >> +++++++++++++++++++++ > >> > > lib/librte_pmd_e1000/e1000/e1000_api.h | 1 + > >> > > lib/librte_pmd_e1000/e1000/e1000_osdep.h | 24 > >> +++++++++++++++++++----- > >> > >> These files are part of the base driver. > >> The rule is to not patch them and try to do the changes in PMD only. > >> There can be exceptions if an Intel maintainer acknowledges it. > >> > > > > Changes in these files are modifying existing macros > > > > E1000_READ_FLASH_REG, > > E1000_WRITE_FLASH_REG > > ... > > > > If it is not recommended to modify these files, should I move macros into > > some PMD file? > > > > Thanks.