Re: soundblaster problems in 2.1.74 and 2.1.75 : on the GUS

teunis (teunis@mauve.computersupportcentre.com)
Fri, 26 Dec 1997 06:06:12 -0700 (MST)

> > Once I got gus.o loaded and working, players still hang; strace says
> > the close command isn't returning (until I control-C the player, e.g.
> > mpg123); top says they're in the "S" (sleeping) state. Any clues as to
> > this, or is it known-broken-we're-working-on-it?
> >
>
> happens with OSS's 'play' too so it definitely is a bug, not a feature...
> [strace play...]
[clip strace - haven't a clue]
>
> > In any case, here's what I had to do; feel free to make this complete
> > and/or prepend it to drivers/sound/Readme.modules; I think that's the
> > most sensible spot, though it deserves mention somewhere more prominent,
> > like Documentation/Changes...
> >
>
> Hmm... good idea - for gus stuff look at the end of this message ;)
>
> > -----------------------------------------------------------------------------
[clip]
> > New (and Reconditioned) Parameters
> > ----------------------------------
> > The sound card modules, and the parameters they take, are known to include:
> > gus Gravis Ultrasound &c
> > io=0x220 irq=15 dma=6
> > (I don't know the keyword for the second DMA channel; there
> > is only the one IRQ needed under these drivers AFAIK

2nd DMA is for record channel (play and record seperately - completely
bidirectional card :)

> [snip, everything after ---'s automatically snipped... be careful with ---'s;)]
>
> >From gus_card.c:
>
> int io = -1;
> int irq = -1;
> int dma = -1;
> int dma16 = -1; /* Set this for modules that need it */
> int type = 0; /* 1 for PnP */
> int gus16 = 0;
> static int db16 = 0; /* Has a Gus16 AD1848 on it */
>
> MODULE_PARM(io, "i");
> MODULE_PARM(irq, "i");
> MODULE_PARM(dma, "i");
> MODULE_PARM(dma16, "i");
> MODULE_PARM(type, "i");
> MODULE_PARM(gus16, "i");
> MODULE_PARM(db16, "i");
>
> ...
> config.dma2 = dma16;
>
> Meaning gus uses that funny dma16 name too...
> I thought gus wasn't really that sb:ish... meaning it doesn't really
> differentiate between 8-bit and 16-bit dma channels or does it? ;)

No - it doesn't (afaik)

> Also another question: When do the dma channels get used? ;)
> (when does the driver actually use dma2?;)

record channel?
dma16 is here instead?

Curiouser and curiouser (waiting to upgrade as GUS + SB-16 are both in my
system and want to keep using them :) [waiting for a positive response]

G'day, eh? :)
- Teunis