[Alsa-devel] Problem with my test driver

I am building a driver for the Sega Dreamcast (sorry for all those who have heard this before). I get this when I attempt to see it using aplay: / # aplay -l ALSA lib control.c:612:(snd_ctl_open_noupdate) Invalid CTL hw:0 aplay: device_list:199: control open (0): No such file or directory aplay:

[Alsa-devel] Trivial bug in aplay

There seems to be a missing LF in the output of aplay --version: / # aplay --version aplay: version 0.9.6 by Jaroslav Kysela [EMAIL PROTECTED]/ # / # It's obviously not serious! And I am too lazy to submit a patch for something this trivial :) But maybe should be fixed in the next version?

Re: [Alsa-devel] Static versus shared builds of alsa-utils

On Monday 01 September 2003 09:11, Clemens Ladisch wrote: Adrian McMenamin wrote: [...] This certainly generates large (static?) binaries: -rwxr-xr-x1 00 2294664 Aug 31 19:26 aplay But when I attempt to run any of them I get this problem: /usr/bin # ./aplay

Re: [Alsa-devel] Static versus shared builds of alsa-utils

On Monday 01 September 2003 11:27, Clemens Ladisch wrote: Adrian McMenamin wrote: Do the compiler flags include --static? Maybe you can add this flag by setting CFLAGS explicitly when ./configure-ing. Exactly, but how? CC=sh-linux-gcc CFLAGS=--static ./configure --xxx=... HTH

Re: [Alsa-devel] Static versus shared builds of alsa-utils

On Monday 01 September 2003 11:27, Clemens Ladisch wrote: Adrian McMenamin wrote: Do the compiler flags include --static? Maybe you can add this flag by setting CFLAGS explicitly when ./configure-ing. Exactly, but how? CC=sh-linux-gcc CFLAGS=--static ./configure --xxx=... OK

[Alsa-devel] Static versus shared builds of alsa-utils

I am trying to build alsa-utils using a cross compiler. AFAICS I have successfully built alsalib (as static as I have no glibc on the target system - it runs a static busybox), and I thought I had successfully configured and built alsa-tools: CC=sh-linux-gcc ./configure --host=sh-linux

[Alsa-devel] Cross compiling alsa-utils

Apologies to anyone who has read this within the bowels of the thread about building alsa-lib as cross compiled static library. Actually, I have been able to compile and install static versions of the alsa-libs, though I am finding it next to impossible to configure the alsa-utils for cross

Re: [Alsa-devel] Cross compiling alsa-utils

On Sunday 31 August 2003 11:17, Adrian McMenamin wrote: Apologies to anyone who has read this within the bowels of the thread about building alsa-lib as cross compiled static library. Actually, I have been able to compile and install static versions of the alsa-libs, though I am finding

[Alsa-devel] Problems with a PCM driver

I am writing a PCM driver for the AICA device on the Sega Dreamcast for a 2.6.0-testX kernel. The driver is far from complete, but I am having various problems when I test bits of it... A simple write of a file gives me this... /dev/snd # cat /test.txt pcmC0D0p ALSA sound/sh/aica.c:165: In

Re: [Alsa-devel] Problems with a PCM driver

On Saturday 30 August 2003 20:14, James Courtier-Dutton wrote: Adrian McMenamin wrote: I am writing a PCM driver for the AICA device on the Sega Dreamcast for a 2.6.0-testX kernel. The driver is far from complete, but I am having various problems when I test bits of it... A simple

Re: [Alsa-devel] Problems with a PCM driver

On Saturday 30 August 2003 20:45, James Courtier-Dutton wrote: Adrian McMenamin wrote: On Saturday 30 August 2003 20:14, James Courtier-Dutton wrote: Adrian McMenamin wrote: I am writing a PCM driver for the AICA device on the Sega Dreamcast for a 2.6.0-testX kernel. The driver is far

[Alsa-devel] Static build of alsa-lib?

Thanks to James I now know a few more of things I need to do to build and test my sound driver on the Dreamcast. But the system I am installing to is based on a static version of Busybox - there is no glibc (or indeed any other C RTL) available on it. Thus I need to build anything I install as

[Alsa-devel] Re: Static build of alsa-lib?

On Saturday 30 August 2003 21:41, Adrian McMenamin wrote: Thanks to James I now know a few more of things I need to do to build and test my sound driver on the Dreamcast. Apologies, I should have read the INSTALL file properly

Re: [Alsa-devel] Static build of alsa-lib?

On Saturday 30 August 2003 22:08, James Courtier-Dutton wrote: Adrian McMenamin wrote: Thanks to James I now know a few more of things I need to do to build and test my sound driver on the Dreamcast. But the system I am installing to is based on a static version of Busybox

[Alsa-devel] A bug or feature in PCM handling or is it really meant to be this way?

I have been working on writing an ALSA driver for the Sega Dreamcast AICA sound system (PCM). But I have noticed that 2.6.0-test2 will not build for PCM unless the OSS PCM emulation is turned on? Is that the way it is meant to be? If so, why different options in the kbuild process? Adrian

Re: [Alsa-devel] Attn Soundcard matrix maintainer.

On Tuesday 05 August 2003 00:05, Eliot Blennerhassett wrote: For AudioScience cards [snip] Just noticed this matrix. Could you add (In green?) the AICA Super Intelligent Sound Processor to the matrix - either under Sega (it is the Dreamcast's sound card) or Yamaha (who actually manufactured

[Alsa-devel] Why should I port my OSS driver to ALSA?

I wrote the OSS driver for the Sega Dremcast for OSS. Are there any real world advantages of porting this to ALSA (the hardware is quite specific and isn't going to appear anywhere else)? Adrian ___ Alsa-devel mailing list [EMAIL PROTECTED]