<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net, branch v2.6.37.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/net?h=v2.6.37.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/net?h=v2.6.37.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-03-14T21:17:39Z</updated>
<entry>
<title>drivers/net: Call netif_carrier_off at the end of the probe</title>
<updated>2011-03-14T21:17:39Z</updated>
<author>
<name>Ivan Vecera</name>
<email>ivecera@redhat.com</email>
</author>
<published>2011-02-15T02:08:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fea891e387dbd48bbe13d5a588059e879eaa8dfe'/>
<id>urn:sha1:fea891e387dbd48bbe13d5a588059e879eaa8dfe</id>
<content type='text'>
commit 0d672e9f8ac320c6d1ea9103db6df7f99ea20361 upstream.

Without calling of netif_carrier_off at the end of the probe the operstate
is unknown when the device is initially opened. By default the carrier is
on so when the device is opened and netif_carrier_on is called the link
watch event is not fired and operstate remains zero (unknown).

This patch fixes this behavior in forcedeth and r8169.

Signed-off-by: Ivan Vecera &lt;ivecera@redhat.com&gt;
Acked-by: Francois Romieu &lt;romieu@fr.zoreil.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>r8169: prevent RxFIFO induced loops in the irq handler.</title>
<updated>2011-03-14T21:17:39Z</updated>
<author>
<name>Francois Romieu</name>
<email>romieu@fr.zoreil.com</email>
</author>
<published>2011-02-03T16:27:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=30b7cb312baeab0504e4ba1bc5b324abf7afcf68'/>
<id>urn:sha1:30b7cb312baeab0504e4ba1bc5b324abf7afcf68</id>
<content type='text'>
commit f60ac8e7ab7cbb413a0131d5665b053f9f386526 upstream.

While the RxFIFO interruption is masked for most 8168, nothing prevents
it to appear in the irq status word. This is no excuse to crash.

Signed-off-by: Francois Romieu &lt;romieu@fr.zoreil.com&gt;
Cc: Ivan Vecera &lt;ivecera@redhat.com&gt;
Cc: Hayes &lt;hayeswang@realtek.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>r8169: RxFIFO overflow oddities with 8168 chipsets.</title>
<updated>2011-03-14T21:17:38Z</updated>
<author>
<name>Francois Romieu</name>
<email>romieu@fr.zoreil.com</email>
</author>
<published>2011-02-03T11:02:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=be70b4e2c60c2d7e03c3193cadd1cb9eddb5e4bc'/>
<id>urn:sha1:be70b4e2c60c2d7e03c3193cadd1cb9eddb5e4bc</id>
<content type='text'>
commit 1519e57fe81c14bb8fa4855579f19264d1ef63b4 upstream.

Some experiment-based action to prevent my 8168 chipsets locking-up hard
in the irq handler under load (pktgen ~1Mpps). Apparently a reset is not
always mandatory (is it at all ?).

- RTL_GIGA_MAC_VER_12
- RTL_GIGA_MAC_VER_25
  Missed ~55% packets. Note:
  - this is an old SiS 965L motherboard
  - the 8168 chipset emits (lots of) control frames towards the sender

- RTL_GIGA_MAC_VER_26
  The chipset does not go into a frenzy of mac control pause when it
  crashes yet but it can still be crashed. It needs more work.

Signed-off-by: Francois Romieu &lt;romieu@fr.zoreil.com&gt;
Cc: Ivan Vecera &lt;ivecera@redhat.com&gt;
Cc: Hayes &lt;hayeswang@realtek.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>r8169: use RxFIFO overflow workaround for 8168c chipset.</title>
<updated>2011-03-14T21:17:38Z</updated>
<author>
<name>Ivan Vecera</name>
<email>ivecera@redhat.com</email>
</author>
<published>2011-01-27T11:24:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cb1f3fd3ba182cd514e2b72487a5f84932e6a03b'/>
<id>urn:sha1:cb1f3fd3ba182cd514e2b72487a5f84932e6a03b</id>
<content type='text'>
commit b5ba6d12bdac21bc0620a5089e0f24e362645efd upstream.

I found that one of the 8168c chipsets (concretely XID 1c4000c0) starts
generating RxFIFO overflow errors. The result is an infinite loop in
interrupt handler as the RxFIFOOver is handled only for ...MAC_VER_11.
With the workaround everything goes fine.

Signed-off-by: Ivan Vecera &lt;ivecera@redhat.com&gt;
Acked-by: Francois Romieu &lt;romieu@fr.zoreil.com&gt;
Cc: Hayes &lt;hayeswang@realtek.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ixgbe: fix for 82599 erratum on Header Splitting</title>
<updated>2011-03-14T21:17:34Z</updated>
<author>
<name>Don Skidmore</name>
<email>donald.c.skidmore@intel.com</email>
</author>
<published>2011-01-18T22:53:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1e405a0b1b2beaf98da098e0a6711d243f5136ff'/>
<id>urn:sha1:1e405a0b1b2beaf98da098e0a6711d243f5136ff</id>
<content type='text'>
commit a124339ad28389093ed15eca990d39c51c5736cc upstream.

