netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@intel.com>
To: sbs <gexlie@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"e1000-devel@lists.sourceforge.net"
	<e1000-devel@lists.sourceforge.net>
Subject: Re: IGB driver upgrade
Date: Mon, 28 Jun 2010 17:00:18 -0700	[thread overview]
Message-ID: <4C293792.6070508@intel.com> (raw)
In-Reply-To: <AANLkTinUoQG4BWC4Q2UFDwGvAwYujlUXz6P-ZLkZozaQ@mail.gmail.com>

sbs wrote:
> Hello guys.
> 
> Is it possible to upgrade intel gigabit adapter's e1000 driver to
> 2.2.9? This is the latest version according to Intel website.
> 
I assume you are referring to the igb driver since that is what is in 
the subject and not the e1000 driver correct?

> I've got a problem with 2.1.0-k2 drivers statically compiled into kernel.
> 
> Surely I can download drivers from intel and compile it as module, but
> I need to compile it statically
> Intel drivers do not provide sources for static compilation :(
> 
> Is it possible to upgrade drivers to igb-2.2.9 in the source tree and
> allow the static compilation of them?
> 
Normally the upstream driver should be up to date with any fixes that 
are in the standalone module.  What version of the kernel are you 
currently running?  Also have your tried testing the older standalone 
igb modules to see if the same issues exist there in either igb 2.1.9 or 
  igb 2.0.6?  This would help us to determine what changes in the 
standalone module might be missing from the in-kernel version of the driver.

> Because having 2.1.0-k2 we experience some strange random freezes with
> network interface which can be fixed only by restarting network.
> 
> 2.2.9 module has no such problems but we need to use static kernels
> according to our policy.

I have CCed our e1000-devel list.  In the future you may want to CC this 
list as it will provide better visibility to the Intel wired networking 
maintainers.

Thanks,

Alex

  reply	other threads:[~2010-06-29  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim6kfnr6yNeUXlLHOztB-qjyvj50D4p7nebqj9r@mail.gmail.com>
2010-06-28 22:02 ` IGB driver upgrade sbs
2010-06-29  0:00   ` Alexander Duyck [this message]
2010-06-29  9:50     ` sbs
2010-06-29 16:15       ` Alexander Duyck
2010-07-05  6:45         ` sbs
2010-07-08 12:45           ` sbs

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=4C293792.6070508@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=gexlie@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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).