<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-toradex.git/drivers/net/igb, branch tegra</title>
<subtitle>Linux kernel for Apalis and Colibri modules</subtitle>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/'/>
<entry>
<title>apalis_t30: igb: no nvm and Ethernet MAC address handling</title>
<updated>2015-04-02T11:55:25+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2015-04-02T11:55:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=c4c3c7449bdb15c53bfebb0a29c73b24ea810d23'/>
<id>c4c3c7449bdb15c53bfebb0a29c73b24ea810d23</id>
<content type='text'>
Springville/i211 with a blank Flash/iNVM use different PCI IDs. Extend
the driver to load despite i210/i211 data sheets claiming tools only,
not for driver.

Only warn rather than fail on NVM validation failures on Apalis T30.

Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).

Use the Toradex OUI as default MAC address if no valid one is
encountered.

Tested on samples of Apalis T30 2GB V1.0B, V1.0C, V1.1A, Apalis T30 1GB
V1.0A, V1.1A and Apalis T30 1GB IT V1.1A both with blank NVMs as well
as iNVMs programmed with Intel's defaults.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Springville/i211 with a blank Flash/iNVM use different PCI IDs. Extend
the driver to load despite i210/i211 data sheets claiming tools only,
not for driver.

Only warn rather than fail on NVM validation failures on Apalis T30.

Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).

Use the Toradex OUI as default MAC address if no valid one is
encountered.

Tested on samples of Apalis T30 2GB V1.0B, V1.0C, V1.1A, Apalis T30 1GB
V1.0A, V1.1A and Apalis T30 1GB IT V1.1A both with blank NVMs as well
as iNVMs programmed with Intel's defaults.
</pre>
</div>
</content>
</entry>
<entry>
<title>igb: integrate tools only device support</title>
<updated>2015-04-02T10:44:26+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2015-04-02T10:44:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=2c7123458270c9b3ec9b5ed668f9d55a7f8dbad9'/>
<id>2c7123458270c9b3ec9b5ed668f9d55a7f8dbad9</id>
<content type='text'>
Springville/i211 with a blank Flash/iNVM use a different PCI ID (tools
only, not for driver) than properly programmed ones.

While at it also fix ethtool time stamping as well as RX flow hash
indirection functionality.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Springville/i211 with a blank Flash/iNVM use a different PCI ID (tools
only, not for driver) than properly programmed ones.

While at it also fix ethtool time stamping as well as RX flow hash
indirection functionality.
</pre>
</div>
</content>
</entry>
<entry>
<title>igb: integrate igb driver 5.2.17</title>
<updated>2015-04-02T08:55:04+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2015-04-02T08:55:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ec09535b190fe3e1ecb43c68610e543d46e7ac92'/>
<id>ec09535b190fe3e1ecb43c68610e543d46e7ac92</id>
<content type='text'>
Integrate latest igb driver version 5.2.17
(igb-5.2.17.tar.gz from e1000.sf.net).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Integrate latest igb driver version 5.2.17
(igb-5.2.17.tar.gz from e1000.sf.net).
</pre>
</div>
</content>
</entry>
<entry>
<title>apalis_t30: ieee 1588 ptp support</title>
<updated>2014-03-31T15:57:51+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2014-03-31T15:57:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=50d2dbba6198a9e195bad36990c259cfd911d53c'/>
<id>50d2dbba6198a9e195bad36990c259cfd911d53c</id>
<content type='text'>
Enable IEEE 1588 precision time protocol (PTP) support.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enable IEEE 1588 precision time protocol (PTP) support.
</pre>
</div>
</content>
</entry>
<entry>
<title>apalis_t30: igb: no nvm and Ethernet MAC address handling</title>
<updated>2014-03-31T15:54:25+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2014-03-31T15:54:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=f032a4e356a04f3ab3d14805b34d48d64ce2a8ca'/>
<id>f032a4e356a04f3ab3d14805b34d48d64ce2a8ca</id>
<content type='text'>
Springville/i211 with a blank Flash/iNVM use different PCI IDs. Extend
the driver to load despite i210/i211 data sheets claiming tools only,
not for driver.

Only warn rather than fail on NVM validation failures on Apalis T30.

Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).

Use the Toradex OUI as default MAC address if no valid one is
encountered.

