Release summary: (detailed descriptions in Edit History in matcd.c)

Adds support for non-Sound Blaster host adapters, including those
distributed by Reveal, Lasermate, IBM, Media Vision, Crystal and others.
The driver automatically senses the correct adapter type and you can
have both in the system at the same time.
(This change should eliminate a few complaints.)

Corrected bit-masking problem that prevented use on SB Vibra-16 boards.

Declared some internal data and functions static that should have been
that way all along.

Documentation changes reflect the new hardware support and change the
appearance version to 2.0.5 (was 2.1).    Nice and tidy.   :-)


Beta testers have verified functionality on SB16, Vibra-16, Media Vision
and Reveal adapters.   -Wall still shows no warnings.

                                        Frank Durda IV
                                        uhclem%nemesis@fw.ast.com
Submitted by:	Frank Durda IV <uhclem%nemesis@fw.ast.com>

1 files changed, 7 insertions, 15 deletions

diff --git a/sys/i386/isa/matcd/TODO b/sys/i386/isa/matcd/TODO
index 62035fc..138f470 100644
--- a/sys/i386/isa/matcd/TODO
+++ b/sys/i386/isa/matcd/TODO
@@ -1,43 +1,35 @@
-Things to do for the matcd driver			6-Apr-95
+Things to do for the matcd driver			4-Jul-95
 
-1.	Just as I was finishing Edit 16, I discovered that there
-	may be a way to cause a drive to go "offline", allowing the host
-	to send a command to one or more other drives on the same
-	interface, similar to the SCSI disconnect mechanism.  The changes
-	to the driver to take advantage of this aren't huge, but will have
-	to wait until after 2.1.  Too much risk of breaking something.
-	Unless you have multiple drives, you won't see a difference.
-
-2.	Someone wants to switch all drivers from disklabel and
+1.	Someone wants to switch all drivers from disklabel and
 	its assorted mechanisms over to disk slicing and its mechanisms,
 	but I was unable to find any useful documentation on how to 
 	implement the changes for a read-only, single-partition,
 	removable (ie, partition can change size) device.
 	So this will have to wait until after 2.1.
 
-3.	Support for reading R-W subcodes while playing audio.  This would be
+2.	Support for reading R-W subcodes while playing audio.  This would be
 	useful if you have any CD+G or CD+MIDI discs, but the demand for this
 	is pretty low, unless you like Karaoke.  Someone will also have to
 	write a CD+G viewer for X.  The code for the driver to add this is
 	pretty minor but there aren't any precedents on how to handle the
 	data transfer to the application.
 
-4.	Support for reading the ISBN and UPC labels.   The ioctl structures
+3.	Support for reading the ISBN and UPC labels.   The ioctl structures
 	for these appear to be defined but no other driver seems to do this.
 
-5.	Multi-session support.  There are two forms of this; what
+4.	Multi-session support.  There are two forms of this; what
 	Philips defined and what Kodak uses.  This will be quite
 	complicated and will probably require changes in the filesystem
 	layer.   The drive support for Kodak multi-session is known to work.
 
-6.	Multiple data tracks.  My vision here was to add an ioctl
+5.	Multiple data tracks.  My vision here was to add an ioctl
 	that caused a track offset to be inserted into block requests,
 	effectively shifting the base to the specified track.  Very
 	easy to add but not a big deal since I have only two discs
 	in my collection that have multiple data tracks and I mastered
 	one of them.
 
-7.	A curses-based CD-Player app (ie, not X).  I will probably do this
+6.	A curses-based CD-Player app (ie, not X).  I will probably do this
 	mainly for its value as a debugging tool.  It was pretty annoying
 	not finding a single application that actually issued all the
 	defined ioctls, let alone any new ones.