Re: [Alsa-devel] ymfpci, big-endian, and spdif out
On Sat, 11 Jan 2003, Troy Benjegerdes wrote: > On Fri, Jan 10, 2003 at 07:48:48PM -0600, Troy Benjegerdes wrote: > > > > results in alsa-kernel/core/pcm_memory.c:alloc_pcm_pages() getting > > > > called with substream->dma_type= SNDRV_PCM_DMA_TYPE_UNKNOWN. > > > > > > oh, you found a bug :) it was introduced due to my last change to pcm > > > pre-allocator. now fixed on cvs. > > > > > > thanks for your report! > > > > Okay, now we're getting somewhere.. I'm not getting any errors anymore. > > The reciever (hardware AC3 decoder) is recognizing I'm sending it > > something other than PCM, but no sound comes out and none of the dolby > > digital or other indicators light up. Any ideas? > > Okay why does snd_ymfpci_playback_spdif_open use writel and every > other write to YDSXGR_SPDIFOUTSTATUS register use writew? The register is 16-bit, but I think that 32-bit accesses are not invalid (high 16-bits are not used in the register space). Anyway, I replaced writel with writew, thanks. Jaroslav - Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] MTP/AV / Sequencer MIDI problem... design issue?
On Sat, 11 Jan 2003, Ryan Pavlik wrote: > On Sat, 11 Jan 2003 20:50:49 -0500 > Paul Davis <[EMAIL PROTECTED]> wrote: > > > > i would have thought that the mtpav driver should do the same > > thing. if you want to access all 8 ports, you should have 8 access > > points (whether this is via the sequencer or the rawmidi interface), > > and write to each one of them. the use of the "Dn" byte(s?) to switch > > output ports shouldn't be exported to user space. > > It does, and you do... except the driver has the problems with parallel > access of ports I mentioned in the original message. When you access > them with the sequencer API, the driver/library doesn't seem to properly > send entire messages. Thus the problem arises. If the device needs full midi messages a stream parser must be implemented in the mtpav driver. There is no guarantee, that the MIDI message is complete in the rawmidi implementation. It behaves like a char stream device (something like tty). Example: port #2 received three bytes from an application: 0x80 0x10 0x15 port #3 received three bytes from an application: 0x90 0x20 0x00 So the mtpav driver might send this sequence in this order: 0xf5 0x02 0x80 0xf5 0x03 0x90 0xf5 0x02 0x10 0x15 0xf5 0x03 0x20 0x00 Where 0xf5 0xXX are port addresses. There is guarantee (using spinlocks) that the port will receive the right values but not whole midi message at once. I think that the problem might be in another code. Jaroslav - Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] [Application] OPL3 with hwdep
I want to make a simple OPL3 beeper, but I'm stuck with snd_hwdep_open(), I just don't know what string I should call it with. pupilla:~$ cat /proc/asound/cards 0 [CARD_0 ]: CMI8738-MC6 - C-Media PCI CMI8738-MC6 C-Media PCI CMI8738-MC6 (model 55) at 0xb800, irq 9 pupilla:~$ cat /proc/asound/hwdep 00-00: OPL3 FM pupilla:~$ cat /proc/asound/devices 0: [0- 0]: ctl 8: [0- 0]: raw midi 18: [0- 2]: digital audio playback 26: [0- 2]: digital audio capture 17: [0- 1]: digital audio playback 16: [0- 0]: digital audio playback 24: [0- 0]: digital audio capture 4: [0- 0]: hardware dependent 1: : sequencer 33: : timer I've tried lots of combinations, but it always fail... :-( -- Saluti, Mardy http://castellina.org/interlingua --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [Application] OPL3 with hwdep
On Sun, 12 Jan 2003, Mardy wrote: > I want to make a simple OPL3 beeper, but I'm stuck with > snd_hwdep_open(), I just don't know what string I should call it with. hw:# (where # is your card number or string identification), it is usually 'hw:0'; or the more simple way is to pass 'default' string as hwdep name Jaroslav - Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [Application] OPL3 with hwdep
On Sun, Jan 12, 2003 at 08:12:53PM +0100, Jaroslav Kysela wrote: > On Sun, 12 Jan 2003, Mardy wrote: > > > I want to make a simple OPL3 beeper, but I'm stuck with > > snd_hwdep_open(), I just don't know what string I should call it with. > > hw:# (where # is your card number or string identification), it is usually > 'hw:0'; or the more simple way is to pass 'default' string as hwdep name Tried both, but I still get a -2. I'm using Debian woody (libasound2 0.9.0beta10a-3). -- Saluti, Mardy http://castellina.org/interlingua --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
