From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Q on Support for I217 and I218 Intel chipsets.
Date: Wed, 14 Jan 2015 17:27:38 +0100 [thread overview]
Message-ID: <3180122.JKDOmAPjoA@xps13> (raw)
In-Reply-To: <CAFb4SLCr-JF9LGXF_rmW-cEHEjPkh_pP-e1kcTO0h8wQWbMvVA@mail.gmail.com>
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 <rkerur@gmail.com> wrote:
>
> > Inline <rk>
> >
> > 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.
> >>
> >
> > <rk> 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.
> >>
> >
> > <rk> 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.
next prev parent reply other threads:[~2015-01-14 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 23:28 Ravi Kerur
2015-01-05 8:55 ` Thomas Monjalon
2015-01-05 16:40 ` Ravi Kerur
2015-01-09 12:41 ` Ravi Kerur
2015-01-14 16:27 ` Thomas Monjalon [this message]
2015-01-15 20:34 ` Ravi Kerur
2015-01-15 21:22 ` O'driscoll, Tim
2015-01-15 23:54 ` Ananyev, Konstantin
2015-01-16 10:52 ` Bruce Richardson
2015-01-16 11:08 ` Ananyev, Konstantin
2015-01-16 11:31 ` Bruce Richardson
2015-01-16 12:01 ` Ananyev, Konstantin
2015-01-22 0:03 ` Ravi Kerur
2015-01-16 1:14 ` Zhang, Helin
2015-01-16 1:43 ` Ravi Kerur
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=3180122.JKDOmAPjoA@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.com \
/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).