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

[alsa-devel] [PATCH] SM56 Modem in Asus A8J Notebook Series
by Christian Rothländer 18 May '07

18 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there after I submitted the solution 5 month ago in the Bug system, I am trying it now directly. Attached to this posting is the necessary patch to get this modem working with slmodemd. The Patch is against alsa-driver-1.0.14rc4/alsa-kernel/pci/hda/patch_si3054.c if included it's Bug #0002732, assigned to tiwai. Greetings Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTadQYMBp7Qf+VpkRAp8MAJ9lii0FA/lBZPRabFxWIiVVJnAh7wCdGEkk fH0mFw4iOP3S9BHcTor3qVo= =suhj -----END PGP SIGNATURE----- --- patch_si3054.c 2007-05-18 15:06:23.000000000 +0200 +++ patch_si3054.c 2007-05-18 15:06:56.000000000 +0200 @@ -305,6 +305,7 @@ { .id = 0x10573055, .name = "Si3054", .patch = patch_si3054 }, { .id = 0x10573057, .name = "Si3054", .patch = patch_si3054 }, { .id = 0x10573155, .name = "Si3054", .patch = patch_si3054 }, + { .id = 0x15433155, .name = "Si3054", .patch = patch_si3054 }, /*Asus A8J Modem (SM56)*/ {} };

2 1

[alsa-devel] [PATCH] Add support for gain in softvol plugin
by Steve Longerbeam 18 May '07

18 May '07

Hi all, What do you think of this patch? I tested this using a stac9205 HDA codec with all sample formats supported by softvol (s32, s16, s24, big and little endian). The potential drawback I see is that softvol now has to use a intermediate long long multiply and add when computing amplified 32-bit samples. This wasn't an issue with the system I tested on, but possibly could be on slower machines. Also, are their any portability issues with using a long long datatype in alsa-lib? What is the list of embedded architectures that alsa-lib is targeted to build on? I see long long used in many other places in alsa-lib, so I'm hoping this isn't an issue. Steve

3 11

[alsa-devel] submitting a patch against the ALSA repos
by Adrian McMenamin 18 May '07

18 May '07

I have submitted my patch against the 2.6.21 kernel tree but I dare say I need to actually submit it against the alsa repos. I have a few questions: 1. Which set of sources do I patch - I assume alsa-driver - is that right? 2. How do I patch the firmware repo? As it is a binary I assume it is by some means other than patch(1) 3. This is a new architecture - there are no other SuperH drivers in alsa (afaik) - how do I add a new architecture? My memory is that when I tried this a year ago it was a bit of a nightmare.

3 4

Re: [alsa-devel] [PATCH] asihpi 3.07.04
by Takashi Iwai 18 May '07

18 May '07

At Fri, 18 May 2007 13:16:44 +1200, Eliot Blennerhassett wrote: > > Greetings, > > Attached patch for alsa-driver/pci/asihpi > > Signed-off-by: Eliot Blennerhassett <eblennerhassett(a)audioscience.com> > The accompanying patch also requires updated firmware > http://audioscience.com/internet/download/firmware/asihpi_firmware-3.07.04.… > > Based on > http://audioscience.com/internet/download/hpklinux-3.07.04.tar.bz2 > Release notes > http://audioscience.com/internet/download/drvnotes.txt > http://audioscience.com/internet/download/drvnotes_rc.txt > > Main points > The bulk of this patch is addition of doxygen documentation to hpi.h and > hpifunc.c. (hopefully coming to the end of this soon) > > Add several new adapter types ASI6618, ASI6518. ASI8900 > Bug fixes to ASI6416 DSP code > Filtered out some more conditionally not compiled for ALSA. > > asihpi.c: experimental MMAP mode (disabled) > hpidebug.h: simplify debug macros > hpios_linux_kernel.h: remove a layer of macros wrapping spinlocks > hpicmn.c: pull more common code from hpi backends > hpifunc.c: remove more obsolete functions > hpimsgx.c: remove dead code > hpios.h pOsReference now struct pci_dev* not void* > hpi6205.c: use power of 2 buffers (REQUIRES matching firmware) Thanks. Many chunks look like a good clean up. Now committed to ALSA HG tree (both driver and firmware). Takashi

1 0

[alsa-devel] HDA: Fix headphone mute issue on non-eapd Conexant systems.
by Tobin Davis 18 May '07

18 May '07

This patch fixes an automute code issue for systems that do not rely on eapd support. Signed off by Tobin Davis <tdavis(a)dsl-only.net>

2 1

