<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/forcedeth.c, branch linux-2.6.12.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.12.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.12.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2005-05-15T22:10:01Z</updated>
<entry>
<title>[PATCH] forcedeth: Update error handling</title>
<updated>2005-05-15T22:10:01Z</updated>
<author>
<name>Manfred Spraul</name>
</author>
<published>2005-04-19T19:17:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=22c6d143f33f10721216a8cfa3a83f7edfc2bd4e'/>
<id>urn:sha1:22c6d143f33f10721216a8cfa3a83f7edfc2bd4e</id>
<content type='text'>
Ayaz wrote an update to the error handling for forcedeth (which I
modified heavily, thus all bugs are mine):
The ERROR4 bit is not a fatal error, it just indicates a mismatch
between the actual packet len and the len according to the 802.3 header.
The patch adds proper handling.
The patch also removes the code that drops all packets with RX_ERROR &amp;
(!RX_FRAMINGERR): ERROR4 errors are also not fatal.
</content>
</entry>
<entry>
<title>[PATCH] forcedeth: netpoll support</title>
<updated>2005-05-12T23:42:06Z</updated>
<author>
<name>Michal Schmidt</name>
</author>
<published>2005-05-12T23:42:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2918c35d311263bc313b3da272783860ce573189'/>
<id>urn:sha1:2918c35d311263bc313b3da272783860ce573189</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!
</content>
</entry>
</feed>