We have found a hardware erratum on 82599 hardware that can lead to
unpredictable behavior when Header Splitting mode is enabled.  So
we are no longer enabling this feature on affected hardware.

Please see the 82599 Specification Update for more information.

Signed-off-by: Don Skidmore &lt;donald.c.skidmore@intel.com&gt;
Tested-by: Stephen Ko &lt;stephen.s.ko@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ath9k: Fix ath9k prevents CPU to enter C3 states</title>
<updated>2011-03-14T21:17:33Z</updated>
<author>
<name>Mohammed Shafi Shajakhan</name>
<email>mshajakhan@atheros.com</email>
</author>
<published>2011-03-04T22:00:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4ae96ec5efcee1c3a5d6665e714d2e7add9533ea'/>
<id>urn:sha1:4ae96ec5efcee1c3a5d6665e714d2e7add9533ea</id>
<content type='text'>
This is a backport of upstream commit 0f5cd45960173ba5b36727decbb4a241cbd35ef9.

The DMA latency issue is observed only in Intel pinetrail platforms
but in the driver we had a default PM-QOS value of 55. This caused
unnecessary power consumption and battery drain in other platforms.

Remove the pm-qos thing in the driver code and address the throughput
issue in Intel pinetrail platfroms in user space using any one of
the scripts in below links:

http://www.kernel.org/pub/linux/kernel/people/mcgrof/scripts/cpudmalatency.c
http://johannes.sipsolutions.net/files/netlatency.c.txt

More details can be found in the following bugzilla link:

https://bugzilla.kernel.org/show_bug.cgi?id=27532

Signed-off-by: Thomas Bächler &lt;thomas@archlinux.org&gt;
Acked-by: Mohammed Shafi Shajakhan &lt;mshajakhan@atheros.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>e1000e: disable broken PHY wakeup for ICH10 LOMs, use MAC wakeup instead</title>
<updated>2011-03-07T23:05:26Z</updated>
<author>
<name>Bruce Allan</name>
<email>bruce.w.allan@intel.com</email>
</author>
<published>2011-02-02T09:30:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ef4fba5d0fc816eff781d6dc70d76ebc0ac8909e'/>
<id>urn:sha1:ef4fba5d0fc816eff781d6dc70d76ebc0ac8909e</id>
<content type='text'>
commit 4def99bbfd46e05c5e03b5b282cb4ee30e27ff19 upstream.

When support for 82577/82578 was added[1] in 2.6.31, PHY wakeup was in-
advertently enabled (even though it does not function properly) on ICH10
LOMs.  This patch makes it so that the ICH10 LOMs use MAC wakeup instead
as was done with the initial support for those devices (i.e. 82567LM-3,
82567LF-3 and 82567V-4).

[1] commit a4f58f5455ba0efda36fb33c37074922d1527a10

Reported-by: Aurelien Jarno &lt;aurelien@aurel32.net&gt;
Signed-off-by: Bruce Allan &lt;bruce.w.allan@intel.com&gt;
Signed-off-by: Jeff Kirsher &lt;jeffrey.t.kirsher@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>r8169: disable ASPM</title>
<updated>2011-03-07T23:05:26Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-02-22T02:00:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=048882f265645e2258a6d6380622b8a1a3634217'/>
<id>urn:sha1:048882f265645e2258a6d6380622b8a1a3634217</id>
<content type='text'>
commit ba04c7c93bbcb48ce880cf75b6e9dffcd79d4c7b upstream.

For some time is known that ASPM is causing troubles on r8169, i.e. make
device randomly stop working without any errors in dmesg.

Currently Tomi Leppikangas reports that system with r8169 device hangs
with MCE errors when ASPM is enabled:
https://bugzilla.redhat.com/show_bug.cgi?id=642861#c4

Lets disable ASPM for r8169 devices at all, to avoid problems with
r8169 PCIe devices at least for some users.

Reported-by: Tomi Leppikangas &lt;tomi.leppikangas@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.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>carl9170: add Airlive X.USB a/b/g/n USBID</title>
<updated>2011-03-07T23:05:25Z</updated>
<author>
<name>Jan Puk</name>
<email>janpuk@volny.cz</email>
</author>
<published>2011-02-22T13:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d70c044346d70fb9c4980da7c5c581260f41305'/>
<id>urn:sha1:5d70c044346d70fb9c4980da7c5c581260f41305</id>
<content type='text'>
commit c86664e5a285af1afa06416e450e7c4af04daa7c upstream.

"AirLive X.USB now works perfectly under a Linux
environment!"

Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54usb: add Senao NUB-350 usbid</title>
<updated>2011-03-07T23:05:24Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2011-02-26T11:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cea4131a1d2ae214544678113eac6497ba5299e5'/>
<id>urn:sha1:cea4131a1d2ae214544678113eac6497ba5299e5</id>
<content type='text'>
commit 2b799a6b25bb9f9fbc478782cd9503e8066ab618 upstream.

Reported-by: Mark Davis
Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
