<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/ethernet/freescale, branch linux-3.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-11-09T22:08:36Z</updated>
<entry>
<title>gianfar: ethernet vanishes after restoring from hibernation</title>
<updated>2012-11-09T22:08:36Z</updated>
<author>
<name>Wang Dongsheng</name>
</author>
<published>2012-11-09T04:43:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=103cdd1d59e1ab6abccb049093239cc8e6295816'/>
<id>urn:sha1:103cdd1d59e1ab6abccb049093239cc8e6295816</id>
<content type='text'>
If a gianfar ethernet device is down prior to hibernating a
system, it will no longer be present upon system restore.

For example:

	~# ifconfig eth0 down
	~# echo disk &gt; /sys/power/state

	  &lt;trigger a restore from hibernation&gt;

	~# ifconfig eth0 up
	SIOCSIFFLAGS: No such device

This happens because the restore function bails out early upon
finding devices that were not up at hibernation.  In doing so,
it never gets to the netif_device_attach call at the end of
the restore function.  Adding the netif_device_attach as done
here also makes the gfar_restore code consistent with what is
done in the gfar_resume code.

Cc: Claudiu Manoil &lt;claudiu.manoil@freescale.com&gt;
Signed-off-by: Wang Dongsheng &lt;dongsheng.wang@freescale.com&gt;
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Acked-by: Claudiu Manoil &lt;claudiu.manoil@freescale.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>gianfar_ptp: use iomem, not ioports resource tree in probe</title>
<updated>2012-10-25T03:18:59Z</updated>
<author>
<name>Wei Yang</name>
</author>
<published>2012-10-24T05:21:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2b9c128e9580e79db48bd3aacb2b4873544e01e8'/>
<id>urn:sha1:2b9c128e9580e79db48bd3aacb2b4873544e01e8</id>
<content type='text'>
When using a 36 bit dtb file, the driver complains "resource busy".

Investigating the source of the message leads one to the
gianfar_ptp_probe function.

Since the type of the device resource requested in this function
is IORESOURCE_MEM, it should use "iomem_resource" instead of
"ioports_resource".

Signed-off-by: Wei Yang &lt;Wei.Yang@windriver.com&gt;
Cc: Claudiu Manoil &lt;claudiu.manoil@freescale.com&gt;
Cc: Timur Tabi &lt;timur@freescale.com&gt;
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: fix typo in freescale/ucc_geth.c</title>
<updated>2012-10-09T04:21:38Z</updated>
<author>
<name>Michael Neuling</name>
</author>
<published>2012-10-08T23:52:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=66eef59f22275002f621ff9d951886b513d011b3'/>
<id>urn:sha1:66eef59f22275002f621ff9d951886b513d011b3</id>
<content type='text'>
The following patch:
  acb600d net: remove skb recycling
added dev_free_skb() to drivers/net/ethernet/freescale/ucc_geth.c

This is a typo and should be dev_kfree_skb().  This fixes this.

Signed-off-by: Michael Neuling &lt;mikey@neuling.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: remove skb recycling</title>
<updated>2012-10-07T04:40:54Z</updated>
<author>
<name>Eric Dumazet</name>
</author>
<published>2012-10-05T06:23:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=acb600def2110b1310466c0e485c0d26299898ae'/>
<id>urn:sha1:acb600def2110b1310466c0e485c0d26299898ae</id>
<content type='text'>
Over time, skb recycling infrastructure got litle interest and
many bugs. Generic rx path skb allocation is now using page
fragments for efficient GRO / TCP coalescing, and recyling
a tx skb for rx path is not worth the pain.

Last identified bug is that fat skbs can be recycled
and it can endup using high order pages after few iterations.

With help from Maxime Bizon, who pointed out that commit
87151b8689d (net: allow pskb_expand_head() to get maximum tailroom)
introduced this regression for recycled skbs.

Instead of fixing this bug, lets remove skb recycling.

Drivers wanting really hot skbs should use build_skb() anyway,
to allocate/populate sk_buff right before netif_receive_skb()

