Changes between Version 48 and Version 49 of WikiStart

Timestamp:

Jul 28, 2010, 5:02:04 AM (14 years ago)

Author:

David Azarewicz

Comment:

--

WikiStart

@@ -4 +4 @@
 = Uniaud for OS/2 & eCS =
 
-This is the development home for uniaud, the Universal Audio Driver for eCS and OS/2.
+This is the development home for uniaud, the Universal Audio Driver for eCS and OS/2. The Uniaud
+project consists of 2 separate drivers, Uniaud16.sys and Uniaud32.sys.
+
+== Uniaud32 ==
+
+Uniaud32.sys is the actual audio driver that connects to the hardware and makes it work. It
+consists of a modified ALSA core and some OS/2 specific pieces which make it load and run on an OS/2
+system. Different major versions of Uniaud32 are based on different versions of ALSA. For example,
+Uniaud32 versions 1.9.x are based on ALSA 1.0.21, and Uniaud32 versions 2.1.x are based on ALSA 1.0.23.
+
+== Uniaud16 ==
+
+Uniaud16.sys is the interface between MMOS2 and Uniaud32.sys. Uniaud16 does not talk to the audio
+hardware. It is just an interface translator, buffer manager, and may do some resampling.  Uniaud16.sys
+has its own version number. Do not confuse Uniaud16's version number with Uniaud32's version number.
+
+= Download Binary Distributions =
+
 The "Retail Install Package" is used to install Uniaud on a system that doesn't already
 have Uniaud installed.  The "Retail and Debug Update" package has both the Retail build
@@ -11 +28 @@
 and uniaud32.sys over your existing files. It is not recommended to run the Debug version
 unless you are testing a specific problem and need to produce a detailed log.
-
-Downloads:
 
 The current GA release is Uniaud16 version 1.9.3 and Uniaud32 version 1.9.23 (based on ALSA 1.0.21):
@@ -70 +85 @@
 = Distributing builds =
 
-== Uniaud16 ==
+Public distribution packages always contain both Uniaud16.sys and Uniaud32.sys.
+See [ReleaseProcedures Release Package Procedures] for how we go about this.
 
-Public builds of uniaud16.sys are included with all uniaud packages. There is not usually be a reason to publicly release Uniaud16 by itself. See [ReleaseProcedures Release Package Procedures] for how we go about this.
+There is not usually be a reason to publicly release Uniaud16 or Uniaud32 by itself. 
 
-When distributing builds of Uniaud16 privately to a few people to test, a good practice, to avoid confusion with the public releases, is to change the "fixpak level" to the svn revision number, e.g. "!r380". If it does not match any revision number, perhaps because you are testing before committing, you may want to distinguish it with a word like "TESTCASE" or "CUSTOM". None of these labels for private builds should be committed to the svn repo. It is also helpful to set the HOSTNAME environment variable to a unique word that can trace the build back to you if your build system's hostname doesn't already.
+When distributing builds of Uniaud16 or Uniaud32 privately to a few people to test, a good practice, to avoid confusion with the public releases, is to change the "fixpak level" to the svn revision number, e.g. "!r380". If it does not match any revision number, perhaps because you are testing before committing, you may want to distinguish it with a word like "TESTCASE" or "CUSTOM". None of these labels for private builds should be committed to the svn repo. It is also helpful to set the HOSTNAME environment variable to a unique word that can trace the build back to you if your build system's hostname doesn't already.
 
-== Uniaud32 ==
-
-Trunk releases of Uniaud32 accompany Uniaud16 of the same version, so public releases follow the same [ReleaseProcedures Release Procedures].
-
-The same practices for private builds apply as well, except that Uniaud32 is GPL, so for license compliance any test builds that are distributed privately should not only specify the svn revision number, but also include a patch against that revision if anything differs. This is easily acquired with:
+Uniaud32 is GPL, so for license compliance any test builds that are distributed privately should not only specify the svn revision number, but also include a patch against that revision if anything differs. This is easily acquired with:
 {{{
 svn diff > my_uni32_from_r380.patch