Hartmut Geissbauer wrote:
Clemens Ladisch wrote:
Hartmut Geissbauer wrote:
The only thing that's missing now are the two playback ports.
Please show the output of lsusb -v.
The descriptors look OK.
But only at first sight.
Please try this patch.
HTH
Clemens
--
Index:
hi,
Any insights will be really helpful :) .
regards
-kshitij
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gupta,
Kshitij
Sent: Wednesday, February 25, 2004 4:59 PM
To: 'Jaroslav Kysela'
Cc: [EMAIL PROTECTED]
Subject: RE: [Alsa-devel] Dma query
On Thu, 26 Feb 2004, Gupta, Kshitij wrote:
hi ,
That's correct the pages will be in whole meory space and I will be
using snd_pcm_lib_preallocate_pages_for_all api for allocating the space.
There are some DMA apis (for our dma framework) like
set_dma_transfer_params(srcaddr,
Looks like a Sound Blaster compatible.
Try
modprobe snd-sb16 enable=1 isapnp=0 port=0x0220 mpu_port=0x330 irq=5
dma8=1 dma16=5
Cheers
James
Tom Watson wrote:
Ah, a new card to try...
This time it is an Ensonic ESS-1869 that is built into an older Compaq
laptop (Armada 3500). When I put in the
On Thu, 2004-02-26 at 11:30, Jaroslav Kysela wrote:
On Thu, 26 Feb 2004, Michel Dnzer wrote:
LD_PRELOAD=~/src/alsa-cvs/alsa-oss/alsa/.libs/libaoss.so bzflag
zsh: segmentation fault
[...]
How can I debug this?
Define this:
export ALSA_OSS_DEBUG=1
and run the application again.
Hi,
So does that mean that the __next period__ DMA transfer parameters
should be set in the interrupt routine(end of transfer of one period). But
to set the next DMA transfer params we must know the start address of the
buffer which the middle layer has filled (and if the middle layer has
On Thu, 2004-02-26 at 15:10, Jaroslav Kysela wrote:
Can you try with the mpg123 program? It works on x86.
It can successfully print the usage info, but also crashes when trying
to actually play a file. Note that even gdb crashes on startup, so the
problem seems completely unrelated to sound?
On Thu, 26 Feb 2004, Gupta, Kshitij wrote:
Hi,
So does that mean that the __next period__ DMA transfer parameters
should be set in the interrupt routine(end of transfer of one period). But
to set the next DMA transfer params we must know the start address of the
buffer which the
On Thu, 26 Feb 2004, Michel Dnzer wrote:
On Thu, 2004-02-26 at 15:10, Jaroslav Kysela wrote:
Can you try with the mpg123 program? It works on x86.
It can successfully print the usage info, but also crashes when trying
to actually play a file. Note that even gdb crashes on startup, so
Mathieu Rondonneau wrote:
I don't understand why count is 1024 ?
why count is not equal to runtime-period_size (i.e. 16*1024)?
If your frame size is 4, this is the size of a memory page. I guess
ALSA wants to copy the data one page at a time, and this is required
if the buffer isn't
On Thu, 2004-02-26 at 15:33, Jaroslav Kysela wrote:
It looks that the wrapper code does not work as expected.
Can you add a printf calls to all public functions in
the alsa-oss/alsa/alsa-oss.c code, so we can determine
where the code hangs?
The problem occurs when the ALSA_OSS_WRAPPER
Hi,
1) I've got 3 separate PCM 'mono' streams of data that I want to
send to
3 different outputs.
Should work.
a) How many PCM inputs do these cards/drivers support? Under OSS,
there were 2, /dev/dsp and /dev/dsp1. Ideally I would like each
input
stream to have a seperate sample rate. In
PROTECTED]
diff -ru alsa-20040226-orig/alsa-oss/alsa/alsa-oss.c
alsa-20040226/alsa-oss/alsa/alsa-oss.c
--- alsa-20040226-orig/alsa-oss/alsa/alsa-oss.c 2004-02-19 17:02:20.0 +0100
+++ alsa-20040226/alsa-oss/alsa/alsa-oss.c 2004-02-26 20:26:39.0 +0100
@@ -196,10 +196,8
Selon Clemens Ladisch [EMAIL PROTECTED]:
Mathieu Rondonneau wrote:
I don't understand why count is 1024 ?
why count is not equal to runtime-period_size (i.e. 16*1024)?
If your frame size is 4, this is the size of a memory page. I guess
ALSA wants to copy the data one page at a time, and
The documentation seems to imply sound blaster compatable as well. So
I tried that driver, as suggested (thanks!) and got a similar result:
...snd-sb16.o: init_module: No such device
Hint...
Oh, well. Any new ideas?? Does anyone have experience with this
laptop and its sound card??
...Thanks
On Thu, 26 Feb 2004, Michel Dnzer wrote:
On Thu, 2004-02-26 at 15:33, Jaroslav Kysela wrote:
It looks that the wrapper code does not work as expected.
Can you add a printf calls to all public functions in
the alsa-oss/alsa/alsa-oss.c code, so we can determine
where the code hangs?
Salut Clemens,
Clemens Ladisch wrote:
Hartmut Geissbauer wrote:
The descriptors look OK.
But only at first sight.
Please try this patch.
HTH
Clemens
That _has_ helped. Now the device is fully functional. Thank you very
much for your patience and your advices.
Kindly regards,
On Thu, 2004-02-26 at 16:55, Sergey Vlasov wrote:
$ gdb mpg123
(gdb) set args xxx.mp3
Or gdb --args mpg123 xxx.mp3 ;)
(gdb) set env LD_PRELOAD /home/user/src/alsa-cvs/alsa-oss/alsa/.libs/libaoss.so
(gdb) run
This way LD_PRELOAD will be set only for the debugged process, and not for
the
On Thu, 26 Feb 2004, Michel Dnzer wrote:
On Thu, 2004-02-26 at 11:30, Jaroslav Kysela wrote:
On Thu, 26 Feb 2004, Michel Dnzer wrote:
LD_PRELOAD=~/src/alsa-cvs/alsa-oss/alsa/.libs/libaoss.so bzflag
zsh: segmentation fault
[...]
How can I debug this?
Define this:
Perry Gilfillan wrote:
Hello,
has any one done any work to develop ALSA versions of the tvmixer and
tvaudio mixer drivers?
Thanks,
Perry
So, no one was interested?
Well, I've made a first effort, and it works in it's way.
As far as I can tell the Segfaults are solved, and it loads and
20 matches
Mail list logo
