Re: [Alsa-devel] Need to know SBLive Chip difference
From: p z [EMAIL PROTECTED]
Reply-To: p z [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] Need to know SBLive Chip difference
Date: Tue, 30 Mar 2004 08:37:35 +0200
Right now I compared changes between alsa 1.0.3b and 1.0.4rc1.
Diffrence is that 1.0.4rc1 contains support for AC97 codec used in
2003 SB Live (Sigmatel STAC9758) and I think, that make it not to
working.
Try to change line in alsa-driver/alsa-kernel/pci/ac97/ac97_codec.c
{ 0x83847658, 0x, STAC9758/59, patch_sigmatel_stac9758,
NULL },
to
{ 0x83847658, 0x, STAC9758/59, NULL,NULL },
Peter Zubaj
== REKLAMA
Java Desktop System predstavuje prvu pouzitelnu alternativu voci Windows za
poslednych 15 rokov, pretoze prinasa zákaznikom bezpecne a doveryhodne
desktopove riesenie za zlomok ceny Windows.
Viac informacii najdete na : http://www.somi.sk/sun/java_desktop.php
===
Ya thanks I get back the Front L/R and Center/Subwoofer output now.
Hi,
Personaly I don't think there is diffrence in emu10k1 between 2003 and
2002. Diffrence is in AC97 codec. In 2002 is two channel. In 2003 is six
channel. I looked for datasheet for this AC97 codec, but it is not public
available. I think, that only some initialization is needed.
Could you try OSS driver if it works ???
Peter Zubaj
Trying oss thing to see if can get the Rear L/R. Btw, how could I get the
AC97 spec for this new codec, by subscription and pay some fee to some
organization? I wish I could help.
_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
I don't mean alsa-oss-emulation, I mean oss driver from opensource.creative.com or linux kernel. If it works, than something is wrong with alsa (I think it will not work). In SB Live up to 2002 was used AC97 codec for front and center/lfe and another dac for rear channels. I think, that in SB Live 2003 creative started using 6 channel AC97 codec and rear channel are using this AC97 codec too. I thing, that only some initialization is needed to get rear channels work (option 1) or rear channels are connected on diffrent output from emu10k1 and this needs to be found (option 2). Peter Zubaj == REKLAMA Spolocnost SUN Microsystems uviedla na trh novy server Sun Fire V20z zalozeny procesoroch AMD Opteron. Viac informacii najdete na : http://www.somi.sk/sun/v20z.php === --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Karsten, please try to enable audio out with us428control -v2 -D hw:1 like this: - toggle INPUT MONITOR until us428control says ...Light is 1 Yes, it does say ... Light is 1, but NO light on the LED. - then move Fader3 to max and play some audio. This is just a guess assuming audio out is mapped on us224 internal mixer 2, input monitor channel 1 is mapped on us224 internal mixer 0 and input monitor channel 2 is mapped on us224 internal mixer 1. Nothing is heard. - Please also try your guitar on both inputs: move faders 1 2 to see if sound is routed to the outputs. Again, nothing seems to be routed. No signal appears on output. Have tryied on both guitar inputs (A and B), with several combinations and fader positions, but can hear a thing. We have to tweak us428control to add real us224 support. I guess that will be really necessary to have a proper us224control :) Above is just to verify that the current us428 internal mixer mechanics is usable for the us224. It seems that it is not quite straightforward, isn't it? Is there any other US-224 user out there to at least confirm all this? It surely ain't nice this feeling of lonelyness ;) but I will prevail =:O Concerning us224's Lights I'm currently left in the dark So do the LEDs ;) For us428 I found that a 7Byte long USB-Message on pipe 4 is a Lights set command, while a 5Byte long is an internal mixer set command. You could tweak us428control to toggle the 0'th light instead of the 25'th light, which is InputMonitor Light on us428. the 0th light is Select Channel 1 on the us428. Exchange Cus428State.cc Line 118 , 119 Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select; Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute; for Light[0].Value = 0x55; Light[2].Value = 0xAA; to check light mechanics. I'll try this tonight, rest assured. If there's still no lights, some usb snooping on windoz might help. I've some specially tuned stuff here which I could send you then. That's of course a very good idea. Please do so ASAP. I'll be very pleased to follow your instructions and get a thorough profile on this. My laptop has a working winxp partition installed and the US-224 (audio mixer leds) works there as designed, but that's hardly a surprise for anyone :) Cheers, -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
The way I tested that channels is using alsa-lib/test/pcm -c6 -v , this should be ok rite? Anyway it can produce 440Hz sound, namely tone A on all six channels when I am using SBLive 2001, 2002 and Audigy 2001. I think I don't understand how the module snd-oss-mixer / snd-oss-pcm will help; I compile and make install alsa-oss-1.0.4rc1.tar.bz2 without problem. I used the aumix and alsamixer, but I could only get Front L/R and Centre/Subwoofer analog channel output after the suggested changes make into alsa-kernel/pci/ac97/ac97_codec.c . Please advice. _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
ok I try the ftp://www.se.opensound.com/pub/oss/linux/oss398d-linux-v2x.tar.gz now. _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
I don't mean this, this is comercial binary only driver (You can try). This http://prdownloads.sourceforge.net/emu10k1/emu10k1-v0.20a.tar.bz2? download or recompile kernel with OSS/free drivers enabled. Peter Zubaj http://www.pobox.sk/ - spolahliva a bezpecna prevadzka --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
Trying to recompile kernel to get rid of something which gives a line in /proc/device as: 14 sound since the oss installer refuse to install.. Checking for any previously installed sound drivers... It looks like the sound driver is linked in the kernel you are currently executing. You should configure recompile the kernel without the built in sound driver and to reboot before trying to install OSS/Linux again Error: OSS cannot be installed because there is another sound driver loaded. Driver 'sound' has registered the sound device (character major 14) for itself. You seem to have OSS/Free statically linked into kernel. You need to reconfigure and reinstall the kernel with sound support disabled. will try my best. Just FYI. The SIGMATEL codec on SBLive 2003 is: SIGMATEL STAC9758T CB1U004 0318 together with emu10k1 chip as: EMU10K1-JFF (C) CREATIVE TECH '97 1G24D02ELQ _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
D2CB0:01C4163F] I don't mean this, this is comercial binary only driver (You can try). This http://prdownloads.sourceforge.net/emu10k1/emu10k1-v0.20a.tar.bz2? download or recompile kernel with OSS/free drivers enabled. Peter Zubaj Ok..but is there any test program which uses this to output 6 channels of sine wave, like alsa-lib/test/pcm does? _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Need to know SBLive Chip difference
FYI too, the Audigy 2001 I have been talking about is using the following chips: SIGMATEL STAC9721T LC5A01E 0201 CREATIVE Audigy(tm) CA0100-IDF (C) CREATIVE TECH'01 2BA70KW I can have 6 channels output with this card. I think if creative uses the SIGMATEL chip on that SBLive 2003 (say, Audigy 2003) then it will create same problem later :) _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket
What needs to happen is that the card driver author needs to investigate what is going on, and, if it seems related to the core PCMCIA core or the socket driver, we need to get involved. he pointed out that it's probably a kernel problem ... we don't want you to solve problems of the alsa driver, but we suspect there is a problem with the cardbus bridge... basics: 1.) the card is a combination of 2 devices: a interface device, either a pci or a cardbus card, and a dsp device, either digital or analog audio ... no problems have ever been reported about the pci interface, so it's likely to be a problem with the cardbus interface ... although i have to admit, that there are only 3 reported systems that have the problems, we experience ... but these systems are completely different ones (p4 / amd64, different cardbus bridges) 2.) the dsp device has an internal matrix mixer, that's independant from the computer (this audio data isn't sent to the computer at all) ... in fact it's possible to set the matrix mixer and unplug the dsp device from the computer ... there are three problems, that show the situation: 3.) if we start an audio application that produces interrupts on the hdsp device, some of the audio data that's been transfered to the computer will be copied or mapped to the buffer of the audio data that's been transfered from the computer to the corresponding output. this could either happen - inside the device itself (i doubt that, since the same driver, the same firmware, the same devices are working without and problems on other linux machines or with windows on the same machine) - inside the cardbus bridge - inside the kernel 4.) if we start the audio playback, the audio playback seems to be distorted: one block of samples will be followed by one block of samples of 0 (zero) ... note that these block are not the blocks of data, that are sent to the hdsp during one interrupt. it's usually 32 samples of sound followed by 32 samples of silence, the driver sends blocks of 64 to 8192 during one interrupt depending on user settings... iirc one sample is 24 bit on the other hand the blocks of silence aren't missing, but the alsa layer will adapt, so that it takes twice as long as it should to play back a soundfile (i'm not sure if it's because of the alsa soundfile player or of the driver) 5.) the reason why we (or at least i) think, that it's a problem with the cardbus interface, is because of jack's output ... jack is both an audio connection interface for different softwares and a very good alsa implementation... using jack as super user in realtime mode, it complains about latency problems: delay of xxx usecs exceeds estimated spare time of yyy; restart ... at the default sample rate of 48000 xxx only about 0.06 % bigger than yyy ... on the other hand, i only get this error on sample rates of more than 32000 ... although the sound at 32000 is distorted, as well... other thoughts i had: 6.) the distortion isn't affected by the block size / the number of interrupts ... it is affected by the samplerate ... that's why i think, there are always 32 samples (768 bit) followed by 32 samples of silence (768 bit zero ???) 7.) the problems occured on different cardbus bridges: ENE C1410 (ico / mandrake) o2micro6933 (myself / gentoo) Texas Instruments PCI1250 (timothy / red hat) i don't know what's the reason for the problems, the latency or the mapping problem, or if there is something else that results this problem ... but since it's a software and not a hardware issue (works fine with windows), i'd like to get into it, and at least try to solve it ... but since i'm neiter a kernel hacker nor i have any idea about the hardware internals, i'd need some help from some people, who are able to help me... i don't want some people to solve my problems for me, but i'd appreciate any help of people, who know what's going on inside the computer... cheers ... Tim mailto:[EMAIL PROTECTED] ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes Awww! Jack Kerouac --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Am Dienstag 30 März 2004 10:14 schrieb Rui Nuno Capela:
If there's still no lights, some usb snooping on windoz might help.
I've some specially tuned stuff here which I could send you then.
That's of course a very good idea. Please do so ASAP.
I'll be very pleased to follow your instructions and get a thorough
profile on this. My laptop has a working winxp partition installed and the
US-224 (audio mixer leds) works there as designed, but that's hardly a
surprise for anyone :)
The real stuff is too big for the list, I'll send it to you seperatly.
It is a modified (changed filter-driver, added ListeningPipe app) usb snooper.
modified so I get (filtered) output consisting of sent/received data in a c
header-file.
It works for me on win2k/vc6 only; haven't tried it on xp yet.
Quick Dirty Instructions:
Install the filter driver
filter/release2k/usbsnoop.sys
like in standard usb snoopy of that version. (Detailed Instructions somewhere
@ sf.net if not in the zip)
enable filter -driver with standard ui app. see attached jpg.
Switch On us224.
Start ListeningPipe/Release/ListeningPipe.exe.
It will (hopefully) create a BIG file fw.h containing everything it snoops
dump first occurances of messages to stdout.
Pipe stdout to a file to capture infos, while you do something with the us224.
to get best results, switch off us224 to end ListeningPipe.exesomefile.
you can also control-c, but then somefile is not complete. some bugs there
still.
take f1up_m1.h as an example :
preconditions:
us428 switch on, INPUT MONITOR Light activ. Other LEDs OFF.
Fader 1 @ Minimum.
Started ListeningPipe.exe in a shell like this:
ListeningPipef1up_m1.h
Moved Fader 1 up (1/5 Full scale).
Switched Mute 1 ON.
Switched off us428. ListeningPipe finished ok.
Cheers,
Karsten
attachment: ui.jpg//Pipe Connected!
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0xE
{ 0x19, 0x08, 0x1A, 0x00, 0x1B, 0x00, 0x1C, 0x02, 0x1D, 0x01, 0x1E, 0x00, 0x1F, 0x00,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x03, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x09, 0x00, 0x0A,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x05, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x13, 0x00, 0x14,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x07, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x1D, 0x00, 0x1E,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x09, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x26, 0x00, 0x28,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x0B, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x30, 0x00, 0x32,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x0D, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x3A, 0x00, 0x3C,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x84
// NEW [EMAIL PROTECTED], len=0x15
{ 0x0F, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00,
0x00, 0x00, 0x00, 0x01, 0x01,
};
// _URB_HEADER 09 URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER
// pipe=0x04
// NEW [EMAIL PROTECTED], len=0x5
{ 0x00, 0x00, 0x43, 0x00, 0x46,
};
// _URB_HEADER 09
Re: [Alsa-devel] Need to know SBLive Chip difference
guan yim wrote: FYI too, the Audigy 2001 I have been talking about is using the following chips: SIGMATEL STAC9721T LC5A01E 0201 CREATIVE Audigy(tm) CA0100-IDF (C) CREATIVE TECH'01 2BA70KW I can have 6 channels output with this card. I think if creative uses the SIGMATEL chip on that SBLive 2003 (say, Audigy 2003) then it will create same problem later :) Do any output channels work. Just try stereo for front and rear and center/lfe Also, what is the output from lspci -n |grep 0401 Cheers James --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Hi Karsten, Already grabbed and installed SnoopyPro-0.22 from http://sourceforge.net/projects/usbsnoop . Guess it's what you mentioned. See on attachment a screenshot right after sniffer installation. If that's right, you probably don't need to send everything, just the ListeningPipe utility. OK? Cheers, -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] attachment: USB224_Snoop1.png
Re: [Alsa-devel] 1.0.4rc1 release
Jaroslav Kysela wrote: 1.0.4rc1 packages are out. Please, report compilation problems. On a 2.2.19 kernel: depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-* depmod: synchronize_irq depmod: tqueue_lock depmod: waitqueue_lock depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-au88?0.o depmod: snd_pci_compat_disable_device depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd.o depmod: kernel_flag How long do we want to support 2.2.x? Regards, Clemens --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] 1.0.4rc1 release
On Tue, 30 Mar 2004, Clemens Ladisch wrote: Jaroslav Kysela wrote: 1.0.4rc1 packages are out. Please, report compilation problems. On a 2.2.19 kernel: depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-* depmod: synchronize_irq depmod: tqueue_lock depmod: waitqueue_lock Missing inclusion of some header files? depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-au88?0.o depmod: snd_pci_compat_disable_device Fixed. depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd.o depmod: kernel_flag What's this? How long do we want to support 2.2.x? At least for 1.0. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] period size
Hi I am trying to write a pcm app which receives sound over the network and outputs it through the speakers. The network protocol is udp. From what I can tell, each packet is a single period with interleaved channels. My problem is that the period size appears to be below the minimum that my hardware will go. For example: rate: 48000 Hz channels: 2 packet size:512 bytes sample size:16 bit ok so far... (correct me if I'm wrong) period size = (packet size * 8) / (channels * sample size) = (512 * 8) / (16 * 2) = 128 buffer size = (whatever i like...? latency/network stability...?) When I try to set the period size exactly I get an error. If I set the period size near I get 192. How do I make this work? Should I reconfigure the network sound source? Do I put the packets together into larger periods? Can alsa do this for me? cheers Tim --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] intel8x0.c
Hi all, I have an intel810 onboard soundcard.I am using the alsa driver with a VoIP session. The intel8x0.c file has a minimum period byte size of 32 bytes with the minimum no. of periods being 1.The min and max rate is set to 48k. How can I find out what actual(runtime) size period the alsa driver is dealing with? Does it use the minimum size as the period size? Brian. ___ WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe Awards www.yahoo.co.uk/internetcafes --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] period size
On Tue, 30 Mar 2004, Tim Hollingsworth wrote: Hi I am trying to write a pcm app which receives sound over the network and outputs it through the speakers. The network protocol is udp. From what I can tell, each packet is a single period with interleaved channels. My problem is that the period size appears to be below the minimum that my hardware will go. For example: rate: 48000 Hz channels: 2 packet size: 512 bytes sample size: 16 bit ok so far... (correct me if I'm wrong) period size = (packet size * 8) / (channels * sample size) = (512 * 8) / (16 * 2) = 128 buffer size = (whatever i like...? latency/network stability...?) When I try to set the period size exactly I get an error. If I set the period size near I get 192. How do I make this work? Should I Your hardware (probably emu10k1 or audigy) does not support this period size for capture. reconfigure the network sound source? Do I put the packets together into larger periods? Can alsa do this for me? You can read/write any size. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] intel8x0.c
On Tue, 30 Mar 2004, Brian Furey wrote: Hi all, I have an intel810 onboard soundcard.I am using the alsa driver with a VoIP session. The intel8x0.c file has a minimum period byte size of 32 bytes with the minimum no. of periods being 1.The min and max rate is set to 48k. How can I find out what actual(runtime) size period the alsa driver is dealing with? After the snd_pcm_hw_params() call, the given hardware parameter container will have the chosen period size or snd_pcm_hw_params_current() creates the current hw_params container. Then use snd_pcm_hw_params_get_period_size() or snd_pcm_hw_params_get_period_time(). Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] intel8x0.c
Right Jaroslav, that means i would modify intel8x0.c to include a call to snd_pcm_hw_params_get_period_size() or snd_pcm_hw_params_get_period_time() in the appropriate place. Write the values returned say to a text file. Recompile the ALsa driver and re-insert it into the kernel.Start my application and check contents of text file. Am I right in saying this? Thanks in advance, Brian. --- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Tue, 30 Mar 2004, Brian Furey wrote: Hi all, I have an intel810 onboard soundcard.I am using the alsa driver with a VoIP session. The intel8x0.c file has a minimum period byte size of 32 bytes with the minimum no. of periods being 1.The min and max rate is set to 48k. How can I find out what actual(runtime) size period the alsa driver is dealing with? After the snd_pcm_hw_params() call, the given hardware parameter container will have the chosen period size or snd_pcm_hw_params_current() creates the current hw_params container. Then use snd_pcm_hw_params_get_period_size() or snd_pcm_hw_params_get_period_time(). Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs ___ WIN FREE WORLDWIDE FLIGHTS - nominate a cafe in the Yahoo! Mail Internet Cafe Awards www.yahoo.co.uk/internetcafes --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] intel8x0.c
On Tue, 30 Mar 2004, Brian Furey wrote: Right Jaroslav, that means i would modify intel8x0.c to include a call to snd_pcm_hw_params_get_period_size() or snd_pcm_hw_params_get_period_time() in the appropriate place. Write the values returned say to a text file. Recompile the ALsa driver and re-insert it into the kernel.Start my application and check contents of text file. Am I right in saying this? I'm talking about application not the driver. Why you need to modify driver? Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket
hi russel The majority of PCMCIA is the same between the two kernels. There have been some cleanups and changes to the way card events (insertions and removals) occur, and some setup changes to the cardbus bridge to turn on some extra features. However, if you're saying that 2.4 and 2.6 behave the same way, then logically it isn't something that any of these changes have caused. i tried to use the pcmcia-cs driver again (2.4.24-ck1 ... they didn't work with the hdsp, either (afaik, the pcmcia-cs driver never worked with the hdsp, but i'm not sure about that) the dmesg output was: PCI: Found IRQ 5 for device 02:00.0 PCI: Sharing IRQ 5 with 01:00.0 PCI: Found IRQ 11 for device 02:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 PCI: Sharing IRQ 11 with 00:1f.6 O2Micro OZ6933 rev 01 PCI-to-CardBus at slot 02:00, mem 0x2000 host opts [0]: [pci/way] [pci irq 5] [lat 168/176] [bus 3/6] host opts [1]: [pci/way] [pci irq 11] [lat 168/176] [bus 7/10] ISA irqs (default) = 3,4,7,9,10 PCI status changes cs: cb_alloc(bus 7): vendor 0x10ee, device 0x3fc5 cs: cb_free(bus 7) cs: cb_alloc(bus 7): vendor 0x10ee, device 0x3fc5 PCI: No IRQ known for interrupt pin A of device . ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:5031: unable to grab memory region 0x0-0x1bff RME Hammerfall-DSP: no cards found i have no idea of the differences between the cardbus drivers of the kernel and of the pcmcia-cs project ... anyway, the hdsp is working on a certain area of memory, that the pcmcia-cs driver can't grab the kernel driver can ... i disabled acpi and apic and used pci=biosirq as kernel flag maybe this can give you a hint ... anyway, i hope thomas can comment on that... cheers and thanks for your help... Tim mailto:[EMAIL PROTECTED] ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes Awww! Jack Kerouac --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket
-Original Message- From: Russell King [mailto:[EMAIL PROTECTED] On Behalf Of Russell King Sent: Tuesday, March 30, 2004 3:01 AM To: Ivica Ico Bukvic Cc: 'A list for linux audio users'; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [linux-audio-user] snd-hdsp+cardbus=distortion -- the sagacontinues (cardbus driver=culprit?) UPDATE: 99.9% sure it is the cardbus driver yenta_socket On Tue, Mar 30, 2004 at 12:52:11AM -0500, Ivica Ico Bukvic wrote: 6) Pester alsa-dev, lau, and kernel/pcmcia people to death begging for help :-) IN-PROGRESS :-) What needs to happen is that the card driver author needs to investigate what is going on, and, if it seems related to the core PCMCIA core or the socket driver, we need to get involved. IOW, linux-pcmcia people don't debug card drivers. To add to what Tim mentioned, I think that the driver is fine as it does work on select notebooks and desktops (the card can be plugged into either PCI card or PCMCIA cardbus). Yet, in these select instances it does not work even though neither the cardbus driver nor the actual card driver do not report any particular problems. Hence the only logical explanation is that there is something wrong with the pcmcia controller driver. This card does tax the throughput of the cardbus like no other card I can think of, hence the problem may be more widespread, but exhibits itself just in this case where the cardbus is being pushed to its limits. Yet, the hardware is not the issue when the same notebook/soundcard combo works flawlessly in WinXP. Hope this helps! Ico --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] intel8x0.c
Brian Furey wrote: Hi all, I have an intel810 onboard soundcard.I am using the alsa driver with a VoIP session. The intel8x0.c file has a minimum period byte size of 32 bytes with the minimum no. of periods being 1.The min and max rate is set to 48k. How can I find out what actual(runtime) size period the alsa driver is dealing with? Does it use the minimum size as the period size? Brian. Brian, I am working on a VoIP setup. I am updating the asterisk alsa console driver so that it actually works! The current driver is stuck round about alsa api 0.5.x The period size that the sound card is actually using does not really matter, if just effects latency. The bigger the period size, the higher the latency. Just set the period size to the smallest the sound card can do, and then just read and write to it. I found that PLAYBACK and CAPTURE directions can have different period sizes, so it is better to open separate handles for playback and capture. In the config setup, you set the buffer and period sizes, and before you set them, you can retrieve the current min/max period and buffer sizes. For playback, it is best to have a certain minimum buffer being full most of the time, due to network jitter, and this buffer can act as the jitter buffer. The actual size of this is probably best found out from trial and error (I have not finished testing this bit yet). For capture, just poll for input, and then read whatever is in the capture buffer and transmit it. You can experiment with different methods of early buffer reads, but again, I have not finished testing with that, so I can't give you any definite answers. Another thing to test with could be sampling and playback at 48k. Most sound cards work at 48k, and this would reduce the period_time. (period_size stays the same, but as one is using a higher rate, the period_time decreases, and thus latency.) The problems with that is that most VoIP is at 8k, so some resampling is required. Cheers James --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Am Dienstag 30 Mrz 2004 14:29 schrieb Rui Nuno Capela: Hi Karsten, Already grabbed and installed SnoopyPro-0.22 from http://sourceforge.net/projects/usbsnoop . Guess it's what you mentioned. See on attachment a screenshot right after sniffer installation. If that's right, you probably don't need to send everything, just the ListeningPipe utility. OK? Hi Rui, screenshot looks ok. I don't know SnoopyPro-0.22. I think I took an older version from somewhere on the web modified it heavyly. maybe SnoopyPro-0.22 can also do what my ListeningPipe app can: Dump any different telegram only the first time it is being transmitted. the usb is in constant usage, so if you need to find a special teloegram that onlyx occurs if you do something, it can be quit hard work to find out the exact telegram. If you want ListeningPipe, you have to also use the filter-driver that came with the zip file. At least so I think... Cheers, Karsten --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
screenshot looks ok. I don't know SnoopyPro-0.22. I just picked it up from sf.net , as you suggested. I think I took an older version from somewhere on the web modified it heavyly. maybe SnoopyPro-0.22 can also do what my ListeningPipe app can: Dump any different telegram only the first time it is being transmitted. the usb is in constant usage, so if you need to find a special teloegram that onlyx occurs if you do something, it can be quit hard work to find out the exact telegram. Hmmm. I think we better stick with your custom binaries and put aside that SnoopyPro thing. AFAICT there's no filtering feature in it. We better use the very same tools, otherwise things get weird, and no one gets the blame ;) If you want ListeningPipe, you have to also use the filter-driver that came with the zip file. At least so I think... Of course I do. Please apologize me, but I'm missing the zip file you're mentioning. Have you sent it already? Hope to. Cheers. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Am Dienstag 30 März 2004 21:32 schrieb Rui Nuno Capela: screenshot looks ok. I don't know SnoopyPro-0.22. I just picked it up from sf.net , as you suggested. I think I took an older version from somewhere on the web modified it heavyly. maybe SnoopyPro-0.22 can also do what my ListeningPipe app can: Dump any different telegram only the first time it is being transmitted. the usb is in constant usage, so if you need to find a special teloegram that onlyx occurs if you do something, it can be quit hard work to find out the exact telegram. Hmmm. I think we better stick with your custom binaries and put aside that SnoopyPro thing. AFAICT there's no filtering feature in it. We better use the very same tools, otherwise things get weird, and no one gets the blame ;) If you want ListeningPipe, you have to also use the filter-driver that came with the zip file. At least so I think... Of course I do. Please apologize me, but I'm missing the zip file you're mentioning. Have you sent it already? i sent it 7 hours ago and now again. I'd suggest you use my tool if it fits winxp USB 2 (I mean the latest high speed USB which your machine is equiped with?) which i don't know as i only used it with win2k and the slower 10MBit/s USB. I mean use what fits best ;-) Just checked: The Mail with the zip is in my inbox again (CCed me), so it should be in yours too soon: Rui Nuno Capela [EMAIL PROTECTED] It is 351 kBytes big, so i can't send it to alsa-devel list. You have it? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Re: [Alsa-user] alsa-driver-1.0.4rc1 missing snd-usb-usx2y ?
the snd-usb-usx2y module. AFAICT it's not being included by ./configure --with-cards option, nor it gets built when one sets --with-cards=all. It is fixed in CVS now. Thanks. Checked out today's alsa-driver-1.0.4rc2 where the missed snd-usb-usx2y module gets built now. However, I couldn't get it to load, dmesg gives: snd_usb_usx2y: Unknown symbol snd_pcm_dma_flags All other alsa packages are up to 1.0.4rc1 here. Bye. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Tascam US-224 support: MIDI OK, Audio KO?
Karsten, Concerning us224's Lights I'm currently left in the dark For us428 I found that a 7Byte long USB-Message on pipe 4 is a Lights set command, while a 5Byte long is an internal mixer set command. You could tweak us428control to toggle the 0'th light instead of the 25'th light, which is InputMonitor Light on us428. the 0th light is Select Channel 1 on the us428. Exchange Cus428State.cc Line 118 , 119 Light[0].Value = StateInputMonitor() ? SelectInputMonitor : Select; Light[2].Value = StateInputMonitor() ? MuteInputMonitor : Mute; for Light[0].Value = 0x55; Light[2].Value = 0xAA; to check light mechanics. Made this tweak, and nothing changed. LEDs remain dark. If there's still no lights, some usb snooping on windoz might help. I've some specially tuned stuff here which I could send you then. Let's go deep :) -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED] --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] 1.0.4rc from cvs-head: snd-usb-usx2y still needs snd-hwdep....
..., which is not built. this is for kernel 2.4. /etc/asound/driver_args: --with-cards=via82xx,msnd-pinnacle,usb-audio,usb-usx2y,es1968 --with-kernel=/usr/src/linux-2.4 --with-debug=full --with-sequencer=yes regards, Karsten --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] buffer producer/consumer sync
hi, I was just curious to know about by when will we be having a proper reference driver for ARM . We are ready to help out from here if there are any issues. warm regards -kshitij -Original Message- From: Russell King [mailto:[EMAIL PROTECTED] Behalf Of Russell King Sent: Tuesday, March 09, 2004 5:17 PM To: Gupta, Kshitij Cc: Jaroslav Kysela; [EMAIL PROTECTED] Subject: Re: [Alsa-devel] buffer producer/consumer sync On Tue, Mar 09, 2004 at 05:03:37PM +0530, Gupta, Kshitij wrote: I was referring to a ARM implementation in the ALSA tree for our ALSA driver development on OMAP 1610 (ARM 926) sound\arm\sa11xx-uda1341.c. Just wanted to know if sa11xx-uda1341.c is also affected by this problem. sa11xx-uda1341 isn't a good driver to look at - it's very specific to the iPAQ as it stands. I've been working on a properly modularised driver which separates out the PCM DMA engine from the rest of the code, which in turn makes it a lot easier to add support for different platforms. IOW, I've done the job properly. However, just as the iPAQ people (didn't) work with the rest of the ARM community when they created their supposed generic sa11xx-uda1341 implementation, the rest of the ARM community didn't work with them when creating our driver. And now various people are calling for sa11xx-uda1341 to be deleted once my driver is merged. It's good when communities fragment, isn't it? 8( However, the problem I've been describing is a problem with the core ALSA implementation and affects all hardware drivers on ARM, whether they be PCI, ISA or ARM specific. -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: compilation problem 3.4.0 gcc toolchain / armv6 / 2.6.0-rmk1 kernel
forgot to paste the error messeges sound/core/oss/pcm_plugin.c:34: internal compiler error: in loc_descriptor_from_tree, at dwarf2out.c:8800 Please submit a full bug report, with preprocessed source if appropriate. Send email to [EMAIL PROTECTED] for instructions. make[3]: *** [sound/core/oss/pcm_plugin.o] Error 1 make[2]: *** [sound/core/oss] Error 2 make[1]: *** [sound/core] Error 2 make: *** [sound] Error 2 -Original Message- From: Gupta, Kshitij Sent: Wednesday, March 31, 2004 12:13 PM To: [EMAIL PROTECTED] Subject: compilation problem 3.4.0 gcc toolchain / armv6 / 2.6.0-rmk1 kernel hi, I am getting errors while compiling 2.6.0-rmk1 kernel with 3.4.0 arm gcc tool chain, for armv6 architecture. Has anyone tried this before, or if anyone can suggest me a toolchain which can compile armv6 + ALSA. regards -kshitij --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] 1.0.4rc from cvs-head: snd-usb-usx2y still needs snd-hwdep....
On Wed, 31 Mar 2004, Karsten Wiese wrote: ..., which is not built. this is for kernel 2.4. /etc/asound/driver_args: --with-cards=via82xx,msnd-pinnacle,usb-audio,usb-usx2y,es1968 --with-kernel=/usr/src/linux-2.4 --with-debug=full --with-sequencer=yes Fixed. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] RE: compilation problem 3.4.0 gcc toolchain / armv6 / 2.6.0-rmk1 kernel
On Wed, 31 Mar 2004, Gupta, Kshitij wrote: forgot to paste the error messeges sound/core/oss/pcm_plugin.c:34: internal compiler error: in loc_descriptor_from_tree, at dwarf2out.c:8800 Please submit a full bug report, with preprocessed source if appropriate. Send email to [EMAIL PROTECTED] for instructions. It's gcc problem. Send your bug-report to this e-mail. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] buffer producer/consumer sync
On Wed, Mar 31, 2004 at 10:32:07AM +0530, Gupta, Kshitij wrote: I was just curious to know about by when will we be having a proper reference driver for ARM . We are ready to help out from here if there are any issues. Given the kernel communities general negative reaction to trying to sort out these problems, I've decided that its not worth me spending my time fixing the core ALSA code any longer. Therefore, expect ALSA to be non-functional on ARM for at least the 2.6 kernel series. Sorry, but that's the way it is. -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] 1.0.4rc1 release
Jaroslav Kysela wrote: On Tue, 30 Mar 2004, Clemens Ladisch wrote: On a 2.2.19 kernel: depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/snd-* ... Missing inclusion of some header files? Sorry, my error. Wrong kernel configuration. (The result of Hey, this old file looks like a kernel -- let's see what happens if I boot it ... ;-) But now: # modprobe snd modprobe: Too deep recursion in module dependencies! modprobe: Circular dependency? snd-page-alloc snd snd_pci_compat_get_pci_driver() is called from pci_compat_pm_callback() in misc.c. I think the 2.2.x CONFIG_APM stuff in misc.c could be moved into pci_compat_22.c, but OTOH it might make more sense to move the PCI functions that don't do page allocation from the snd-page-alloc module into snd. What's your opinion on this? Regards, Clemens --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] buffer producer/consumer sync
On Wed, 31 Mar 2004, Russell King wrote: On Wed, Mar 31, 2004 at 10:32:07AM +0530, Gupta, Kshitij wrote: I was just curious to know about by when will we be having a proper reference driver for ARM . We are ready to help out from here if there are any issues. Given the kernel communities general negative reaction to trying to sort out these problems, I think that the consensus was that using -nopage callback does not make much sense for the DMA pages so remap_page_coherent_range() should be used for this case when designed. Is not that true? We are ready to change the ALSA core ourself, but we need this API on the kernel core side. I also don't mind to include some hacks in our midlevel code to let the ARM platform working. I've decided that its not worth me spending my time fixing the core ALSA code any longer. :-( Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] buffer producer/consumer sync
On Wed, Mar 31, 2004 at 09:44:45AM +0200, Jaroslav Kysela wrote: I think that the consensus was that using -nopage callback does not make much sense for the DMA pages so remap_page_coherent_range() should be used for this case when designed. The consensus was that -nopage is fine to use IFF you have RAM-backed pages. However, the choice of whether -nopage is used or not is one that the architecture must make, and not the device driver. This requires a dma_mmap_coherent() API for all architectures to implement. However, I can not get anyone to even respond to agreeing what the API requires. It's no good one architecture implementing one version of the API and others then deciding that they don't actually like it after all and needing a different API. -- Russell King Linux kernel2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