Tested on samples of Apalis T30 2GB V1.0B, V1.0C and Apalis T30 1GB
V1.0A both with blank NVMs as well as iNVMs programmed with Intel's
defaults.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Springville/i211 with a blank Flash/iNVM use different PCI IDs. Extend
the driver to load despite i210/i211 data sheets claiming tools only,
not for driver.

Only warn rather than fail on NVM validation failures on Apalis T30.

Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).

Use the Toradex OUI as default MAC address if no valid one is
encountered.

Tested on samples of Apalis T30 2GB V1.0B, V1.0C and Apalis T30 1GB
V1.0A both with blank NVMs as well as iNVMs programmed with Intel's
defaults.
</pre>
</div>
</content>
</entry>
<entry>
<title>igb: integrate tools only device support</title>
<updated>2014-03-31T15:52:49+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2014-03-31T15:52:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=3560d23f14c26b65f89a9d6b674fc0f3196fa0f1'/>
<id>3560d23f14c26b65f89a9d6b674fc0f3196fa0f1</id>
<content type='text'>
Springville/i211 with a blank Flash/iNVM use a different PCI ID (tools
only, not for driver) than properly programmed ones.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Springville/i211 with a blank Flash/iNVM use a different PCI ID (tools
only, not for driver) than properly programmed ones.
</pre>
</div>
</content>
</entry>
<entry>
<title>igb: integrate igb driver 5.1.2</title>
<updated>2014-03-31T15:50:10+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2014-03-31T15:50:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=1a0ab01fdd5104255dcfdeb0527e7001d28e3345'/>
<id>1a0ab01fdd5104255dcfdeb0527e7001d28e3345</id>
<content type='text'>
Integrate latest igb driver version 5.1.2
(igb-5.1.2.tar.gz from e1000.sf.net).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Integrate latest igb driver version 5.1.2
(igb-5.1.2.tar.gz from e1000.sf.net).
</pre>
</div>
</content>
</entry>
<entry>
<title>apalis_t30: igb: add un-programmed i211 support</title>
<updated>2013-08-07T11:58:42+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2013-08-07T11:58:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=4c37205178482335cd6a68caea2ba46c02522ea2'/>
<id>4c37205178482335cd6a68caea2ba46c02522ea2</id>
<content type='text'>
I211 with a blank iNVM uses a different PCI ID. Hack the driver to load
despite i211 data sheet claiming tools only, not for driver.

Please note that the existing driver hacks concerning NVM validation
skipping and Ethernet MAC address assignment equally apply.

Tested on initial samples of Apalis T30 1GB V1.0A.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I211 with a blank iNVM uses a different PCI ID. Hack the driver to load
despite i211 data sheet claiming tools only, not for driver.

Please note that the existing driver hacks concerning NVM validation
skipping and Ethernet MAC address assignment equally apply.

Tested on initial samples of Apalis T30 1GB V1.0A.
</pre>
</div>
</content>
</entry>
<entry>
<title>net: igb: apalis_t30: revise Ethernet MAC address assignment</title>
<updated>2013-05-09T01:29:25+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2013-05-09T01:29:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=ddd4c65b5b6ef4bc1f4f8476fccc60d410bfbe3a'/>
<id>ddd4c65b5b6ef4bc1f4f8476fccc60d410bfbe3a</id>
<content type='text'>
Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Revise Ethernet MAC address assignment: should now handle up to two
instances of custom user MACs (2nd one with a 0x100000 offset). This
way customer does not have to worry about NVM on a secondary Ethernet
on the carrier board and still gets a valid official MAC address from
us (e.g. analogous to how we did it on our Protea carrier board).
</pre>
</div>
</content>
</entry>
<entry>
<title>igb: Add Support for new i210/i211 devices.</title>
<updated>2013-01-24T14:30:47+00:00</updated>
<author>
<name>Marcel Ziswiler</name>
<email>marcel.ziswiler@toradex.com</email>
</author>
<published>2013-01-24T14:30:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.toradex.cn/cgit/linux-toradex.git/commit/?id=dd13c4e19f12fbef1f131f29df04ed83be51afaa'/>
<id>dd13c4e19f12fbef1f131f29df04ed83be51afaa</id>
<content type='text'>
The following commit actually missed adding the new files:

7925180aee227f3de7af4a8cbad1c4b203a9132e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The following commit actually missed adding the new files:

7925180aee227f3de7af4a8cbad1c4b203a9132e
</pre>
</div>
</content>
</entry>
</feed>
