On Mon, 2004-06-21 at 11:35, Takashi Iwai wrote:
> At Sun, 20 Jun 2004 00:06:23 -0400,
> Lee Revell wrote:
> > 
> > Now, there is one more issue.  For some reason, in the emu10k1 driver, 
> > different numbered devices are used for FXBus capture and playback -
> > capture is hw:0,2 and playback is hw:0,3.  I don't think JACK supports 
> > full duplex mode if the playback and capture devices are different.  
> > It seems like these should be part of the same device anyway, they refer
> > to the exact same registers.
> 
> Yes, it would make more sense.  I'll fix this, too.
> 
> Meanwhile, you can use asym plugin for this purpose, e.g. adding the
> following to ~/.asoundrc:
> 
> 	pcm.fx {
> 		type asym
> 		playback.pcm "hw:0,3"
> 		capture.pcm "hw:0,2"
> 	}
> 
> and use the PCM "fx" for jack.
> 

Now that I understand the driver more completely, I think that merging
these devices does not make sense.

The FXBus playback device is used for AC3 passthrough (referred to as
'Raw SPDIF PCM' in the driver source), and uses TRAM and DSP code.  The
capture device uses the FXWC register and the normal DMA buffer, and can
capture any of the 64 FXBus outputs (with Peter Zubaj's patch).  These
devices actually have almost nothing to do with each other.

I think this change should be backed out.  I am working on a new device
for multichannel, low latency capture and playback but I think it will 
merged with the current FXBus capture device, hw:x,2.  The AC3
passthrough device should be moved back to hw:x,3.  Once the driver can
support capture of raw AC3 stream, then a corresponding hw:x,3 capture
device can be added.

Also, I have attached a patch to fix a few magic numbers in emupcm.c.

Lee