From owner-freebsd-current  Fri Mar 17 19:30:08 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA07763 for current-outgoing; Fri, 17 Mar 1995 19:30:08 -0800
Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA07754 for <current@freebsd.org>; Fri, 17 Mar 1995 19:30:02 -0800
Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id WAA01243; Fri, 17 Mar 1995 22:29:52 -0500
From: "matthew c. mead" <mmead@goof.com>
Message-Id: <199503180329.WAA01243@goof.com>
Subject: Re: GUS on kernel supped last night
To: faulkner@mpd.tandem.com (Boyd Faulkner)
Date: Fri, 17 Mar 1995 22:29:51 -0500 (EST)
Cc: swallace@ece.uci.edu, faulkner@devnull.mpd.tandem.com, current@FreeBSD.org
In-Reply-To: <9503172217.AA11721@olympus> from "Boyd Faulkner" at Mar 17, 95 04:17:48 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1948      
Sender: current-owner@FreeBSD.org
Precedence: bulk

Boyd Faulkner wrote:

[ my grumblings about GUS MAX with the sound driver ]

> > > Perhaps you should try removing the gusmax0 driver.

> > 	Building that kernel now.

> I'm not sure it works with this as I think I just did it to see if it would
> probe.  I may not have tested the sound.  It does work "fairly" well without.

> cat *.au > /dev/audio OK
> MODs have pops and cracks but the underlying music is good.
> I can't get xvmixer to load under X.  Says it can't attach to the Server.
> It is an Xview message.  I don't get it.  I am rebuilding Xview to see
> if I can solve the problem.

	Sounds like an XView thing - I just got up and running on the kernel
without the gusmax0 support, but with regular gus support, and it works ok for
cat >/dev/audio, midi works great, but things played with /dev/dsp (like
.wav's) have that repeat at the end of them - mods are crackly and suffer from
the end of the sample repeat (since /dev/dsp is used?).

> > > There have been no code changes in functionality, just the way the
> > > drivers are configured.

	Yeah - it now appears that when the only thing I configure is the GUS,
it works *CLOSE* to perfectly (symptoms described above) - but when I add in
the others, it breaks.

> > > People running -curent should make sure the port/irq/dma in the device
> > > config matches what their card actually uses.

> > 	They're the same.

> Ditto.


	So - now that I've complained a lot, and done so much kernel rebuilding
and testing - what do I need to do in order to "get my feet wet," and "my hands
dirty," and help out with fixing the code?  Thanks, guys, for your patience,
and time!


-matt

-- 
Matthew C. Mead  -> Virginia Tech Center for Transportation Research -
                 -> Multiple Platform System and Network Administration
Work Related     -> mmead@ctr.vt.edu    |     mmead@goof.com <-     All Other
---- -------            WWW -> http://www.goof.com/~mmead           --- -----