[Alsa-devel] Terratec Phase 88 support?
Hi, The Terratec EWS88MT is a very affordable multichannel soundcard with ALSA support that has unfortunately been discontinued, as I understand from their distributors. It is replaced by the Phase 88, which appears to be a very similar card and might in fact just be a rebranded EWS88MT. Someone replaced the PCI ID in the EWS ALSA driver with that of the Phase 88, and was able to play back sounds via ALSA. Recording and mixing seems to be a problem, though. I plan on buying some of these cards in the near future, but I need recording functionality using JACK. Without an ALSA driver, I therefore can't use it. Is there anyone working on a driver for this card? Could the people who wrote the EWS driver maybe look into this? If this driver doesn't materialize soon, are there any alternative affordable multichannel soundcards (meaning 8-channel cards costing about $400) I can consider? Thanks very much in advance, Ludwig Schwardt --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] [PATCH] Terratec PHASE 26 MIDI support
This adds a quirk for the PHASE 26's MIDI interface.
Index: alsa-kernel/usb/usbquirks.h
===
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbquirks.h,v
retrieving revision 1.26
diff -u -r1.26 usbquirks.h
--- alsa-kernel/usb/usbquirks.h 20 Jan 2004 15:31:59 - 1.26
+++ alsa-kernel/usb/usbquirks.h 11 Feb 2004 09:33:45 -
@@ -688,4 +688,14 @@
},
+{
+ USB_DEVICE_VENDOR_SPEC(0x0ccd, 0x0013),
+ .driver_info = (unsigned long) (const snd_usb_audio_quirk_t) {
+ .vendor_name = Terratec,
+ .product_name = PHASE 26,
+ .ifnum = 3,
+ .type = QUIRK_MIDI_STANDARD_INTERFACE
+ }
+},
+
#undef USB_DEVICE_VENDOR_SPEC
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] [PATCH] AD1888 support
This adds support for the AD1888 (same as AD1980, but without 2CMIC).
Not tested.
Index: alsa-kernel/pci/ac97/ac97_codec.c
===
RCS file: /cvsroot/alsa/alsa-kernel/pci/ac97/ac97_codec.c,v
retrieving revision 1.120
diff -u -r1.120 ac97_codec.c
--- alsa-kernel/pci/ac97/ac97_codec.c 9 Feb 2004 12:01:07 - 1.120
+++ alsa-kernel/pci/ac97/ac97_codec.c 11 Feb 2004 09:26:20 -
@@ -100,6 +100,7 @@
{ 0x41445361, 0x, AD1886,patch_ad1886, NULL },
{ 0x41445362, 0x, AD1887,patch_ad1881, NULL },
{ 0x41445363, 0x, AD1886A, patch_ad1881, NULL },
+{ 0x41445368, 0x, AD1888,patch_ad1888, NULL },
{ 0x41445370, 0x, AD1980,patch_ad1980, NULL },
{ 0x41445372, 0x, AD1981A, patch_ad1981a, NULL },
{ 0x41445374, 0x, AD1981B, patch_ad1981b, NULL },
Index: alsa-kernel/pci/ac97/ac97_patch.c
===
RCS file: /cvsroot/alsa/alsa-kernel/pci/ac97/ac97_patch.c,v
retrieving revision 1.34
diff -u -r1.34 ac97_patch.c
--- alsa-kernel/pci/ac97/ac97_patch.c 9 Feb 2004 11:45:40 - 1.34
+++ alsa-kernel/pci/ac97/ac97_patch.c 11 Feb 2004 09:26:20 -
@@ -799,7 +799,7 @@
return 0;
}
-static int snd_ac97_ad1980_lohpsel_info(snd_kcontrol_t *kcontrol, snd_ctl_elem_info_t
*uinfo)
+static int snd_ac97_ad1888_lohpsel_info(snd_kcontrol_t *kcontrol, snd_ctl_elem_info_t
*uinfo)
{
uinfo-type = SNDRV_CTL_ELEM_TYPE_BOOLEAN;
uinfo-count = 1;
@@ -808,7 +808,7 @@
return 0;
}
-static int snd_ac97_ad1980_lohpsel_get(snd_kcontrol_t *kcontrol,
snd_ctl_elem_value_t* ucontrol)
+static int snd_ac97_ad1888_lohpsel_get(snd_kcontrol_t *kcontrol,
snd_ctl_elem_value_t* ucontrol)
{
ac97_t *ac97 = snd_kcontrol_chip(kcontrol);
unsigned short val;
@@ -818,7 +818,7 @@
return 0;
}
-static int snd_ac97_ad1980_lohpsel_put(snd_kcontrol_t *kcontrol, snd_ctl_elem_value_t
*ucontrol)
+static int snd_ac97_ad1888_lohpsel_put(snd_kcontrol_t *kcontrol, snd_ctl_elem_value_t
*ucontrol)
{
ac97_t *ac97 = snd_kcontrol_chip(kcontrol);
unsigned short val;
@@ -829,7 +829,7 @@
AC97_AD198X_LOSEL | AC97_AD198X_HPSEL, val);
}
-static int snd_ac97_ad1980_downmix_info(snd_kcontrol_t *kcontrol, snd_ctl_elem_info_t
*uinfo)
+static int snd_ac97_ad1888_downmix_info(snd_kcontrol_t *kcontrol, snd_ctl_elem_info_t
*uinfo)
{
static char *texts[3] = {Off, 6 - 4, 6 - 2};
@@ -842,7 +842,7 @@
return 0;
}
-static int snd_ac97_ad1980_downmix_get(snd_kcontrol_t *kcontrol,
snd_ctl_elem_value_t* ucontrol)
+static int snd_ac97_ad1888_downmix_get(snd_kcontrol_t *kcontrol,
snd_ctl_elem_value_t* ucontrol)
{
ac97_t *ac97 = snd_kcontrol_chip(kcontrol);
unsigned short val;
@@ -855,7 +855,7 @@
return 0;
}
-static int snd_ac97_ad1980_downmix_put(snd_kcontrol_t *kcontrol, snd_ctl_elem_value_t
*ucontrol)
+static int snd_ac97_ad1888_downmix_put(snd_kcontrol_t *kcontrol, snd_ctl_elem_value_t
*ucontrol)
{
ac97_t *ac97 = snd_kcontrol_chip(kcontrol);
unsigned short val;
@@ -871,51 +871,47 @@
AC97_AD198X_DMIX0 | AC97_AD198X_DMIX1, val);
}
-static const snd_kcontrol_new_t snd_ac97_ad1980_controls[] = {
+static const snd_kcontrol_new_t snd_ac97_ad1888_controls[] = {
{
.iface = SNDRV_CTL_ELEM_IFACE_MIXER,
.name = Exchange Front/Surround,
- .info = snd_ac97_ad1980_lohpsel_info,
- .get = snd_ac97_ad1980_lohpsel_get,
- .put = snd_ac97_ad1980_lohpsel_put
+ .info = snd_ac97_ad1888_lohpsel_info,
+ .get = snd_ac97_ad1888_lohpsel_get,
+ .put = snd_ac97_ad1888_lohpsel_put
},
AC97_SINGLE(Spread Front to Surround and Center/LFE, AC97_AD_MISC, 7, 1, 0),
{
.iface = SNDRV_CTL_ELEM_IFACE_MIXER,
.name = Downmix,
- .info = snd_ac97_ad1980_downmix_info,
- .get = snd_ac97_ad1980_downmix_get,
- .put = snd_ac97_ad1980_downmix_put
+ .info = snd_ac97_ad1888_downmix_info,
+ .get = snd_ac97_ad1888_downmix_get,
+ .put = snd_ac97_ad1888_downmix_put
},
AC97_SINGLE(Surround Jack as Input, AC97_AD_MISC, 12, 1, 0),
AC97_SINGLE(Center/LFE Jack as Input, AC97_AD_MISC, 11, 1, 0),
};
-static int patch_ad1980_specific(ac97_t *ac97)
+static int patch_ad1888_specific(ac97_t *ac97)
{
- int err;
-
/* rename 0x04 as Master and 0x02 as Master Surround */
snd_ac97_rename_ctl(ac97, Master Playback Switch, Master Surround Playback
Switch);
snd_ac97_rename_ctl(ac97, Master Playback Volume, Master Surround Playback
Volume);
Re: [Alsa-devel] Creamware Noah, snd-usb-audio capable?
Frank Barknecht wrote:
Hartmut Geissbauer hat gesagt: // Hartmut Geissbauer wrote:
reading the different entries in usbquirks.h it looks like they are
taken from the usb-infos like lsusb provides. Is it very difficult to
take the infos from lsusb and translate it to an quirk?
It depends. If the class-specific descriptors are missing, you have
to guess and try what the sample format actually is.
[...] I was investigating why the Midi jacks on the Terratec Phase
26 aren't supported.
I looked up the specification of usb-midi in
http://www.usb.org/developers/devclass_docs/midi10.pdf and also looked
very closely and for a long time at the lsusb output. This interface
descriptor then looks very much like it must be the midi interface:
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber3
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 3
bInterfaceProtocol 0
iInterface 3 TerraTec PHASE 26 USB
unknown descriptor type: 07 24 01 00 01 41 00
unknown descriptor type: 06 24 02 01 10 00
unknown descriptor type: 06 24 02 02 11 00
unknown descriptor type: 09 24 03 01 12 01 11 01 00
unknown descriptor type: 09 24 03 02 13 01 10 01 00
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes2
Transfer TypeBulk
Synch Type none
wMaxPacketSize 64
bInterval 0
bRefresh0
bSynchAddress 0
unknown descriptor type: 05 25 01 01 10
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes2
Transfer TypeBulk
Synch Type none
wMaxPacketSize 64
bInterval 0
bRefresh0
bSynchAddress 0
unknown descriptor type: 05 25 01 01 12
The main reason for my assumption is the value for bInterfaceNumber
which is 3 or 0x03 as it should be according to the USB spec which
requires for a MIDI Adapter Standard MIDIStreaming Interface
Descriptor to have this field set as follows:
Offset FieldSize Value Description
...
6 bInterfaceSubclass 1 0x03 MIDISTREAMING.
...
The bInterfaceNumber field simply specifies the number (i.e., the
index) of the interface. Interfaces must be numbered 0, 1, 2, etc.
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 3
bInterfaceProtocol 0
The problem is that bInterfaceClass isn't set to 1 (Audio).
The class-specific descriptors are there (lsusb shows them as
unknown because it doesn't try to parse vendor-specific things), so
it should be possible to use the MIDI_STANDARD_INTERFACE quirk (see
below).
Regards,
Clemens
--
Index: alsa-kernel/usb/usbquirks.h
===
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbquirks.h,v
retrieving revision 1.26
diff -u -r1.26 usbquirks.h
--- alsa-kernel/usb/usbquirks.h 20 Jan 2004 15:31:59 - 1.26
+++ alsa-kernel/usb/usbquirks.h 11 Feb 2004 09:33:45 -
@@ -688,4 +688,14 @@
},
+{
+ USB_DEVICE_VENDOR_SPEC(0x0ccd, 0x0013),
+ .driver_info = (unsigned long) (const snd_usb_audio_quirk_t) {
+ .vendor_name = Terratec,
+ .product_name = PHASE 26,
+ .ifnum = 3,
+ .type = QUIRK_MIDI_STANDARD_INTERFACE
+ }
+},
+
#undef USB_DEVICE_VENDOR_SPEC
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] CARDBUS problems
At Tue, 10 Feb 2004 18:20:58 +0100 (CET), Giuliano Pochini wrote: I have problems running my driver with a Layla24-CARDBUS card. The same driver works fine with the PCI version of the card and the manufacturer says they're identical. Is there something I have to take care of in case the card is connected to the CARDBUS port ? from the driver viewpoint, there is no difference. Takashi --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Using preallocate pci, isa or nothing?
At Sun, 8 Feb 2004 18:29:10 -0600, Mathieu Rondonneau wrote: Hi, I'm sorry for the html format, these are some questions according to my problems. I'm writing an ALSA driver for a CSB337 board (AT91RM9200). There is no PCI or ISA on this board. Should I preallocate memory with: snd_pcm_lib_preallocate_pages_for_all, snd_pcm_lib_preallocate_isa_pages_for_all() or snd_pcm_lib_preallocate_pci_pages_for_all()? There is a specific DMA (PDC) on the AT91RM9200, so i'm trying to use snd_pcm_lib_preallocate_pages_for_all() but seems complicated to understand what is needed by the ALSA pcm and what i have to write. What does the function snd_..._pointer() mean? should i need it if i don't use ISA or PCI mecanism? What does the function snd_pcm_period_elapsed() mean? Should i need it if i don't use ISA or PCI mecanism? did you take a look at my document? http://www.alsa-project.org/~iwai/writing-an-alsa-driver/ Takashi --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [PATCH] Terratec PHASE 26 MIDI support
At Wed, 11 Feb 2004 10:47:33 +0100 (MET), Clemens Ladisch wrote: This adds a quirk for the PHASE 26's MIDI interface. thanks, is on cvs now. Takashi --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] I think MSI KT6 Delta-SR also needs VIA_DXS_NO_VRA in whitelist
At Wed, 11 Feb 2004 16:02:00 +0100,
Kristof vansant wrote:
This: ?
yes.
:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/
A/8235 AC97 Audio Controller (rev 60)
:00:11.5 Class 0401: 1106:3059 (rev 60)
Subsystem: 1462:5901
Flags: medium devsel, IRQ 11
I/O ports at d800
Capabilities: [c0] Power Management version 2
could you test the attached patch?
thanks,
Takashi
Index: alsa-kernel/pci/via82xx.c
===
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/via82xx.c,v
retrieving revision 1.94
diff -u -r1.94 via82xx.c
--- alsa-kernel/pci/via82xx.c 11 Feb 2004 12:05:28 - 1.94
+++ alsa-kernel/pci/via82xx.c 11 Feb 2004 15:06:44 -
@@ -1994,6 +1994,7 @@
{ .vendor = 0x14ff, .device = 0x0403, .action = VIA_DXS_ENABLE }, /*
Twinhead mobo */
{ .vendor = 0x1462, .device = 0x3800, .action = VIA_DXS_ENABLE }, /*
MSI KT266 */
{ .vendor = 0x1462, .device = 0x7120, .action = VIA_DXS_ENABLE }, /*
MSI KT4V */
+ { .vendor = 0x1462, .device = 0x5901, .action = VIA_DXS_NO_VRA }, /*
MSI KT6 Delta-SR */
{ .vendor = 0x1631, .device = 0xe004, .action = VIA_DXS_ENABLE }, /*
Easy Note 3174, Packard Bell */
{ .vendor = 0x1695, .device = 0x3005, .action = VIA_DXS_ENABLE }, /*
EPoX EP-8K9A */
{ .vendor = 0x1849, .device = 0x3059, .action = VIA_DXS_NO_VRA }, /*
ASRock K7VM2 */
[Alsa-devel] Can someone test my patch: without it alsa wouldn't build on kernel 2.6.1
Warning I'm running kernel 2.6.1 from redhat so not vanilla. I don't
know for sure if the problem is with kernel 2.6.1 vanilla to.
After the patch it compiles normal :)
error:
make -C /lib/modules/2.6.1-1.65/build SUBDIRS=/home/lupus/alsa-driver-
1.0.2c/kbuild modules
make[1]: Entering directory `/lib/modules/2.6.1-1.65/build'
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
CHK include/asm-i386/asm_offsets.h
CC [M] /home/lupus/alsa-driver-1.0.2c/kbuild/../acore/memalloc.o
In file included from /home/lupus/alsa-driver-1.0.2c/acore/memalloc.
inc:13,
from /home/lupus/alsa-driver-1.0.2c/acore/memalloc.c:1:
/home/lupus/alsa-driver-1.0.2c/include/adriver.h:425: error: conflicting
types for `class_simple_device_add'
include/linux/device.h:255: error: previous declaration of
`class_simple_device_add'
/home/lupus/alsa-driver-1.0.2c/include/adriver.h:426: error: conflicting
types for `class_simple_device_remove'
include/linux/device.h:256: error: previous declaration of
`class_simple_device_remove'
make[3]: *** [/home/lupus/alsa-driver-1.0.2c/kbuild/../acore/memalloc.o]
Fout 1
make[2]: *** [/home/lupus/alsa-driver-1.0.2c/kbuild/../acore] Fout 2
make[1]: *** [/home/lupus/alsa-driver-1.0.2c/kbuild] Fout 2
make[1]: Leaving directory `/lib/modules/2.6.1-1.65/build'
make: *** [compile] Fout 2
--- ./include/adriver.h.kernel261 2004-02-11 16:57:13.708662312 +0100
+++ ./include/adriver.h 2004-02-11 16:57:25.869813536 +0100
@@ -420,7 +420,7 @@
#endif
/* sysfs */
-#if LINUX_VERSION_CODE KERNEL_VERSION(2, 6, 2)
+#if LINUX_VERSION_CODE KERNEL_VERSION(2, 6, 1)
struct class_simple;
static inline void class_simple_device_add(struct class_simple *class, int devnum, ...) { return; }
static inline void class_simple_device_remove(int devnum) { return; }
Re: [Alsa-devel] I think MSI KT6 Delta-SR also needs VIA_DXS_NO_VRA in whitelist
How can I see that it is enabled? I patched it and installed it. At Wed, 11 Feb 2004 16:02:00 +0100, Kristof vansant wrote: This: ? yes. :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/ A/8235 AC97 Audio Controller (rev 60) :00:11.5 Class 0401: 1106:3059 (rev 60) Subsystem: 1462:5901 Flags: medium devsel, IRQ 11 I/O ports at d800 Capabilities: [c0] Power Management version 2 could you test the attached patch? thanks, Takashi --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Creamware Noah, snd-usb-audio capable?
Hallo, Clemens Ladisch hat gesagt: // Clemens Ladisch wrote: Frank Barknecht wrote: The main reason for my assumption is the value for bInterfaceNumber which is 3 or 0x03 as it should be according to the USB spec which requires for a MIDI Adapter Standard MIDIStreaming Interface Descriptor to have this field set as follows: Offset FieldSize Value Description ... 6 bInterfaceSubclass 1 0x03 MIDISTREAMING. ... The bInterfaceNumber field simply specifies the number (i.e., the index) of the interface. Interfaces must be numbered 0, 1, 2, etc. Ah, my fault: I intended to write bInterfaceSubclass as in the spec quote... The problem is that bInterfaceClass isn't set to 1 (Audio). The class-specific descriptors are there (lsusb shows them as unknown because it doesn't try to parse vendor-specific things), so it should be possible to use the MIDI_STANDARD_INTERFACE quirk (see below). I'd love to test it, but I had to send back the device already. :( Could you test it? ciao -- Frank Barknecht _ __footils.org__ --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Using preallocate pci, isa or nothing?
At Sun, 8 Feb 2004 18:29:10 -0600, Mathieu Rondonneau wrote: Hi, I'm sorry for the html format, these are some questions according to my problems. I'm writing an ALSA driver for a CSB337 board (AT91RM9200). There is no PCI or ISA on this board. Should I preallocate memory with: snd_pcm_lib_preallocate_pages_for_all, snd_pcm_lib_preallocate_isa_pages_for_all() or snd_pcm_lib_preallocate_pci_pages_for_all()? There is a specific DMA (PDC) on the AT91RM9200, so i'm trying to use snd_pcm_lib_preallocate_pages_for_all() but seems complicated to understand what is needed by the ALSA pcm and what i have to write. What does the function snd_..._pointer() mean? should i need it if i don't use ISA or PCI mecanism? What does the function snd_pcm_period_elapsed() mean? Should i need it if i don't use ISA or PCI mecanism? did you take a look at my document? http://www.alsa-project.org/~iwai/writing-an-alsa-driver/ Takashi Yes I did, and i thank you for your work, your document is very helpfull. But, i'm not familiar with ALSA driver development. Could I use PCI or ISA mecanism (memory allocation and dma) even if there are no PCI or ISA bus in my board? If i don't use it, it's more work to do. I 'm just wondering if i could use more ALSA function in order to simplify my development. I'm sorry for my english (i'm french) Thank you very much for your help. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Using preallocate pci, isa or nothing?
At Wed, 11 Feb 2004 14:39:47 -0600, Mathieu Rondonneau wrote: At Sun, 8 Feb 2004 18:29:10 -0600, Mathieu Rondonneau wrote: Hi, I'm sorry for the html format, these are some questions according to my problems. I'm writing an ALSA driver for a CSB337 board (AT91RM9200). There is no PCI or ISA on this board. Should I preallocate memory with: snd_pcm_lib_preallocate_pages_for_all, snd_pcm_lib_preallocate_isa_pages_for_all() or snd_pcm_lib_preallocate_pci_pages_for_all()? There is a specific DMA (PDC) on the AT91RM9200, so i'm trying to use snd_pcm_lib_preallocate_pages_for_all() but seems complicated to understand what is needed by the ALSA pcm and what i have to write. What does the function snd_..._pointer() mean? should i need it if i don't use ISA or PCI mecanism? What does the function snd_pcm_period_elapsed() mean? Should i need it if i don't use ISA or PCI mecanism? did you take a look at my document? http://www.alsa-project.org/~iwai/writing-an-alsa-driver/ Takashi Yes I did, and i thank you for your work, your document is very helpfull. But, i'm not familiar with ALSA driver development. Could I use PCI or ISA mecanism (memory allocation and dma) even if there are no PCI or ISA bus in my board? then, no. but note that the functions you asked above have basically nothing to do with PCI or ISA. the whole preallocation meachanism is provided for the abstraction regardless of BUS type. also, pcm and control callbacks are also irrelevant to BUS type. Takashi --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] When I use xmms with OSS plugin sound is normal with the ALSA plugin sound skips sometimes
When I use xmms with OSS plugin sound is normal but with the ALSA plugin sound skips sometimes. Is this a xmms problem? Or makes OSS emulation the sound stable? :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/ A/8235 AC97 Audio Controller (rev 60) 0-0/0: C-Media Electronics CMI9739 modprobe.conf: alias eth0 ne2k-pci alias eth1 b44 alias sound-slot-0 snd-via82xx install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L /dev/null 21 || : remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S /dev/null 21 || : alias char-major-81 bttv alias usb-controller ehci-hcd alias usb-controller1 uhci-hcd alsa-driver-1.2c kernel-2.6.1 --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: still interested in us224 support?
Am Dienstag, 10. Februar 2004 19:58 schrieben Sie: I had some time to try us428control. I tried to run it without arguments, but it complained about no-existent /dev/seq (don't have built-in sequencer in my internal sound card). I tried to use options /dev/seq refers here to a software-alsa-part. see my computers answer to $cat /proc/asound/devices 0: [0- 0]: ctl 8: [0- 0]: raw midi 16: [0- 0]: digital audio playback 24: [0- 0]: digital audio capture 1: : sequencer this is alsas sequencer 33: : timer 32: [1- 0]: ctl 36: [1- 0]: hardware dependent 48: [1- 0]: digital audio playback 56: [1- 0]: digital audio capture 40: [1- 0]: raw midi the alsa's sequencer is definitly needed to let us428control work. the corresponding module is snd-seq-device. lsmod should show it. if not, try modprobe snd-seq-device. if snd-seq-device is missing, build it. configure alsa-driver by creating the file /etc/asound/driver_args. mine looks like: --with-cards=via82xx,msnd-pinnacle,usb-audio,usb-usx2y,es1968 --with-kernel=/usr/src/linux-2.4 --with-debug=full --with-sequencer=yes then rebuild with ./cvscompile etc. to override this, but i must admit i'm not sure i understand all alsa principles. I tried options like : # ./us428control -Dhw1,0,0 ALSA lib hwdep.c:151:(snd_hwdep_open_noupdate) Unknown HwDep hw1,0,0 # ./us428control -D1,0 ALSA lib hwdep.c:151:(snd_hwdep_open_noupdate) Unknown HwDep 1,0 # ./us428control -chw1,0,0 us428control: cannot open hwdep hw:0 # ./us428control -chw1,0 us428control: cannot open hwdep hw:0 start it like $us428control -v2 -Dhw:X or $us428control -v2 -cX with X=index of the card. But I thought there were a control midi port on us224, which to seems noexistent with alsa ? us428 controls work. provided us428control runs. I cand send more usb snooping if needed. try to get us428control running first. if us224 is very similar to 428, you'll get a printout of lots of control numbers if you use the controls and have started us428control with option -v2. You uncommented any section containing USB_ID_US224 in snd-usb-usx2y? Also for trying on us224 please change usbusx2yaudio.c line 1244 (usX2Y(card)-chip.dev-descriptor.idProduct == USB_ID_US428 to (usX2Y(card)-chip.dev-descriptor.idProduct == USB_ID_US224 Also tried this change (just to test) : Feb 7 11:57:31 ouragan /etc/hotplug/usb.agent: Module setup tascam_fpga for USB product 1604/8005/1 Feb 7 11:57:31 ouragan /etc/hotplug/usb/tascam_fpga: calling /usr/local/bin/usx2yloader for /proc/bus/usb/001/010 Feb 7 11:57:35 ouragan kernel: ALSA usX2Yhwdep.c:315: snd_usX2Y_create_alsa_devices error -19 this only happens with the change aplied? so this change doesn't help. Karsten --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: When I use xmms with OSS plugin sound is normal with the ALSA plugin sound skips sometimes
Kristof vansant [EMAIL PROTECTED] writes: When I use xmms with OSS plugin sound is normal but with the ALSA plugin sound skips sometimes. Is this a xmms problem? Or makes OSS emulation the sound stable? It's an xmms problem. Read the code and you'll see why. It can skip with OSS output too. -- Måns Rullgård [EMAIL PROTECTED] --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] ISA pnp kernel 2.6
I have an ISA pnp card (opti931) which stopped working when I installed kernel 2.6 and the problem is as follows: The kernel function that sets and activates the card is isapnp_set_resources (in drivers/pnp/isapnp/core.c) and for each resource, it is checking that the correct flag is set before writing to the port (i.e. IORESOURCE_IO, IORESOURCE_IRQ, IORESOURCE_DMA, IORESOURCE_MEM) however, these flags are never being set because the driver code is just using pnp_init_resource_table followed by pnp_resource_change for each setting and so the configuration is never written to the card. (I believe that the equivalent code in 2.4 just checked for flags != 0). As I see it, there are four options: 1) Manually set the flags in the driver code (this is what I have done temporarily to get the card working). 2) Change the test in isapnp_set_resources to ((flags IORESOURCE_xx) | (~flags IORESOURCE_AUTO)) as anything that has been auto-allocated should have the appropriate flag set. 3) Change pnp_resource_change to clear IORESOURCE_UNSET and change the test in isapnp_set_resources to (~flags IORESOURCE_UNSET) 4) In the driver, use something else apart from pnp_resource_change (i.e. is there now a preferred method for filling in the settings). I prefer 3) or else 2) but are there any reasons not to do this? Any advice welcome. Michael. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] intel8x0 CVS - warnings in console log
Hi, I have just noticed these errors in my console log (with the few line immediately before): Feb 11 20:01:58 twopit kernel: PCI: Setting latency timer of device :00:1f.5 to 64 Feb 11 20:01:59 twopit kernel: intel8x0_measure_ac97_clock: measured 49371 usecs Feb 11 20:01:59 twopit kernel: intel8x0: clocking to 48000 Feb 11 21:47:31 twopit kernel: ALSA /home/chris/Programs/alsa/alsa-driver/pci/intel8x0.c:817: intel8x0: unknown IRQ bits 0x100 (sta_mask=0xe0) Feb 11 21:47:32 twopit last message repeated 8 times I am running Linux 2.6.2 with the latest CVS drivers. The chip in question is the on-board Intel 82801AA-ICH, Cirrus Logic CS4299 rev 4, running as my second sound device. This is the first time that I have noticed these errors. Cheers, Chris ___ BT Yahoo! Broadband - Free modem offer, sign up online today and save £80 http://btyahoo.yahoo.co.uk --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] new alsa driver for ti omap chip
hi, I am trying to write an alsa driver for a tsc2101 codec on a arm based SOC. The control interface between the SOC and the tsc2101 codec is via SPI. And the data interface is a I2S interface. Can some one suggest a good starting point to start such a driver. does sound/drivers/dummy.c makes sense for such a driver ??? warm regards -kshitij --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