Signed-off-by: Eric Dumazet &lt;edumazet@google.com&gt;
Cc: Maxime Bizon &lt;mbizon@freebox.fr&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2012-09-28T18:40:49Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-09-28T18:40:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a06e5e1bb217be077e1f8ee2745b4c5b1aa02db'/>
<id>urn:sha1:6a06e5e1bb217be077e1f8ee2745b4c5b1aa02db</id>
<content type='text'>
Conflicts:
	drivers/net/team/team.c
	drivers/net/usb/qmi_wwan.c
	net/batman-adv/bat_iv_ogm.c
	net/ipv4/fib_frontend.c
	net/ipv4/route.c
	net/l2tp/l2tp_netlink.c

The team, fib_frontend, route, and l2tp_netlink conflicts were simply
overlapping changes.

qmi_wwan and bat_iv_ogm were of the "use HEAD" variety.

With help from Antonio Quartulli.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>gianfar: Change default HW Tx queue scheduling mode</title>
<updated>2012-09-24T20:25:16Z</updated>
<author>
<name>Claudiu Manoil</name>
</author>
<published>2012-09-23T22:39:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b98b8babd6e3370fadb7c6eaacb00eb2f6344a6c'/>
<id>urn:sha1:b98b8babd6e3370fadb7c6eaacb00eb2f6344a6c</id>
<content type='text'>
This is primarily to address transmission timeout occurrences, when
multiple H/W Tx queues are being used concurrently. Because in
the priority scheduling mode the controller does not service the
Tx queues equally (but in ascending index order), Tx timeouts are
being triggered rightaway for a basic test with multiple simultaneous
connections like:
iperf -c &lt;server_ip&gt; -n 100M -P 8

resulting in kernel trace:
NETDEV WATCHDOG: eth1 (fsl-gianfar): transmit queue &lt;X&gt; timed out
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:255
...
and controller reset during intense traffic, and possibly further
complications.

This patch changes the default H/W Tx scheduling setting (TXSCHED)
for multi-queue devices, from priority scheduling mode to a weighted
round robin mode with equal weights for all H/W Tx queues, and
addresses the issue above.

Signed-off-by: Claudiu Manoil &lt;claudiu.manoil@freescale.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ptp: link the phc device to its parent device</title>
<updated>2012-09-22T19:42:38Z</updated>
<author>
<name>Richard Cochran</name>
</author>
<published>2012-09-22T07:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1ef761582c074448bae5be97abde5934667e7710'/>
<id>urn:sha1:1ef761582c074448bae5be97abde5934667e7710</id>
<content type='text'>
PTP Hardware Clock devices appear as class devices in sysfs. This patch
changes the registration API to use the parent device, clarifying the
clock's relationship to the underlying device.

Signed-off-by: Richard Cochran &lt;richardcochran@gmail.com&gt;
Acked-by: Ben Hutchings &lt;bhutchings@solarflare.com&gt;
Acked-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>gianfar: fix phc index build failure</title>
<updated>2012-09-21T17:45:29Z</updated>
<author>
<name>Richard Cochran</name>
</author>
<published>2012-09-20T19:11:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=28889b7e7818342f6c254e27b9b2c68702ab867a'/>
<id>urn:sha1:28889b7e7818342f6c254e27b9b2c68702ab867a</id>
<content type='text'>
This patch fixes a build failure introduced in commit 66636287
("gianfar: Support the get_ts_info ethtool method."). Not only was a
global variable inconsistently named, but also it was not exported as
it should have been.

This fix is also needed in stable version 3.5.

Signed-off-by: Richard Cochran &lt;richardcochran@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2012-08-31T19:14:18Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-08-31T19:14:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c32f38619af6302da58835fb292b159bdd96d11f'/>
<id>urn:sha1:c32f38619af6302da58835fb292b159bdd96d11f</id>
<content type='text'>
Merge the 'net' tree to get the recent set of netfilter bug fixes in
order to assist with some merge hassles Pablo is going to have to deal
with for upcoming changes.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net/fsl_pq_mdio: add support for the Fman 1G MDIO controller</title>
<updated>2012-08-30T17:29:32Z</updated>
<author>
<name>Timur Tabi</name>
</author>
<published>2012-08-29T08:08:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=761743ebc92df72053e736fce953a5d2e90099d5'/>
<id>urn:sha1:761743ebc92df72053e736fce953a5d2e90099d5</id>
<content type='text'>
The MDIO controller on the Frame Manager (Fman) is compatible with the
QE and Gianfar MDIO controllers, but we don't care about the TBI because
the Ethernet drivers (FMD) take care of programming it.

Signed-off-by: Timur Tabi &lt;timur@freescale.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
