Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[xsrc/trunk]: xsrc/external/mit/xf86-video-vboxvideo/dist initial import of x...
details: https://anonhg.NetBSD.org/xsrc/rev/66dfa4b49e27
branches: trunk
changeset: 10079:66dfa4b49e27
user: mrg <mrg%NetBSD.org@localhost>
date: Wed Jan 09 23:50:29 2019 +0000
description:
initial import of xf86-video-vboxvideo-1.0.0
diffstat:
external/mit/xf86-video-vboxvideo/dist/COPYING | 26 +
external/mit/xf86-video-vboxvideo/dist/ChangeLog | 11 +
external/mit/xf86-video-vboxvideo/dist/INSTALL | 370 +
external/mit/xf86-video-vboxvideo/dist/Makefile.am | 33 +
external/mit/xf86-video-vboxvideo/dist/Makefile.in | 872 +
external/mit/xf86-video-vboxvideo/dist/README | 20 +
external/mit/xf86-video-vboxvideo/dist/aclocal.m4 | 12431 +++++
external/mit/xf86-video-vboxvideo/dist/compile | 347 +
external/mit/xf86-video-vboxvideo/dist/config.guess | 1462 +
external/mit/xf86-video-vboxvideo/dist/config.h.in | 78 +
external/mit/xf86-video-vboxvideo/dist/config.sub | 1825 +
external/mit/xf86-video-vboxvideo/dist/configure | 21065 ++++++++++
external/mit/xf86-video-vboxvideo/dist/configure.ac | 97 +
external/mit/xf86-video-vboxvideo/dist/depcomp | 791 +
external/mit/xf86-video-vboxvideo/dist/install-sh | 508 +
external/mit/xf86-video-vboxvideo/dist/ltmain.sh | 11156 +++++
external/mit/xf86-video-vboxvideo/dist/man/Makefile.am | 41 +
external/mit/xf86-video-vboxvideo/dist/man/Makefile.in | 553 +
external/mit/xf86-video-vboxvideo/dist/man/vboxvideo.man | 27 +
external/mit/xf86-video-vboxvideo/dist/missing | 215 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMI.h | 258 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIBase.c | 293 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIBase.h | 54 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIBuffers.c | 118 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIChSetup.h | 79 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIChannels.h | 64 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMICommon.c | 449 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIContext.h | 104 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIDefs.h | 118 +
external/mit/xf86-video-vboxvideo/dist/src/HGSMIMemAlloc.h | 56 +
external/mit/xf86-video-vboxvideo/dist/src/Makefile.am | 68 +
external/mit/xf86-video-vboxvideo/dist/src/Makefile.in | 751 +
external/mit/xf86-video-vboxvideo/dist/src/Modesetting.c | 386 +
external/mit/xf86-video-vboxvideo/dist/src/VBVABase.c | 390 +
external/mit/xf86-video-vboxvideo/dist/src/VBoxVideo.h | 2106 +
external/mit/xf86-video-vboxvideo/dist/src/VBoxVideoErr.h | 64 +
external/mit/xf86-video-vboxvideo/dist/src/VBoxVideoGuest.h | 175 +
external/mit/xf86-video-vboxvideo/dist/src/VBoxVideoIPRT.h | 221 +
external/mit/xf86-video-vboxvideo/dist/src/VBoxVideoVBE.h | 81 +
external/mit/xf86-video-vboxvideo/dist/src/edid.c | 166 +
external/mit/xf86-video-vboxvideo/dist/src/getmode.c | 318 +
external/mit/xf86-video-vboxvideo/dist/src/helpers.c | 81 +
external/mit/xf86-video-vboxvideo/dist/src/hgsmimemalloc.c | 106 +
external/mit/xf86-video-vboxvideo/dist/src/pointer.c | 493 +
external/mit/xf86-video-vboxvideo/dist/src/setmode.c | 132 +
external/mit/xf86-video-vboxvideo/dist/src/vboxvideo.c | 1492 +
external/mit/xf86-video-vboxvideo/dist/src/vboxvideo.h | 240 +
external/mit/xf86-video-vboxvideo/dist/src/vbva.c | 252 +
external/mit/xf86-video-vboxvideo/dist/src/version-generated.h | 14 +
49 files changed, 61057 insertions(+), 0 deletions(-)
diffs (truncated from 61253 to 300 lines):
diff -r ef09ea508fe2 -r 66dfa4b49e27 external/mit/xf86-video-vboxvideo/dist/COPYING
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/external/mit/xf86-video-vboxvideo/dist/COPYING Wed Jan 09 23:50:29 2019 +0000
@@ -0,0 +1,26 @@
+Copyright (c) 2000 by Conectiva S.A. (http://www.conectiva.com)
+Copyright 2008 Red Hat, Inc.
+Copyright (C) 2005-2017 Oracle Corporation
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+CONECTIVA LINUX BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
+OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+Except as contained in this notice, the name of Conectiva Linux shall
+not be used in advertising or otherwise to promote the sale, use or other
+dealings in this Software without prior written authorization from
+Conectiva Linux.
diff -r ef09ea508fe2 -r 66dfa4b49e27 external/mit/xf86-video-vboxvideo/dist/ChangeLog
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/external/mit/xf86-video-vboxvideo/dist/ChangeLog Wed Jan 09 23:50:29 2019 +0000
@@ -0,0 +1,11 @@
+commit 948bc1ae047668df040d62a19cae6d7a49e452fd
+Author: Michael Thayer <michael.thayer%oracle.com@localhost>
+Date: Tue Nov 28 11:58:30 2017 +0100
+
+ vboxvideo 1.0.0
+
+commit ab07f97612d045d8c0a376174b39a294d028fef2
+Author: Michael Thayer <michael.thayer%oracle.com@localhost>
+Date: Sat Oct 14 10:23:47 2017 +0200
+
+ Initial commit.
diff -r ef09ea508fe2 -r 66dfa4b49e27 external/mit/xf86-video-vboxvideo/dist/INSTALL
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/external/mit/xf86-video-vboxvideo/dist/INSTALL Wed Jan 09 23:50:29 2019 +0000
@@ -0,0 +1,370 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2011 Free Software Foundation,
+Inc.
+
+ Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+ Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package. Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below. The lack of an optional feature in a given package is not
+necessarily a bug. More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+ The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system.
+
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package, generally using the just-built uninstalled binaries.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation. When installing into a prefix owned by root, it is
+ recommended that the package be configured and built as a regular
+ user, and only the `make install' phase executed with root
+ privileges.
+
+ 5. Optionally, type `make installcheck' to repeat any self-tests, but
+ this time using the binaries in their final installed location.
+ This target does not install anything. Running this target as a
+ regular user, particularly if the prior `make install' required
+ root privileges, verifies that the installation completed
+ correctly.
+
+ 6. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+ 7. Often, you can also type `make uninstall' to remove the installed
+ files again. In practice, not all packages have tested that
+ uninstallation works correctly, even though it is required by the
+ GNU Coding Standards.
+
+ 8. Some packages, particularly those that use Automake, provide `make
+ distcheck', which can by used by developers to test that all other
+ targets like `make install' and `make uninstall' work correctly.
+ This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you can use GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'. This
+is known as a "VPATH" build.
+
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor. Like
+this:
+
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
+
+ This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+ By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them. In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+ The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+ The first method involves providing an override variable for each
+affected directory. For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'. Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated. The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+ The second method involves providing the `DESTDIR' variable. For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names. The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters. On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+ Some packages offer the ability to configure how verbose the
+execution of `make' will be. For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+ HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved. Use GNU `make'
+instead.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+a workaround. If GNU CC is not installed, it is therefore recommended
+to try
+
+ ./configure CC="cc"
+
+and if that doesn't work, try
+
+ ./configure CC="cc -nodtk"
+
+ On Solaris, don't put `/usr/ucb' early in your `PATH'. This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+ On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'. It is recommended to use the following options:
Home |
Main Index |
Thread Index |
Old Index