<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/net/ethernet/faraday, branch dev-4.6</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.6</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.6'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2016-07-12T09:58:20+00:00</updated>
<entry>
<title>drivers/net/ftgmac100: Adapt for Aspeed SoCs</title>
<updated>2016-07-12T09:58:20+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2016-06-24T07:08:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=ab753f2f6623f12ae459e6f693db8997db45f985'/>
<id>urn:sha1:ab753f2f6623f12ae459e6f693db8997db45f985</id>
<content type='text'>
The RXDES and TXDES registers bits in the ftgmac100 indicates EDO{R,T}R
at bit position 15 for the Faraday Tech IP. However, the version of this
IP present in the Aspeed SoCs has these bits at position 30 in the
registers.

It appers that ast2400 SoCs support both positions, with the 15th bit
marked as reserved but still functional. In the ast2500 this bit is
reused for another function, so we need a work around.

This was confirmed with engineers from Aspeed that using bit 30 is
correct for both the ast2400 and ast2500 SoCs.

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>drivers/net/ftgmac100: Make EDO{R,T}R bits configurable</title>
<updated>2016-07-12T09:58:07+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2016-06-03T06:31:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=83bef141ee84036914ad29be97d7eb981538d0e8'/>
<id>urn:sha1:83bef141ee84036914ad29be97d7eb981538d0e8</id>
<content type='text'>
These bits are #defined at a fixed location. In order to support future
hardware that has chosen to move these bits around move the bits into a
member of the struct ftgmac100.

Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>drievrs/net/ftgmac100: Separate rx page storage from rxdesc</title>
<updated>2016-07-12T09:58:01+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2016-06-03T01:41:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=c0cbc1776dd474717aa2ff786a01a6c1b9631bb3'/>
<id>urn:sha1:c0cbc1776dd474717aa2ff786a01a6c1b9631bb3</id>
<content type='text'>
The ftgmac100 hardware revision in e.g. the Aspeed AST2500 no longer
reserves all bits in RXDES#2 but instead uses the bottom 16 bits to
store MAC frame metadata. Avoid corruption by shifting struct page
pointers out to their own member in struct ftgmac100.

Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net/ethernet/ftgmac100: Warn when nc-si enabled</title>
<updated>2016-07-12T09:57:50+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2016-06-15T01:13:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cdff4c2e2dfbda7b425c9ad148e0824824ae71b1'/>
<id>urn:sha1:cdff4c2e2dfbda7b425c9ad148e0824824ae71b1</id>
<content type='text'>
When a driver indicates it wants to use nc-si in the device tree but the
kerenl does not have it enabled the driver currently silently fails.

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net/ethernet/faraday: Forward port ftgmac100 NC-SI</title>
<updated>2016-06-03T20:51:49+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2016-05-21T15:17:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=1223d9745ac5c3a55a4c68d01514f94282a8402e'/>
<id>urn:sha1:1223d9745ac5c3a55a4c68d01514f94282a8402e</id>
<content type='text'>
This reflects changes made in order to build with 4.7.

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net/farady: Keep MAC always active for NCSI packets</title>
<updated>2016-06-03T20:51:49+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2016-05-09T01:47:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=04a12038baaf3d7de67c2886f60f61fea0004865'/>
<id>urn:sha1:04a12038baaf3d7de67c2886f60f61fea0004865</id>
<content type='text'>
The status of MAC and NCSI interface are sychronized. When NCSI
interface is down, the MAC is brought down. It means the NCSI
packets (especially AEN packets) cannot be received by the MAC's
driver even they're transmitted by far end. It causes one issue:
the ethernet cable is unplugged initially and system boots up
with down NCSI interface. The MAC stops receiving any ingress
traffic including NCSI packets. At later point, one NCSI (AEN)
packet is sent from far end when the ethernet cable is plugged.
We're going to miss the AEN on local end and the interface has
to be down for ever.

This keeps the receive/transmit buffer, IRQ and NAPI are always
enabled so that we won't miss any NCSI packets even the interrupt
is currently in link down state.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net/ncsi: Remove ncsi_stop_dev()</title>
<updated>2016-06-03T20:51:47+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2016-05-09T01:47:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=0198bab47b28e0f4e5d20be4b024a24083bf8cd7'/>
<id>urn:sha1:0198bab47b28e0f4e5d20be4b024a24083bf8cd7</id>
<content type='text'>
This drops API ncsi_stop_dev() as it does nothing.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net/faraday: Enable NCSI interface</title>
<updated>2016-06-03T20:51:46+00:00</updated>
<author>
<name>Gavin Shan</name>
<email>gwshan@linux.vnet.ibm.com</email>
</author>
<published>2015-04-14T08:39:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=cf9a5edbe8a84284286c4d21354c95953b4ba22e'/>
<id>urn:sha1:cf9a5edbe8a84284286c4d21354c95953b4ba22e</id>
<content type='text'>
The NIC has the possibility to connect to NCSI package and channel.
This supports NCSI enabled interface. When the network device is
registered, the accompanying NCSI device is registered. When the
interface is to be brought up, the NCSI device is started to probe
NCSI topology and choose one active channel automatically. On the
other handle, when the interface is to be brought down, the interface
will be shuted down when the NCSI device is teared down.

IP/UDP/TCP offload checksum is enabled according to information passed
on from bootloader through device-tree. The offload doesn't work
properly when the interface is in NCSI mode.

Signed-off-by: Gavin Shan &lt;gwshan@linux.vnet.ibm.com&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>net: ethernet: faraday: Use phy_find_first() instead of open coding it</title>
<updated>2016-01-11T03:05:30+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2016-01-10T20:04:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=e574f39816f0227e3f43806952c8bc551d61770a'/>
<id>urn:sha1:e574f39816f0227e3f43806952c8bc551d61770a</id>
<content type='text'>
Use phy_find_first() to find the first phy device instead of
open coding it.

Cc: Andrew Lunn &lt;andrew@lunn.ch&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Acked-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>phy: Add API for {un}registering an mdio device to a bus.</title>
<updated>2016-01-07T19:31:26+00:00</updated>
<author>
<name>Andrew Lunn</name>
<email>andrew@lunn.ch</email>
</author>
<published>2016-01-06T19:11:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=7f854420fbfe9d49afe2ffb1df052cfe8e215541'/>
<id>urn:sha1:7f854420fbfe9d49afe2ffb1df052cfe8e215541</id>
<content type='text'>
Rather than have drivers directly manipulate the mii_bus structure,
provide and API for registering and unregistering devices on an MDIO
bus, and performing lookups.

Signed-off-by: Andrew Lunn &lt;andrew@lunn.ch&gt;
Reviewed-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
