<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/base/firmware_class.c, branch linux-2.6.12.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.12.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-2.6.12.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2005-04-19T04:57:31Z</updated>
<entry>
<title>[PATCH] add TIMEOUT to firmware_class hotplug event</title>
<updated>2005-04-19T04:57:31Z</updated>
<author>
<name>kay.sievers@vrfy.org</name>
<email>kay.sievers@vrfy.org</email>
</author>
<published>2005-04-19T04:57:31Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6897089c5f7989603ccb9c696050470ba1dbd262'/>
<id>urn:sha1:6897089c5f7989603ccb9c696050470ba1dbd262</id>
<content type='text'>
On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote:
&gt; The current implementation of the firmware class breaks a fundamental
&gt; assumption in udevd: that the physical device can be initialised fully
&gt; prior to executing the next event for that device.

Here we add a TIMEOUT value to the hotplug environment of the firmware
requesting event. I will adapt udevd not to wait for anything else, if
it finds a TIMEOUT key.

Signed-off-by: Kay Sievers &lt;kay.sievers@vrfy.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@ppc970.osdl.org</email>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/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>
