<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/include/sound/asoundef.h, branch linux-5.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2012-04-18T06:00:36Z</updated>
<entry>
<title>ALSA: Add definitions for CEA-861 Audio InfoFrames</title>
<updated>2012-04-18T06:00:36Z</updated>
<author>
<name>Ricardo Neri</name>
<email>ricardo.neri@ti.com</email>
</author>
<published>2012-04-18T00:46:11Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7ba1c40b536e1c0df18d44af67ffa5a87a99f91c'/>
<id>urn:sha1:7ba1c40b536e1c0df18d44af67ffa5a87a99f91c</id>
<content type='text'>
Along with the IEC-60958 channel status word, CEA-861 Audio InfoFrames
are used in HDMI and DisplayPort to describe the parameters of the audio
stream. Hence, drivers for such devices may use these definitions to, for
instance, fill a CEA-861 data structure and pass it to a display driver
to configure an IP.

Signed-off-by: Ricardo Neri &lt;ricardo.neri@ti.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: IEC958 definition for consumer status channel update</title>
<updated>2008-08-01T11:13:13Z</updated>
<author>
<name>Pawel MOLL</name>
<email>pawel.moll@st.com</email>
</author>
<published>2008-08-01T10:23:44Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=687fbc3fece34e7e1c2ac529348ad897095a0bde'/>
<id>urn:sha1:687fbc3fece34e7e1c2ac529348ad897095a0bde</id>
<content type='text'>
Updated IEC958 consumer status channel definitions according
to the third edition of IEC60958-3 spec.

Signed-off-by: Pawel Moll &lt;pawel.moll@st.com&gt;
Signed-off-by: Jaroslav Kysela &lt;perex@perex.cz&gt;
</content>
</entry>
<entry>
<title>[ALSA] IEC958 definitions for consumer status channel, byte 4</title>
<updated>2008-04-24T10:00:19Z</updated>
<author>
<name>Pawel MOLL</name>
<email>pawel.moll@st.com</email>
</author>
<published>2008-02-29T11:41:31Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=fd6640fa2d8b5f5f471aad5abd8ce5d6995df563'/>
<id>urn:sha1:fd6640fa2d8b5f5f471aad5abd8ce5d6995df563</id>
<content type='text'>
Added definition for byte 4 of SPDIF channel status, according to
second edition of IEC 60958-3 (consumer) spec.

Signed-off-by: Pawel MOLL &lt;pawel.moll@st.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>[ALSA] Changed Jaroslav Kysela's e-mail from perex@suse.cz to perex@perex.cz</title>
<updated>2007-10-16T14:51:18Z</updated>
<author>
<name>Jaroslav Kysela</name>
<email>perex@perex.cz</email>
</author>
<published>2007-10-15T07:50:19Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c1017a4cdb68ae5368fbc9ee42c77f1f5dca8916'/>
<id>urn:sha1:c1017a4cdb68ae5368fbc9ee42c77f1f5dca8916</id>
<content type='text'>
Signed-off-by: Jaroslav Kysela &lt;perex@perex.cz&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>
