<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/stable/linux-stable.git/drivers/net/e1000, branch linux-2.6.28.y</title>
<subtitle>Linux kernel stable tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/atom?h=linux-2.6.28.y</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/atom?h=linux-2.6.28.y'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/'/>
<updated>2009-02-12T17:50:28+00:00</updated>
<entry>
<title>e1000: Fix PCI enable to honor the need_ioport flag</title>
<updated>2009-02-12T17:50:28+00:00</updated>
<author>
<name>Karsten Keil</name>
<email>kkeil@suse.de</email>
</author>
<published>2009-02-03T23:18:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=df19ea14c317dafc61cde95f918a5783ac56a593'/>
<id>urn:sha1:df19ea14c317dafc61cde95f918a5783ac56a593</id>
<content type='text'>
commit 4d7155b932b8129c72e2f2714890e20b2a05e0b7 upstream.

On machine were no IO ports are assigned the call
to pci_enable_device() will fail, even if need_ioport
is false, we need to use pci_enable_device_mem() here.

Signed-off-by: Karsten Keil &lt;kkeil@suse.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>e1000: fix bug with shared interrupt during reset</title>
<updated>2009-02-12T17:50:27+00:00</updated>
<author>
<name>Jesse Brandeburg</name>
<email>jesse.brandeburg@intel.com</email>
</author>
<published>2009-01-28T00:41:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=c784f619619bec525d7791f8b527cc363d708c16'/>
<id>urn:sha1:c784f619619bec525d7791f8b527cc363d708c16</id>
<content type='text'>
commit 15b2bee22a0390d951301b53e83df88d0350c499 upstream.

A nasty bug was found where an MTU change (or anything else that caused a
reset) could race with the interrupt code.  The interrupt code was entered
by a shared interrupt during the MTU change.

This change prevents the interrupt code from running while the driver is in
the middle of its reset path.

Signed-off-by: Jesse Brandeburg &lt;jesse.brandeburg@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>e1000: Use device_set_wakeup_enable</title>
<updated>2008-11-16T09:35:56+00:00</updated>
<author>
<name>\"Rafael J. Wysocki\</name>
<email>rjw@sisk.pl</email>
</author>
<published>2008-11-07T20:30:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=de1264896c8012a261c1cba17e6a61199c276ad3'/>
<id>urn:sha1:de1264896c8012a261c1cba17e6a61199c276ad3</id>
<content type='text'>
Since dev-&gt;power.should_wakeup bit is used by the PCI core to
decide whether the device should wake up the system from sleep
states, set/unset this bit whenever WOL is enabled/disabled using
e1000_set_wol().  Accordingly, use device_can_wakeup() for checking
if wake-up is supported by the device.

Signed-off-by: "Rafael J. Wysocki" &lt;rjw@sisk.pl&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>e1000: allow VLAN devices to use TSO and CSUM offload</title>
<updated>2008-10-11T19:25:59+00:00</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2008-10-11T19:25:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=20501a69818827884b4381cdcedefdb5e7892915'/>
<id>urn:sha1:20501a69818827884b4381cdcedefdb5e7892915</id>
<content type='text'>
This patch changes e1000 to set vlan_features so TSO and CSUM
offload can be used by VLAN devices, similar as with the other
Intel drivers.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Jesse Brandeburg &lt;jesse.brandeburg@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>e1000: don't generate bad checksums for tcp packets with 0 csum</title>
<updated>2008-10-09T21:29:26+00:00</updated>
<author>
<name>Dave Graham</name>
<email>david.graham@intel.com</email>
</author>
<published>2008-10-09T21:29:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=3ed30676f5bc9960c67644fa37c5fdc36ae47b5b'/>
<id>urn:sha1:3ed30676f5bc9960c67644fa37c5fdc36ae47b5b</id>
<content type='text'>
When offloading transmit checksums only, the driver was not
correctly configuring the hardware to handle the case of a zero
checksum.  For UDP the correct behavior is to leave it alone, but
for tcp the checksum must be changed from 0x0000 to 0xFFFF.  The
hardware takes care of this case but only if it is told the
packet is tcp.

same patch as e1000e

Signed-off-by: Dave Graham &lt;david.graham@intel.com&gt;
Signed-off-by: Jesse Brandeburg &lt;jesse.brandeburg@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6</title>
<updated>2008-10-01T13:12:56+00:00</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2008-10-01T13:12:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=b262e60309e1b0eb25d300c7e739427d5316abb1'/>
<id>urn:sha1:b262e60309e1b0eb25d300c7e739427d5316abb1</id>
<content type='text'>
Conflicts:

	drivers/net/wireless/ath9k/core.c
	drivers/net/wireless/ath9k/main.c
	net/core/dev.c
