- Alsa-devel - mailman.alsa-project.org

[alsa-devel] How to enforce 32bit access?
by Joachim Foerster 11 Oct '07

11 Oct '07

Hi ALSA devs, (based on a Xilinx ML403, PPC405, OPB bus) I have a custom sound controller, which allows 32bit write accesses to its IO memory, only. The controller supports S16_LE, S16_BE, U16_LE, U16_BE with min. and max. 2 channels (stereo), only! => So a frame has to be 32bits wide and one frame has to be written at one point of time (= one 32bit bus access). Now, playing a 16kHz, S16_LE, Mono .wav-file with aplay invokes the conversion framework of the alsa-lib. The following line of code (of pcm_plugin.h) is executed: conv_xx12_xx12: as_u16(dst) = as_u16c(src); This is a 16bit access and thus fails with a Bus error/Kernel Oops. Therefore my question is: In my driver for the controller, how do I tell ALSA, that it is only allowed to write in 32bit quantities? Is this possible at all? Or do I have to use a special .asoundrc file? Thanks, Joachim PS: 16bit, signed/unsigned, LE/BE, stereo (!) .wav files can be played without any problem.

3 8

[alsa-devel] alsa 1.0.15
by paul blakeley 11 Oct '07

11 Oct '07

Can someone please tell me when version 1.0.15 will be released and then become the current stable package?

4 4

[alsa-devel] dont know if bug in /tmp/217usbkeyboardbug.log
by linuxcbon 11 Oct '07

11 Oct '07

hi, I have no idea if this is a bug : tv card is hauppauge wintv model 44346, tuner model is Philips FI1216MF MK2 I found in /tmp/217usbkeyboardbug.log Last 20 lines of dmesg: tveeprom 2-0050: has radio bttv0: Hauppauge eeprom indicates model#44346 bttv0: using tuner=3 bttv0: i2c: checking for MSP34xx @ 0x80... found msp3400 2-0040: MSP3415G-B8 found @ 0x80 (bt878 #0 [sw]) msp3400 2-0040: MSP3415G-B8 supports nicam and radio, mode is autodetect and autoselect bttv0: i2c: checking for TDA9875 @ 0xb0... not found bttv0: i2c: checking for TDA7432 @ 0x8a... not found bttv0: i2c: checking for TDA9887 @ 0x86... not found tuner 2-0061: chip found @ 0xc2 (bt878 #0 [sw]) tuner 2-0061: type set to 3 (Philips (SECAM+PAL_BG) (FI1216MF, FM1216MF, FR1216MF)) tuner 2-0061: type set to 3 (Philips (SECAM+PAL_BG) (FI1216MF, FM1216MF, FR1216MF)) bttv0: registered device video0 bttv0: registered device vbi0 bttv0: registered device radio0 bttv0: PLL: 28636363 => 35468950 .. ok ALSA /mnt/hda3/sources/sources116/alsa-driver-1.0.15rc2/pci/bt87x.c:872: unknown card 0x878-0x70:0x13eb ALSA /mnt/hda3/sources/sources116/alsa-driver-1.0.15rc2/pci/bt87x.c:875: please mail id, board name, and, if it works, the correct digital_rate option to <alsa-devel(a)alsa-project.org> ACPI: PCI Interrupt 0000:01:04.1[A] -> Link [LNK1] -> GSI 5 (level, low) -> IRQ 5 ALSA /mnt/hda3/sources/sources116/alsa-driver-1.0.15rc2/pci/bt87x.c:943: bt87x0: Using board 0, analog, digital (rate 32000 Hz) I hope this can help. regards _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

2 1

[alsa-devel] vaio_mux's num_items is not equal to the actual items
by zhejiang 11 Oct '07

11 Oct '07

In patch_sigmatel.c, static struct hda_input_mux vaio_mux = { .num_items = 2, .items = { /* { "HP", 0x0 }, */ { "Mic Jack", 0x1 }, { "Internal Mic", 0x2 }, { "PCM", 0x3 }, } }; Why is the num_items not 3 ? The "PCM" won't be selected with num_times = 2.

2 1

[alsa-devel] Creative Labs XFi drivers.
by Tobin Davis 11 Oct '07

11 Oct '07

