Re: [Alsa-devel] driver cvscompile with k-2.2.24
At Mon, 22 Sep 2003 11:42:07 +0300, Andrei Boros wrote: Trying cvscompile on the cvs tree updated 30min ago : make[2]: Entering directory `/serve/install/alsa-cvs/alsa-driver/usb/us428' gcc -D__KERNEL__ -DMODULE=1 -I/serve/install/alsa-cvs/alsa-driver/include -I/us r/src/linux/include -O2 -mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall - Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -DKBUILD_BASENAME=usbus428 -c -o usbus428.o us bus428.c (snip) fixed now. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: SOLVED = RE: [Alsa-devel] Alsa 2.6 kernel
At Wed, 24 Sep 2003 14:24:29 -0700, Mark Knecht wrote: I see that in the Gentoo kernel tree (and maybe all 2.6 kernels) linux/drivers/sound has moved to linux/sound. the OSS drivers are located now on linux/sound/oss. the other sound directories correspond to ALSA's alsa-kernel tree (except for alsa-kernel/include - linux/include/sound, and alsa-kernel/Documentation - linux/Documentation/sound/alsa). Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] cvs alsa-lib compilation :
At Thu, 25 Sep 2003 06:46:22 +0300, Andrei Boros wrote: A followup on my last post : I remove the symlinks in alsa-lib/src/control (which are broken). make /bin/sh ../../libtool --mode=link gcc -O2 -Wall -W -pipe -g -o libcontrol.la cards.lo hcontrol.lo control.lo control_hw.lo control_shm.lo setup.lo control_symbols.lo rm -fr .libs/libcontrol.la .libs/libcontrol.* .libs/libcontrol.* (cd . ln -s cards.lo cards.lo) (cd . ln -s hcontrol.lo hcontrol.lo) (cd . ln -s control.lo control.lo) (cd . ln -s control_hw.lo control_hw.lo) (cd . ln -s control_shm.lo control_shm.lo) (cd . ln -s setup.lo setup.lo) (cd . ln -s control_symbols.lo control_symbols.lo) ar cru .libs/libcontrol.al cards.lo hcontrol.lo control.lo control_hw.lo control_shm.lo setup.lo control_symbols.lo ar: cards.lo: Too many levels of symbolic links try to run make clean ? it's definitely a problem of libtool (or the combination with other auto-tools). Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] alsa-utils cvscompile
At Thu, 25 Sep 2003 06:00:10 +0300, Andrei Boros wrote: Takashi Iwai wrote: hmm, check whether depcomp file at the top directory is empty. if so, try to remove depcomp. it must come from automake, but the combination of the old automake and the new libtool can be problematic. removed an empty depcomp and problem solved. Thanks. anyway, the best way would be to upgrade (or even downgrade) the all GNU auto-tools to the sane combination. i'm not sure which version combinations are correct, though. upgrading them to the latest version would be fine for ALSA, but it might not work on others occasionally. sigh. I don't know, I just upgraded severla weeks ago the compiler, gnu auto*, libtool, make to the versions required to compile glibc-2.2.5, so they are all pretty new. well... it's not so new nowadays :) on my system: % automake --version automake (GNU automake) 1.7.6 % autoconf --version autoconf (GNU Autoconf) 2.57 % libtool --version ltmain.sh (GNU libtool) 1.5 (1.1220.2.1 2003/04/14 22:48:00) IIRC, at least, the libtool 1.4.x is problematic for creating versioned symbols. (we have workarounds, but not perfect.) Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Opti92x-ad1848 won't take Opti924 card
At Tue, 23 Sep 2003 11:17:51 +0300, Andrei Boros wrote: Clemens Ladisch wrote: Andrei Boros wrote: options snd-opti-92x-ad1848 index=1 isapnp=1 id=Opti924 port=0x220 irq=5 dma1=0 fm_port=0x380 mpu_port=0x300 mpu_irq=7 You've specified all parameters manually, so you could try to disable ISA PnP (isapnp=0). And fm_port must be 0x388 (0x380 is the OPL4 port, which is detected automatically if you have an OPL4). I corrected it to 0x388. Doesn't work Completely commented the line. Doesn't work Changed to isapnp=0. Doesn't work. Again: the card is Opti924 in ISA slot. modprobe returns : /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or resource busy snd: Device or resource busy snd-isapnp module is not loaded automatically. this is already something wrong. it MUST be autoloaded. do you still get the dependecy error? i suspect either isapnp or pnp layer wasn't called / executed properly. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] usbus428.c.patch_1.3_1.4
Hi Takashi,
this makes it work again!
ciao,
Karsten
Index: alsa-driver/usb/us428/usbus428.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/us428/usbus428.c,v
retrieving revision 1.3
diff -u -r1.3 usbus428.c
--- alsa-driver/usb/us428/usbus428.c 24 Sep 2003 16:45:10 - 1.3
+++ alsa-driver/usb/us428/usbus428.c 25 Sep 2003 09:29:07 -
@@ -169,15 +169,12 @@
int j, send = us428ctls-p4outSent + 1;
if (send = N_us428_p4out_BUFS)
send = 0;
-while (us428ctls-p4out[send].type == eLT_Light send != us428ctls-p4outLast)
- if (++send = N_us428_p4out_BUFS)
- send = 0;
for (j = 0; j URBS_AsyncSeq; ++j)
if (0 == us428-AS04.urb[j]-status) {
us428_p4out_t *p4out = us428ctls-p4out + send; // FIXME if more then 1 p4out is new, 1 gets lost.
usb_fill_bulk_urb(us428-AS04.urb[j], us428-chip.dev,
usb_sndbulkpipe(us428-chip.dev, 0x04), p4out-vol,
- p4out-type == eLT_Light ? sizeof(us428_lights_t) : sizeof(usX2Y_volume_t),
+ p4out-type == eLT_Light ? sizeof(us428_lights_t) : 5,
snd_us428_Out04Int, us428);
#ifdef OLD_USB
us428-AS04.urb[j]-transfer_flags = USB_QUEUE_BULK;
@@ -225,7 +222,7 @@
for (dev = 0; dev SNDRV_CARDS; ++dev)
if (enable[dev] !snd_us428_card_used[dev])
- return NULL;
+ break;
if (dev = SNDRV_CARDS)
return NULL;
[Alsa-devel] Re: usbus428.c.patch_1.3_1.4
At Thu, 25 Sep 2003 11:42:43 +0200, Karsten Wiese wrote: Hi Takashi, this makes it work again! thanks, i'll apply it. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Opti92x-ad1848 won't take Opti924 card
On Wed, 24 Sep 2003, Andrei Boros wrote: Jaroslav Kysela wrote: Andrei Boros wrote: options snd-opti-92x-ad1848 index=1 isapnp=1 id=Opti924 port=0x220 irq=5 dma1=0 fm_port=0x380 mpu_port=0x300 mpu_irq=7 I corrected it to 0x388. Doesn't work snd-isapnp module is not loaded automatically. If I load it manually, I see the following in the log : kernel: isapnp: Card 'OPTi Audio 16' kernel: isapnp: 1 Plug Play card detected total Then modprobe snd-opti92x-ad1848 says : kernel: no OPTi 82C92x soundcard found Send us the contents of /proc/isapnp after 'modprobe snd-isapnp'. modprobe snd-isapnp --- Card 1 'OPT0924:OPTi Audio 16' PnP version 1.0 Logical device 0 'OPT:Pro Audio 16' This looks ok. It seems that you don't have compiled the ISA PnP support for the module or something is broken. Could you check, if the snd- module has references to pnp_* functions? (nm snd-opti92x-ad1848.o | grep pnp_) Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: SOLVED = RE: [Alsa-devel] Alsa 2.6 kernel
At Wed, 24 Sep 2003 14:24:29 -0700, Mark Knecht wrote: I see that in the Gentoo kernel tree (and maybe all 2.6 kernels) linux/drivers/sound has moved to linux/sound. the OSS drivers are located now on linux/sound/oss. the other sound directories correspond to ALSA's alsa-kernel tree (except for alsa-kernel/include - linux/include/sound, and alsa-kernel/Documentation - linux/Documentation/sound/alsa). Takashi Takashi-san, Thank you very much for the response. It is helpful. Would I be correct that if I had a 2.6 level kernel and wanted to use the newest Alsa from CVS, then I would: 1) Download CVS to my machine in it's own directory 2) Replace what is currently in linux/sound with the CVS source EXCEPT for the oss directory which I would leave alone. 3) Build the kernel with Alsa sound support and no OSS support 4) Use Alsa to do OSS emulation like I do today in modules.conf In linux/sound there are a few other files - Kconfig, etc. If these are not supplied by Alsa CVS, then I would leave them in linux/sound to perform whatever function they perform today. Does this sound about right? I may try it out one of these days. Thanks, Mark --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] tascam us-122 : invalid synch pipe
Hello, i'm unable to get a tascam us-122 usb audio/midi box working. This device is supported by ALSA us428 driver. Trying alsaplayer and MusE both return an error on setting the pcm hw params: ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Invalid argument The kernel log says: Sep 25 16:40:58 t10 vmunix: ALSA usbaudio.c:1108: 7:0:1 : invalid synch pipe I am using current (todays) ALSA cvs and linux 2.4.23pre4. What i'm doing wrong? Regards, Werner --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] tascam us-122 : invalid synch pipe
--- Werner Schweer [EMAIL PROTECTED] schrieb: Hello, i'm unable to get a tascam us-122 usb audio/midi box working. This device is supported by ALSA us428 driver. Trying alsaplayer and MusE both return an error on setting the pcm hw params: ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Invalid argument The kernel log says: Sep 25 16:40:58 t10 vmunix: ALSA usbaudio.c:1108: 7:0:1 : invalid synch pipe I am using current (todays) ALSA cvs and linux 2.4.23pre4. What i'm doing wrong? nothing, except snd-usb-us428 is not yet capable of handling the us122. You are shure it was loaded? Would wonder how that would happen. I'd need hands on an us122 to support it in snd-usb-us428. regards, Karsten __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: SOLVED = RE: [Alsa-devel] Alsa 2.6 kernel
At Thu, 25 Sep 2003 07:45:08 -0700, Mark Knecht wrote: At Wed, 24 Sep 2003 14:24:29 -0700, Mark Knecht wrote: I see that in the Gentoo kernel tree (and maybe all 2.6 kernels) linux/drivers/sound has moved to linux/sound. the OSS drivers are located now on linux/sound/oss. the other sound directories correspond to ALSA's alsa-kernel tree (except for alsa-kernel/include - linux/include/sound, and alsa-kernel/Documentation - linux/Documentation/sound/alsa). Takashi Takashi-san, Thank you very much for the response. It is helpful. Would I be correct that if I had a 2.6 level kernel and wanted to use the newest Alsa from CVS, then I would: 1) Download CVS to my machine in it's own directory 2) Replace what is currently in linux/sound with the CVS source EXCEPT for the oss directory which I would leave alone. 3) Build the kernel with Alsa sound support and no OSS support 4) Use Alsa to do OSS emulation like I do today in modules.conf In linux/sound there are a few other files - Kconfig, etc. If these are not supplied by Alsa CVS, then I would leave them in linux/sound to perform whatever function they perform today. Does this sound about right? I may try it out one of these days. yes. alsa-kernel tree includes the all files (including Kconfig) except for OSS driver codes under oss directory. please remember the difference of alsa-kernel and alsa-driver trees. for 2.6.x kernel, only alsa-kernel tree is used. also, you can build on alsa-drivers as well as 2.4.x (i fixed this yesterday). but in this case, note that the kernel configuration will override the local configuration of alsa-driver (provided by configure script). for example, if you turn off the ALSA support on 2.6.x kernel config, you cannot build on alsa-drivers tree properly at all. this causes often problems when CONFIG_SND_DEBUG mismatches between kernel and alsa-driver trees. also, when the kernel is compiled with MODVERSION, you'll have many compile warnings on alsa-driver tree, due to redefinition of symbols. but you can ignore them in general. ciao, Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] tascam us-122 : invalid synch pipe
At Thu, 25 Sep 2003 18:06:19 +0200, Werner Schweer wrote: Hello, i'm unable to get a tascam us-122 usb audio/midi box working. This device is supported by ALSA us428 driver. it seems you're using snd-usb-audio driver instead of snd-usb-us428 driver. the error above should happen only on snd-usb-audio. Trying alsaplayer and MusE both return an error on setting the pcm hw params: ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Invalid argument The kernel log says: Sep 25 16:40:58 t10 vmunix: ALSA usbaudio.c:1108: 7:0:1 : invalid synch pipe I am using current (todays) ALSA cvs and linux 2.4.23pre4. What i'm doing wrong? please check whether you have usbaudio.c cvs rev.1.65, which i fixed yesterday. there is a delay between the main cvs and anon.cvs... Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: SOLVED = RE: [Alsa-devel] Alsa 2.6 kernel
Takashi-san, Thanks very much. It's making more sense. A couple of questions are embedded below. I think you only need to answer then if you think I'm confused which is a definite possibility. ;-) Does this sound about right? I may try it out one of these days. yes. alsa-kernel tree includes the all files (including Kconfig) except for OSS driver codes under oss directory. Oops! I thought I was clear up to this, so I want to double, double check. When you say 'OSS driver codes' here, you are speaking of the real OSS that is not part of Alsa, correct? I have not ever built (TTBOMK) real OSS Sound support, and don't want to do so now. I do want 'OSS Emulation' that is offered by Alsa. I get this from the Alsa code and not from anything in the OSS directory, correct? The right answer (in my mind) is that I should be able to delete the oss directory in linux/sound, not enable OSS Sound support when I configure the kernel, and still get OSS emulation support from Alsa. I hope I have not been incorrect about this. please remember the difference of alsa-kernel and alsa-driver trees. for 2.6.x kernel, only alsa-kernel tree is used. Right! The 'drivers' portion of the 2.4 series kernel is now located in /linux/sound. I see my hdsp.c driver under pci. If I needed to do an HDSP 9652 update, I would take Thomas's work and place it in the linux/sound/pci/rme9652 directory and rebuild the kernel and kernel modules. also, you can build on alsa-drivers as well as 2.4.x (i fixed this yesterday). but in this case, note that the kernel configuration will override the local configuration of alsa-driver (provided by configure script). for example, if you turn off the ALSA support on 2.6.x kernel config, you cannot build on alsa-drivers tree properly at all. this causes often problems when CONFIG_SND_DEBUG mismatches between kernel and alsa-driver trees. Certainly. Of course, I'm not a programmer, but I cannot understand why and end-user like me would want to turn off Alsa support in the kernel but still build a driver. I'm trying to be a good citizen. Just give me Alsa and my driver and I'll be happy! ;-) also, when the kernel is compiled with MODVERSION, you'll have many compile warnings on alsa-driver tree, due to redefinition of symbols. but you can ignore them in general. Way beyond me, I think, but thanks for the info. Maybe it will sink in later. Cheers, Mark --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] tascam us-122 : invalid synch pipe
On Thursday 25 September 2003 19:15, Takashi Iwai wrote: At Thu, 25 Sep 2003 18:06:19 +0200, Werner Schweer wrote: Hello, i'm unable to get a tascam us-122 usb audio/midi box working. This device is supported by ALSA us428 driver. it seems you're using snd-usb-audio driver instead of snd-usb-us428 driver. the error above should happen only on snd-usb-audio. you are right, i found the message in snd-usb-audio.c Trying alsaplayer and MusE both return an error on setting the pcm hw params: ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Invalid argument The kernel log says: Sep 25 16:40:58 t10 vmunix: ALSA usbaudio.c:1108: 7:0:1 : invalid synch pipe I am using current (todays) ALSA cvs and linux 2.4.23pre4. What i'm doing wrong? please check whether you have usbaudio.c cvs rev.1.65, which i fixed yesterday. there is a delay between the main cvs and anon.cvs... yes, i'm using rev 1.65 from cvs. Meanwhile i checked the us122 alsa patch from martin-langer (http://www.langerland.de/us122/driver.html) with no effect. Regards, Werner --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] tascam us-122 : invalid synch pipe
On Thursday 25 September 2003 19:12, karsten wiese wrote: --- Werner Schweer [EMAIL PROTECTED] schrieb: Hello, i'm unable to get a tascam us-122 usb audio/midi box working. This device is supported by ALSA us428 driver. Trying alsaplayer and MusE both return an error on setting the pcm hw params: ALSA lib pcm_hw.c:324:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Invalid argument The kernel log says: Sep 25 16:40:58 t10 vmunix: ALSA usbaudio.c:1108: 7:0:1 : invalid synch pipe I am using current (todays) ALSA cvs and linux 2.4.23pre4. What i'm doing wrong? nothing, except snd-usb-us428 is not yet capable of handling the us122. You are shure it was loaded? Would wonder how that would happen. I'd need hands on an us122 to support it in snd-usb-us428. ok, i saw the us122 string in the snd-usb-us428 source and assumed it would handle the device. snd-usb-us428 was loaded but the above error message was produced by snd-usb-audio. Regards, Werner --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
