renesas/drm.git - libdrm, cloned from git://anongit.freedesktop.org/mesa/drm

Age	Commit message (Expand)	Author
2009-11-20	Merge remote branch 'origin/master' into libdrm	Kristian Høgsberg
2009-11-17	Move libdrm/ up one level	Kristian Høgsberg

\begin{titlepage} \thispagestyle{fancy} \begin{tabular*}{\textwidth}{@{\extracolsep{\fill}}lr} \includegraphics[height=0.55in]{images/oasis.png}\\ \hline \end{tabular*} \oasistitle{Virtual I/O Device (VIRTIO) Version 1.0} \oasisstagelabel{Working Draft} \vspace{0.05in}\vfill \oasisstagelabel{\virtioworkingdraftdate} \vfill \begin{oasistitlesection}{Technical Committee} \href{https://www.oasis-open.org/committees/virtio/}{OASIS Virtual I/O Device (VIRTIO) TC} \end{oasistitlesection} \begin{oasistitlesection}{Chair} Rusty Russell (\href{mailto:rusty@au.ibm.com}{rusty@au.ibm.com}), \href{http://www.ibm.com/}{IBM}\newline \end{oasistitlesection} \begin{oasistitlesection}{Editors} Michael S. Tsirkin (\href{mailto:mst@redhat.com}{mst@redhat.com}), \href{http://redhat.com/}{Red Hat}\newline Cornelia Huck (\href{mailto:cornelia.huck@de.ibm.com}{cornelia.huck@de.ibm.com}), \href{http://www.ibm.com/}{IBM}\newline Pawel Moll (\href{mailto:pawel.moll@arm.com}{pawel.moll@arm.com}), \href{https://arm.com/}{ARM Limited} \end{oasistitlesection} \begin{oasistitlesection}{Additional artifacts} This prose specification is one component of a Work Product which also includes: \begin{itemize*} \item XML schemas (list)\newline \item TeX source files for this prose document:\newline \url{http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/tex/} \end{itemize*} \end{oasistitlesection} \vspace{-0.2in} \begin{oasistitlesection}{Related work} This specification replaces or supersedes: \begin{itemize*} \item Virtio PCI Card Specification Version 0.9.5:\newline \url{http://ozlabs.org/~rusty/virtio-spec/virtio-0.9.5.pdf} \end{itemize*} This specification is related to: \begin{itemize*} \item Related speifications (list) \end{itemize*} \end{oasistitlesection} \vspace{-0.2in} \begin{oasistitlesection}{Declared XML namespaces} \vspace{-0.1in} \begin{itemize*} \item namespaces which are declared, not just referenced or used (list) \end{itemize*} \end{oasistitlesection} \begin{oasistitlesection}{Abstract} Summary of the technical purpose of the specification \end{oasistitlesection} \begin{oasistitlesection}{Status} This \href{https://www.oasis-open.org/committees/process.php#dWorkingDraft}{Working Draft} (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or \href{https://www.oasis-open.org/committees/process.php#committeeDraft}{approved} as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document \href{https://www.oasis-open.org/committees/process.php#standApprovProcess}{Approval Process} begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft. Technical Committee members should send comments on this specification to the Technical Committee’s \href{https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback}{mailing list}. Others should send comments to the Technical Committee by sending mail to the virtio-comment public mailing list or using the "\href{https://www.oasis-open.org/committees/comments/form.php?wg_abbrev=virtio}{Send A Comment}" button on the Technical Committee’s web page at \url{https://www.oasis-open.org/committees/virtio/}. \end{oasistitlesection} \oasisspecificationuris{Initial URI pattern}\newline \url{http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.odt}\newline (Managed by OASIS TC Administration; please don’t modify.)\newline \url{http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.pdf} (Authoritative)\newline \url{http://docs.oasis-open.org/virtio/virtio/v1.0/csd01/virtio-v1.0-csd01.html} \vfill\newpage \vfill\newpage \oasisnoticelabel{Notices} Copyright © OASIS Open 2013. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full \href{https://www.oasis-open.org/policies-guidelines/ipr}{Policy} may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. The name "OASIS" is a trademark of \href{https://www.oasis-open.org/}{OASIS}, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see \url{https://www.oasis-open.org/policies-guidelines/trademark} for above guidance. \\\\ \end{titlepage}