Hi,
Your fix of the ALSA memory allocation problem is incorrect. This only fixes the
problem with the commerical USB Audio driver. It does not fix for all drivers. The
proper fix is to replace the function setup_pcm_id with this one (note the added
"card->number << 24"):
==
On Thu, May 13, 2004 at 06:28:17PM +0200, Giuliano Pochini wrote:
> Good question. The current approach is based on the control
> names but sometimes they're not enough. What do you suggest ?
I am testing changed aoss lib which uses dmix plugin
to play simultaniously many stereo sound sources.
Now
On Mon, 10 May 2004 17:08:49 +0200
Takashi Iwai <[EMAIL PROTECTED]> wrote:
> prepare and trigger callbacks are already in irq-disabled.
> i.e. you need only spin_lock() in them.
Does it mean that ALSA acquires the lock only when it calls PCM callbacks,
that is trigger(), etc., are atomic only wr
On Thursday 13 May 2004 7:12 pm, Jaroslav Kysela wrote:
> Maybe, lost interrupts can cause this. Actually, there is no
> correction in the PCM slave timer code for this situation.
Looking over the figures again, it looks like (for the test case
forwarded to me) the sequencer queue is actually con
At Thu, 13 May 2004 20:06:45 +0200,
I wrote:
>
> [1 ]
> At Thu, 13 May 2004 10:53:48 -0700,
> Loc Ho wrote:
> >
> > Hi,
> >
> > Also, after looking at the snd memory allocation routines, the
> > unique tag are type, id, and flag. The type is "continous". The id is
> > formated by the device ID,
Fix for:
/home/Giu/soft/alsa-driver-1.0.4/ppc/pmac.c: In function `snd_pmac_tx_intr':
/home/Giu/soft/alsa-driver-1.0.4/ppc/pmac.c:702: warning: `return' with no value, in
function returning non-void
[...]
--- ppc/pmac.c_old Thu May 13 19:49:12 2004
+++ ppc/pmac.c Thu May 13 19:49:57 200
At Thu, 13 May 2004 10:53:48 -0700,
Loc Ho wrote:
>
> Hi,
>
> Also, after looking at the snd memory allocation routines, the
> unique tag are type, id, and flag. The type is "continous". The id is
> formated by the device ID, stream number, and substream number. The
> flag is the kernel memory fl
On Thu, 13 May 2004, Chris Cannam wrote:
> I asked about this on the JACK list just now and was recommended to
> bring the question here instead. So here we are.
>
> If I'm running JACK with output to my first (and only) PCM device, and
> I have a JACK client running that also sets up an ALSA
At Thu, 13 May 2004 10:45:20 -0700,
Loc Ho wrote:
>
> Hi,
>
> Are you saying that the third parameter for the function
> snd_pcm_new, int device, should be the value of the "chip" (driver
> context pointer) pointer.
no.
as written in my last mail, both dev and id fields of struct
snd_dma_device
On Wed, 2004-05-12 at 12:57, Takashi Iwai wrote:
> At Wed, 12 May 2004 12:31:54 +0200,
> Michel DÃnzer wrote:
> >
> > The only thing that bothers me is
> > https://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=057,
> > but I can live with it.
>
> sorry, forgot to answe
On 13-May-2004 Adam Tla/lka wrote:
>> What do you want to do with the mixer?
> Hmm - typically people just want to control PCM volume.
> When using OSS you can just do mixer ioctl's on the opened PCM fd.
> Simple and clear.
No, it's not simple, unless the driver makes it simple
removing some cap
>When using OSS you can just do mixer ioctl's on the opened PCM fd.
When using OSS, you can't model a lot of the functionality present in
contemporary audio interface hardware mixers.
So there's a choice: a limited, simple API that fails to support card
features, or a complex API that over time g
On Wed, May 12, 2004 at 05:40:55PM +0200, Clemens Ladisch wrote:
> Ronald S. Bultje wrote:
> > for a given alsa device ("default", "dmix", "plughw:N", "hw:N,M",
> > "dspN", etc.), how do I automatically obtain the right device to use as
> > a audio mixer with that device?
>
> Depends on your defin
Rodrigo Severo wrote:
> With the Askey Magic I got only silence but with the Prolink PlayTV Pro
> revision 9D I got bad sound with btaudio. By bad I mean a slightly high
> pitch soundI got the sound of the TV with a slightly higher pitch than
> usual and with more than usual noise during silence. T
At Wed, 12 May 2004 18:36:56 GMT,
[EMAIL PROTECTED] wrote:
>
>
> > nice, i'll add this to alsa-driver tree.
> > i guess pci/emu10k1 is the best location.
>
> That's fine. I had it under pci on my system just because it was easier.
>
> > would you mind to change the indentation level to 8, as de
I asked about this on the JACK list just now and was recommended to
bring the question here instead. So here we are.
If I'm running JACK with output to my first (and only) PCM device, and
I have a JACK client running that also sets up an ALSA sequencer
queue with its timer set to the ALSA PCM
At Wed, 12 May 2004 18:40:05 -0700,
Loc Ho wrote:
>
> Hi,
>
> I developed an custom USB Audio driver. In addition, I am also using
> the provided USB Audio driver for commercial USB Audio devices. After
> some testing with the custom USB Audio driver and the provided USB
> Audio driver, there see
At Thu, 13 May 2004 09:22:51 +0200 (CEST),
Giuliano Pochini wrote:
>
>
> On 10-May-2004 Takashi Iwai wrote:
> > At Sun, 9 May 2004 18:21:21 +0200,
> > Giuliano Pochini wrote:
> >>
> >> I read /linux/Documentation/firmware_class/README infos about the firmware
> >> loader. That loader is not used
On 10-May-2004 Takashi Iwai wrote:
> prepare and trigger callbacks are already in irq-disabled.
> i.e. you need only spin_lock() in them. [...]
Fine. I moved SetSampleRate() from prepare() to the hw_params()
callback because it may need to reload the firmware.
--
Giuliano.
-
On 10-May-2004 Takashi Iwai wrote:
> At Sun, 9 May 2004 18:21:21 +0200,
> Giuliano Pochini wrote:
>>
>> I read /linux/Documentation/firmware_class/README infos about the firmware
>> loader. That loader is not used by any of the alsa drivers. Is there a
>> reason ? Should I write my own custom load
20 matches
Mail list logo