</content>
</entry>
<entry>
<title>e1000: remove unused Kconfig option for disabling packet split</title>
<updated>2008-09-25T02:17:42+00:00</updated>
<author>
<name>Brandeburg, Jesse</name>
<email>jesse.brandeburg@intel.com</email>
</author>
<published>2008-09-16T20:01:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=630b25cdf4e3f8c0a11eb04fc8436cc36653cd58'/>
<id>urn:sha1:630b25cdf4e3f8c0a11eb04fc8436cc36653cd58</id>
<content type='text'>
Since the e1000/e1000e split, no hardware supported by e1000
supports packet split, just remove the Kconfig option and associated
code from the driver.

Signed-off-by: Jesse Brandeburg &lt;jesse.brandeburg@intel.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>e1000: prevent corruption of EEPROM/NVM</title>
<updated>2008-09-19T01:40:24+00:00</updated>
<author>
<name>Christopher Li</name>
<email>chrisl@vmware.com</email>
</author>
<published>2008-09-05T21:04:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=78566fecbb12a7616ae9a88b2ffbc8062c4a89e3'/>
<id>urn:sha1:78566fecbb12a7616ae9a88b2ffbc8062c4a89e3</id>
<content type='text'>
Andrey reports e1000 corruption, and that a patch in vmware's ESX fixed
it.

The EEPROM corruption is triggered by concurrent access of the EEPROM
read/write. Putting a lock around it solve the problem.

[akpm@linux-foundation.org: use DEFINE_SPINLOCK to avoid confusing lockdep]
Signed-off-by: Christopher Li &lt;chrisl@vmware.com&gt;
Reported-by: Andrey Borzenkov &lt;arvidjaar@mail.ru&gt;
Cc: Zach Amsden &lt;zach@vmware.com&gt;
Cc: Pratap Subrahmanyam &lt;pratap@vmware.com&gt;
Cc: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Cc: Jesse Brandeburg &lt;jesse.brandeburg@intel.com&gt;
Cc: Bruce Allan &lt;bruce.w.allan@intel.com&gt;
Cc: PJ Waskiewicz &lt;peter.p.waskiewicz.jr@intel.com&gt;
Cc: John Ronciak &lt;john.ronciak@intel.com&gt;
Cc: Jeff Garzik &lt;jeff@garzik.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>e1000: fix stack size</title>
<updated>2008-08-27T20:56:27+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2008-08-27T08:14:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=16ecf85a5ca7345efbcbb2de76607db0f7ec9049'/>
<id>urn:sha1:16ecf85a5ca7345efbcbb2de76607db0f7ec9049</id>
<content type='text'>
Here's the patch. It shrinks the stack from 1152 bytes to 192 bytes (the
first version, that only did the e1000_option part, got it down to 600
bytes). About half comes from not using multiple "e1000_option"
structures, the other half comes from turning the "e1000_opt_list[]"
arrays into "static const" instead, so that gcc doesn't copy them onto the
stack.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Reveiewed-by: Auke Kok &lt;auke-jan.h.kok@intel.com&gt;
Tested-by: Emil Tantilov &lt;emil.s.tantilov@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>e1000: make ioport free</title>
<updated>2008-07-22T23:39:14+00:00</updated>
<author>
<name>Taku Izumi</name>
<email>izumi.taku@jp.fugitsu.com</email>
</author>
<published>2008-07-11T22:17:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=81250297d85b26eb4e9de5decf752dce430277f9'/>
<id>urn:sha1:81250297d85b26eb4e9de5decf752dce430277f9</id>
<content type='text'>
This patch makes e1000 driver ioport-free.
This corrects behavior in probe function so as not to request ioport
resources as long as they are not really needed.  This is based on the
ioport-free patch of e1000 driver from Auke Kok and Tomohiro Kusumi.

Signed-off-by: Tomohiro Kusumi &lt;kusumi.tomohiro@jp.fujitsu.com&gt;
Signed-off-by: Auke Kok &lt;auke-jan.h.kok@intel.com&gt;
Signed-off-by: Taku Izumi &lt;izumi.taku@jp.fujitsu.com&gt;
Signed-off-by: Jeff Kirsher&lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
</feed>