Creative Labs has released a proprietary driver base for their XFi cards. I downloaded it because it claims to have compatibility with alsa. In fact, it requires alsa include files to be able to compile. I haven't looked at the source yet (this information is all in the Readme.txt in the main download) and probably won't (especially since I don't own a Creative Labs XFi card). What I don't understand, is are they allowed to use our code to build their drivers? They use alsa core modules to interoperate (from what I can tell in the Readme.txt). Also, this line in the License.txt is especially troubling: > In the event that the Software includes Linux code or drivers, then, unless expressly stated to the contrary, such Linux > code and drivers are proprietary to Creative and all rights therein are reserved. I'm deleting all but the big tarball I downloaded. I'll delete it later. -- Tobin Davis <tdavis(a)dsl-only.net>

4 4

[alsa-devel] Alsa 1.0.15rc2 and oops with Dell M1210
by zhejiang 10 Oct '07

10 Oct '07

Seems that the spec->input_mux contains no item at all. So system maybe crash in the snd_hda_input_mux_info() when try to copy the items[].label,which is null pointer. May you replace the function stac92xx_mux_enum_info() in alsa-driver-1.0.15rc2/alsa-kernel/pci/hda/patch_sigmatel.c ? static int stac92xx_mux_enum_info(struct snd_kcontrol *kcontrol, struct snd_ctl_elem_info *uinfo) { struct hda_codec *codec = snd_kcontrol_chip(kcontrol); struct sigmatel_spec *spec = codec->spec; printk("spec->input_mux->num_items is %d \n",spec->input_mux->num_items); if(!spec->input_mux->num_items) return 0; return snd_hda_input_mux_info(spec->input_mux, uinfo); } Does it still crash? What's the number of num_items? The pin_config for M1210 didn't include any input pin. I wonder why.

3 4

Re: [alsa-devel] chmod with USB sound device?
by william estrada 10 Oct '07

10 Oct '07

Harald, I revisited /etc/security/console.perms.d/50-default.perms and got it to work. For the list, I changed: In /etc/security/console.perms.d/50-default.perms > # permission definitions . > <console> 0666 <sound> 0666 root And In /etc/udev/rules.d/50-udev.rules > KERNEL=="snd/*", MODE="0666", OWNER="wre00:root" Then I did the udevtrigger. Then i did the udevtrigger, plugged in my USB sound device and got this: > [root@laptop wre00]# ls -lrt /dev/snd > total 0 > crw-rw-rw- 1 wre00 root 116, 2 Oct 10 09:45 timer > crw-rw-rw- 1 wre00 root 116, 3 Oct 10 09:45 seq > crw-rw-rw- 1 wre00 root 116, 4 Oct 10 09:45 pcmC0D0p > crw-rw-rw- 1 wre00 root 116, 5 Oct 10 09:45 pcmC0D0c > crw-rw-rw- 1 wre00 root 116, 6 Oct 10 09:45 controlC0 > crw-rw-rw- 1 wre00 root 116, 7 Oct 10 10:28 pcmC1D0p > crw-rw-rw- 1 wre00 root 116, 8 Oct 10 10:28 pcmC1D0c > crw-rw-rw- 1 wre00 root 116, 9 Oct 10 10:28 controlC1 I guess both changes are required but it now works. Thanks for your time. William Estrada MrUmunhum(a)popdial.com Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net ) Ymessenger: MrUmunhum Harald Hoyer wrote: > william estrada wrote: >> Hi guys, >> >> I'm trying to run 'chmod' on a USB sound card using 'Hot Plug' udev >> support. >> From reading, I think I need to update my >> '/etc/udev/rules.d/50-udev.rules'? >> I have made these changes: >>> # audio devices . >>> KERNEL=="snd/*", MODE="0666" > > You may have a look in pam_console... > /etc/security/console.perms > /etc/security/console.perms.d/* >

1 0

[alsa-devel] snd-hdsp & digiface
by Fernando Lopez-Lezcano 10 Oct '07

10 Oct '07

Hi... We are using both digiface and multiface interfaces here at ccrma and we have a (small) problem of consistency in the channel numbering because of the way they are connected. Both cards are connected digitally to digital mixers, but in the case of the multiface the digital channels (which would be the ones users use) are 9-16 while on the digiface the first eight are 1-8[*]. Is there a way to change the ordering in the multiface so that the digital interface is presented as ports 1-8 instead of 9-16? (even a hack to the driver would be welcome) - and preferably one that does not need the default interface to be changed from hw:0 in jack... -- Fernando [*] accounts are shared so any configuration you do on one machine for 1-8 will be wrong for the other where the real outputs are 9-16.

2 1

Re: [alsa-devel] different user causes 'no such device'
by william estrada 10 Oct '07

10 Oct '07

Thanks, I did a 'chmod -R 666 /dev/snd/' and it worked. Now how do I make the hot plugged USB sound device use these setting?? Thanks for your time. William Estrada MrUmunhum(a)popdial.com Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net ) Ymessenger: MrUmunhum Takashi Iwai wrote: > At Wed, 03 Oct 2007 12:55:27 -0700, > william estrada wrote: >> Hi guys, >> >> I have what seams like a interesting problem. I have written an ALSA app >> to record wav files and it runs while I am logged in an terminal as the >> logged in Gnome user or root. But when I su to another user, it can't >> find the default sound card. >> >> I am running FC6. I tried changing own of /dev/dsp to 'nobody', that did >> not work. >> >> Anyone know of this problem and a fix for it. >> >> Thanks for your time. >> >> -- >> William Estrada >> MrUmunhum(a)popdial.com >> Mt-Umunhum-Wireless.net ( http://Mt-Umunhum-Wireless.net ) >> Ymessenger: MrUmunhum >> >>> MSGrec - Version 1.1, Mt-Umunhum-Wireless.net >>> WavMSG: Paused: enter 'q' to stop, <ENTER> to start. >>> ALSA lib confmisc.c:848:(snd_func_card_driver) cannot find card '0' >>> ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device >>> ALSA lib confmisc.c:397:(snd_func_concat) error evaluating strings >>> ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device >>> ALSA lib confmisc.c:1248:(snd_func_refer) error evaluating name >>> ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device >>> ALSA lib conf.c:3972:(snd_config_expand) Evaluate error: No such device >>> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default > > ALSA-native apps access only ALSA device files, usually /dev/snd/*, > not /dev/dsp*, those for OSS. In this case, it should be > /dev/snd/controlC* files. Check the premission of these files. > > > Takashi >

2 1

[alsa-devel] Add quirk support for Dell XPS1330 and Inspiron 1420.
by Tim Gardner 10 Oct '07

10 Oct '07

-- Tim Gardner tim.gardner(a)ubuntu.com

2 1