[alsa-devel] [PATCH] asihpi 3.07.04
by Eliot Blennerhassett 18 May '07

18 May '07

Greetings, There is a new patch for alsa-driver/pci/asihpi here http://audioscience.com/internet/download/alsa_driver3282_asihpi30704.patch Signed-off-by: Eliot Blennerhassett <eblennerhassett(a)audioscience.com> The accompanying patch also requires updated firmware http://audioscience.com/internet/download/firmware/asihpi_firmware-3.07.04.… Based on http://audioscience.com/internet/download/hpklinux-3.07.04.tar.bz2 Release notes http://audioscience.com/internet/download/drvnotes.txt http://audioscience.com/internet/download/drvnotes_rc.txt Main points The bulk of this patch is addition of doxygen documentation to hpi.h and hpifunc.c. (hopefully coming to the end of this soon) Add several new adapter types ASI6618, ASI6518. ASI8900 Bug fixes to ASI6416 DSP code Filtered out some more conditionally not compiled for ALSA. asihpi.c: experimental MMAP mode (disabled) hpidebug.h: simplify debug macros hpios_linux_kernel.h: remove a layer of macros wrapping spinlocks hpicmn.c: pull more common code from hpi backends hpifunc.c: remove more obsolete functions hpimsgx.c: remove dead code hpios.h pOsReference now struct pci_dev* not void* hpi6205.c: use power of 2 buffers (REQUIRES matching firmware) -- Eliot

1 0

[alsa-devel] Newbie questions regarding ALSA drivers
by Pharaoh . 17 May '07

17 May '07

Hi, I am very new to ALSA and just trying to get familier with the things, I have got few questions. 1. Is it true that all the OSS drivers are included only in directory linux/sound/oss and no where else? 2. There are arch specific folders like ARM, MIPS etc, so all the drivers in these folders are ALSA or OSS? 3. If I write a new driver for an OMAP based board, it should go in to linux/sound/arm/omap/ right? Or only ALSA drivers for this board should go there? 4. I have some old OSS drivers which were written for my board, do I need to make them ALSA drivers to be in line with the latest trend i.e. phasing out OSS drivers? -Pharaoh.

2 1

[alsa-devel] Audio driver for OMAP 730 based board - hpw to migrate from OSS to ALSA
by Pharaoh . 17 May '07

17 May '07

Hi I am new here and have slight idea about the Linux audio drivers. I am working on OMAP 730 based p2-sample board. AFAIK, there is no audio driver support for this board. I have found 2.4 drivers for the same board which I have ported to 2.6, but it is an OSS driver. So, the questions: 1. Has anyone written audio drivers for the above mentioned board? Any plans to make them open source? Any pointers will be useful regarding the same. 2. How should I go about migrating the OSS driver to ALSA, if something like this is necessary? 3. Any resources which will be helpful for writing ALSA drivers? Thanks & regards, Pharaoh.

1 1

Re: [alsa-devel] Can someone verify support for "AzTech Sound Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset - FCC-ID:I38-MMSN846" ?
by ramkromberg＠mail.com 17 May '07

17 May '07

Yes, its like you said Rene, sb8 works although the sound is distorted and the module can't be removed... Later I can modprobe sgalaxy too, and the sound works without a hitch. Also since now I can compile some code - your "eeprom.c" compiles and works - I'm available for further testing... I also noticed that the binary you sent was 506kb while my compilation is 9kb, maybe you sent an early/later version with some additional includes for verbose ? I compiled it with "gcc -W -Wall -o eeprom eeprom.c" like you said (on my xubuntu 7.04 with build-essentials deb package installed). See attachment... Ram Kromberg ramkromberg(a)mail.com

2 1

Re: [alsa-devel] Can someone verify support for "AzTech Sound Galaxy Nova 16 Extra II-3D - using AZT-2316/R Chipset - FCC-ID:I38-MMSN846" ?
by ramkromberg＠mail.com 17 May '07

17 May '07

You did it Rene !!! >sudo ./eeprom >sudo modprobe snd-sgalaxy sbport=0x220 wssport=0x530 It's working now !! I downloaded the binary (i didn't compile the code), chmod it, sudo it and the sgalaxy worked !!! the sb8 didn't work but I don't really care for that anyhow :-) For the record, I tested it on xubuntu 7.04 with xmms. Are you now planning to implement the code to the driver itself ? If you want me to test anything, let me know. i'm also considering installing slackware 11 since I need the preformance... THANKS !!! Ram Kromberg ramkromberg(a)mail.com

2 1