Loading Documentation/00-INDEX +2 −0 Original line number Diff line number Diff line Loading @@ -104,6 +104,8 @@ cpuidle/ - info on CPU_IDLE, CPU idle state management subsystem. cputopology.txt - documentation on how CPU topology info is exported via sysfs. crc32.txt - brief tutorial on CRC computation cris/ - directory with info about Linux on CRIS architecture. crypto/ Loading Documentation/ABI/testing/sysfs-bus-rpmsg 0 → 100644 +75 −0 Original line number Diff line number Diff line What: /sys/bus/rpmsg/devices/.../name Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels are identified with a (textual) name, which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in rpmsg.h). This sysfs entry contains the name of this channel. What: /sys/bus/rpmsg/devices/.../src Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels have a local ("source") rpmsg address, and remote ("destination") rpmsg address. When an entity starts listening on one end of a channel, it assigns it with a unique rpmsg address (a 32 bits integer). This way when inbound messages arrive to this address, the rpmsg core dispatches them to the listening entity (a kernel driver). This sysfs entry contains the src (local) rpmsg address of this channel. If it contains 0xffffffff, then an address wasn't assigned (can happen if no driver exists for this channel). What: /sys/bus/rpmsg/devices/.../dst Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels have a local ("source") rpmsg address, and remote ("destination") rpmsg address. When an entity starts listening on one end of a channel, it assigns it with a unique rpmsg address (a 32 bits integer). This way when inbound messages arrive to this address, the rpmsg core dispatches them to the listening entity. This sysfs entry contains the dst (remote) rpmsg address of this channel. If it contains 0xffffffff, then an address wasn't assigned (can happen if the kernel driver that is attached to this channel is exposing a service to the remote processor. This make it a local rpmsg server, and it is listening for inbound messages that may be sent from any remote rpmsg client; it is not bound to a single remote entity). What: /sys/bus/rpmsg/devices/.../announce Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels are identified by a textual name (see /sys/bus/rpmsg/devices/.../name above) and have a local ("source") rpmsg address, and remote ("destination") rpmsg address. A channel is first created when an entity, whether local or remote, starts listening on it for messages (and is thus called an rpmsg server). When that happens, a "name service" announcement is sent to the other processor, in order to let it know about the creation of the channel (this way remote clients know they can start sending messages). This sysfs entry tells us whether the channel is a local server channel that is announced (values are either true or false). Documentation/DocBook/kgdb.tmpl +17 −0 Original line number Diff line number Diff line Loading @@ -361,6 +361,23 @@ <para>It is possible to use this option with kgdboc on a tty that is not a system console. </para> </para> </sect1> <sect1 id="kgdbreboot"> <title>Run time parameter: kgdbreboot</title> <para> The kgdbreboot feature allows you to change how the debugger deals with the reboot notification. You have 3 choices for the behavior. The default behavior is always set to 0.</para> <orderedlist> <listitem><para>echo -1 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Ignore the reboot notification entirely.</para> </listitem> <listitem><para>echo 0 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Send the detach message to any attached debugger client.</para> </listitem> <listitem><para>echo 1 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Enter the debugger on reboot notify.</para> </listitem> </orderedlist> </sect1> </chapter> <chapter id="usingKDB"> Loading Documentation/DocBook/media/v4l/biblio.xml +20 −0 Original line number Diff line number Diff line Loading @@ -128,6 +128,26 @@ url="http://www.ijg.org">http://www.ijg.org</ulink>)</corpauthor> <subtitle>Version 1.02</subtitle> </biblioentry> <biblioentry id="itu-t81"> <abbrev>ITU-T.81</abbrev> <authorgroup> <corpauthor>International Telecommunication Union (<ulink url="http://www.itu.int">http://www.itu.int</ulink>)</corpauthor> </authorgroup> <title>ITU-T Recommendation T.81 "Information Technology — Digital Compression and Coding of Continous-Tone Still Images — Requirements and Guidelines"</title> </biblioentry> <biblioentry id="w3c-jpeg-jfif"> <abbrev>W3C JPEG JFIF</abbrev> <authorgroup> <corpauthor>The World Wide Web Consortium (<ulink url="http://www.w3.org/Graphics/JPEG">http://www.w3.org</ulink>)</corpauthor> </authorgroup> <title>JPEG JFIF</title> </biblioentry> <biblioentry id="smpte12m"> <abbrev>SMPTE 12M</abbrev> <authorgroup> Loading Documentation/DocBook/media/v4l/compat.xml +14 −0 Original line number Diff line number Diff line Loading @@ -2393,6 +2393,20 @@ details.</para> to the <link linkend="control">User controls class</link>. </para> </listitem> <listitem> <para>Added the device_caps field to struct v4l2_capabilities and added the new V4L2_CAP_DEVICE_CAPS capability.</para> </listitem> </orderedlist> </section> <section> <title>V4L2 in Linux 3.4</title> <orderedlist> <listitem> <para>Added <link linkend="jpeg-controls">JPEG compression control class</link>.</para> </listitem> </orderedlist> </section> Loading Loading
Documentation/00-INDEX +2 −0 Original line number Diff line number Diff line Loading @@ -104,6 +104,8 @@ cpuidle/ - info on CPU_IDLE, CPU idle state management subsystem. cputopology.txt - documentation on how CPU topology info is exported via sysfs. crc32.txt - brief tutorial on CRC computation cris/ - directory with info about Linux on CRIS architecture. crypto/ Loading
Documentation/ABI/testing/sysfs-bus-rpmsg 0 → 100644 +75 −0 Original line number Diff line number Diff line What: /sys/bus/rpmsg/devices/.../name Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels are identified with a (textual) name, which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in rpmsg.h). This sysfs entry contains the name of this channel. What: /sys/bus/rpmsg/devices/.../src Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels have a local ("source") rpmsg address, and remote ("destination") rpmsg address. When an entity starts listening on one end of a channel, it assigns it with a unique rpmsg address (a 32 bits integer). This way when inbound messages arrive to this address, the rpmsg core dispatches them to the listening entity (a kernel driver). This sysfs entry contains the src (local) rpmsg address of this channel. If it contains 0xffffffff, then an address wasn't assigned (can happen if no driver exists for this channel). What: /sys/bus/rpmsg/devices/.../dst Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels have a local ("source") rpmsg address, and remote ("destination") rpmsg address. When an entity starts listening on one end of a channel, it assigns it with a unique rpmsg address (a 32 bits integer). This way when inbound messages arrive to this address, the rpmsg core dispatches them to the listening entity. This sysfs entry contains the dst (remote) rpmsg address of this channel. If it contains 0xffffffff, then an address wasn't assigned (can happen if the kernel driver that is attached to this channel is exposing a service to the remote processor. This make it a local rpmsg server, and it is listening for inbound messages that may be sent from any remote rpmsg client; it is not bound to a single remote entity). What: /sys/bus/rpmsg/devices/.../announce Date: June 2011 KernelVersion: 3.3 Contact: Ohad Ben-Cohen <ohad@wizery.com> Description: Every rpmsg device is a communication channel with a remote processor. Channels are identified by a textual name (see /sys/bus/rpmsg/devices/.../name above) and have a local ("source") rpmsg address, and remote ("destination") rpmsg address. A channel is first created when an entity, whether local or remote, starts listening on it for messages (and is thus called an rpmsg server). When that happens, a "name service" announcement is sent to the other processor, in order to let it know about the creation of the channel (this way remote clients know they can start sending messages). This sysfs entry tells us whether the channel is a local server channel that is announced (values are either true or false).
Documentation/DocBook/kgdb.tmpl +17 −0 Original line number Diff line number Diff line Loading @@ -361,6 +361,23 @@ <para>It is possible to use this option with kgdboc on a tty that is not a system console. </para> </para> </sect1> <sect1 id="kgdbreboot"> <title>Run time parameter: kgdbreboot</title> <para> The kgdbreboot feature allows you to change how the debugger deals with the reboot notification. You have 3 choices for the behavior. The default behavior is always set to 0.</para> <orderedlist> <listitem><para>echo -1 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Ignore the reboot notification entirely.</para> </listitem> <listitem><para>echo 0 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Send the detach message to any attached debugger client.</para> </listitem> <listitem><para>echo 1 > /sys/module/debug_core/parameters/kgdbreboot</para> <para>Enter the debugger on reboot notify.</para> </listitem> </orderedlist> </sect1> </chapter> <chapter id="usingKDB"> Loading
Documentation/DocBook/media/v4l/biblio.xml +20 −0 Original line number Diff line number Diff line Loading @@ -128,6 +128,26 @@ url="http://www.ijg.org">http://www.ijg.org</ulink>)</corpauthor> <subtitle>Version 1.02</subtitle> </biblioentry> <biblioentry id="itu-t81"> <abbrev>ITU-T.81</abbrev> <authorgroup> <corpauthor>International Telecommunication Union (<ulink url="http://www.itu.int">http://www.itu.int</ulink>)</corpauthor> </authorgroup> <title>ITU-T Recommendation T.81 "Information Technology — Digital Compression and Coding of Continous-Tone Still Images — Requirements and Guidelines"</title> </biblioentry> <biblioentry id="w3c-jpeg-jfif"> <abbrev>W3C JPEG JFIF</abbrev> <authorgroup> <corpauthor>The World Wide Web Consortium (<ulink url="http://www.w3.org/Graphics/JPEG">http://www.w3.org</ulink>)</corpauthor> </authorgroup> <title>JPEG JFIF</title> </biblioentry> <biblioentry id="smpte12m"> <abbrev>SMPTE 12M</abbrev> <authorgroup> Loading
Documentation/DocBook/media/v4l/compat.xml +14 −0 Original line number Diff line number Diff line Loading @@ -2393,6 +2393,20 @@ details.</para> to the <link linkend="control">User controls class</link>. </para> </listitem> <listitem> <para>Added the device_caps field to struct v4l2_capabilities and added the new V4L2_CAP_DEVICE_CAPS capability.</para> </listitem> </orderedlist> </section> <section> <title>V4L2 in Linux 3.4</title> <orderedlist> <listitem> <para>Added <link linkend="jpeg-controls">JPEG compression control class</link>.</para> </listitem> </orderedlist> </section> Loading