[[PageOutline]] = Uniaud for OS/2 & eCS = This is the development home for uniaud, the Universal Audio Driver for eCS and OS/2. Share your success with Uniaud on our new SupportedHardware matrix. Download: The current stable binary release is coming soon. The current unstable binary release is [ftp://ftp.netlabs.org/pub/uniaud/uniaud114RC7.ZIP 1.1.4 RC7] released March 1, 2009 The debug build for this release is [ftp://ftp.netlabs.org/pub/uniaud/uniaud_debug114RC7.zip 1.1.4 RC7 debug] If you have HDA hardware, please try instead one or more of Paul's recent test builds, such as: [http://download.smedley.info/uniaud32-1.9.14.zip] May 17th, 2009 - Release build [http://download.smedley.info/uniaud32-1.9.14-debug.zip] May 17th, 2009 - Debug build = Getting the sources = In addition to [/uniaud/browser browsing] the sources here, you can check out the [/repos/uniaud sources] with your favorite subversion client. Keep in mind that, unlike [http://www.nongnu.org/cvs/ cvs], tags and branches are ordinary directories in subversion. With the typical subversion respository layout, it is rather easy to checkout more than you probably intend to. To pull just the trunk version, use something like {{{ mkdir uniaud32_workspace cd uniaud32_workspace svn checkout http://svn.netlabs.org/repos/uniaud/GPL/trunk trunk }}} and {{{ mkdir uniaud16_workspace cd uniaud16_workspace svn checkout http://svn.netlabs.org/repos/uniaud/OCO/trunk trunk }}} To update your workspace with the current repository content, use {{{ cd uniaud32_workspace\trunk svn update }}} If you want commit access to the repository, contact Paul. = Building the drivers = Once you have the sources, [wiki:Building building] the uniaud drivers is relatively straight-forward. You will need the following development tools: - [http://www.openwatcom.org OpenWatcom] 1.7a or later. - ilink 5.0 from IBM, or, if using wlink, you need lxlite to bring it down to size. - The DDK. - For ACPI builds, the [http://en.ecomstation.ru/projects/developer/?action=acpi ACPI toolkit]. = Distributing builds = == Uniaud16 == Public builds of uniaud16.sys are included with 1.1.4RCx packages, with the installer, uniaud32.sys of the same version, and other related files. There should not usually be a reason to publicly release Uniaud16 by itself, because any time Uniaud16 is improved it is probably a good time to release a complete package anyway. See [ReleaseProcedures Release Package Procedures] for how we go about this. 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. == Uniaud32 == Trunk (1.1.4) 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: {{{ svn diff > my_uni32_from_r380.patch }}} The experimental branches each follow very different conventions. See the explanation of the [VersioningInfo Branches and Versioning Info of Uniaud32] for details about working with them. = Debugging and such = Since the drivers are under development, issues are expected. See [DebuggingAndSuch debugging hints] for a guide to techniques and tools that can make solving them easier (we hope). = Alsa Resync = Uniaud derives some of its functionality from the [http://www.alsa.com Alsa] project. This mean we periodically [AlsaResync resync] our sources with the latest ALSA sources. This provide both aditional device support as well as defect fixes. = Submitting Tickets = You must be logged into TRAC to create tickets. Please login with your [http://www.netlabs.org Netlabs] login id. If you do not have a login id, you can request one at http://www.netlabs.org/en/site/member/member.xml. If you have troubles acquiring a [http://www.netlabs.org Netlabs] login id send an e-mail to [mailto:community@netlabs.org Netlabs Community Mailing List]. When you create a new ticket, please remember to always attach the uniaud logs.[[BR]] You can create all the logs we need, by downloading this package:[[BR]] [ftp://ftp.netlabs.org/pub/uniaud/UniInfo.zip][[BR]] Please attach the Uniinfo.zip it creates to your ticket. = Information for End Users = More information regarding selection, installation, and basic testing may be found on the [EndUserInfo End User Info] page. = Mailing lists = Access to the mailing lists is available both via e-mail and news. * [mailto://uniaud-dev-subscribe@netlabs.org Uniaud Developers Mailing List] * [mailto://uniaud-user-subscribe@netlabs.org Uniaud Users Mailing List] * [http://news.gmane.org/gmane.org.netlabs.uniaud.general Uniaud Users Newsgroup] * [http://news.gmane.org/gmane.org.netlabs.uniaud.devel Uniaud Developers Newsgroup] = Credits = * Vlad Stelmahosky * Pavel Schtemenko * Paul Smedley * Rich Jerant * Steven Levine * Mike Greene * Allan Holm * Andy Willis * Brendan Oakley * Roderick Klein If we forgot anyone, please let us know. It was unintentional. ---- []