From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tim.o'driscoll@intel.com>
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65])
 by dpdk.org (Postfix) with ESMTP id 1C9705A35
 for <dev@dpdk.org>; Thu, 15 Jan 2015 22:23:18 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga103.jf.intel.com with ESMTP; 15 Jan 2015 13:18:51 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="441096579"
Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153])
 by FMSMGA003.fm.intel.com with ESMTP; 15 Jan 2015 13:09:22 -0800
Received: from irsmsx102.ger.corp.intel.com ([169.254.2.213]) by
 IRSMSX101.ger.corp.intel.com ([169.254.1.126]) with mapi id 14.03.0195.001;
 Thu, 15 Jan 2015 21:22:19 +0000
From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Ravi Kerur <rkerur@gmail.com>, Thomas Monjalon <thomas.monjalon@6wind.com>
Thread-Topic: [dpdk-dev] Q on Support for I217 and I218 Intel chipsets.
Thread-Index: AQHQKHYoqtOiMJqf/0SRafz+Pmt4iZyxOdCAgACBywCABga8AIAIGsEAgAHXQYCAAAwDAA==
Date: Thu, 15 Jan 2015 21:22:18 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C9972F@IRSMSX102.ger.corp.intel.com>
References: <CAFb4SLBH4SJ2kL-JeCziXMtiG-g+F3b6wQ__6fSjsTWq7LzO3A@mail.gmail.com>
 <CAFb4SLAvUiiDHuevRK5Qk_GYCii7LqfOAr+ADw9ezxdEcq_QRg@mail.gmail.com>
 <CAFb4SLCr-JF9LGXF_rmW-cEHEjPkh_pP-e1kcTO0h8wQWbMvVA@mail.gmail.com>
 <3180122.JKDOmAPjoA@xps13>
 <CAFb4SLDs3wVDpOOLtH3Lg1h3+c8ZpzgKZUz3MMO17Akqoc1B9Q@mail.gmail.com>
In-Reply-To: <CAFb4SLDs3wVDpOOLtH3Lg1h3+c8ZpzgKZUz3MMO17Akqoc1B9Q@mail.gmail.com>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 21:23:19 -0000

> On Thursday, January 15, 2015  at 8:34 PM, Ravi Kerur <rkerur@gmail.com> =
wrote:
>=20
> On Wed, Jan 14, 2015 at 8:27 AM, Thomas Monjalon
> <thomas.monjalon@6wind.com>
> wrote:
>=20
> > 2015-01-09 04:41, Ravi Kerur:
> > > Thomas,
> > >
> > > Please let me know how I can move forward on this. If i confine chang=
es
> > 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 fil=
e.
> > >
> > > ...
> > > 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 co=
de
> > at Intel.
> > The problem is that there is not really an identified responsible for t=
his
> > 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.
> >
>=20
> <rk> Please let me know who is the contact person from Intel so I can add
> him/her to "To" list when I send the patch or Should I contact Jim St Leg=
er
> and ask him about this?

We're looking into this, but don't have a definitive answer yet. Somebody f=
rom Intel will reply as soon as we've confirmed whether the change you prop=
osed is OK or not.


Tim