Patrick Shirkey wrote:
> > http://www.alsa-project.org/alsa-doc/
> > contains almost as many broken links etc.
>
> Thanks for that. If you have the inclination to send in a patch that
> would be very appreciated.
Not a patch, but the whole thing fixed up:
You can grab it from
http://www.av8n
Patrick Shirkey wrote:
> http://www.alsa-project.org/~goemon/
How did you get access to it?
Google.
This version is now deprecated.
Point taken.
However, the apparently non-deprecated version
http://www.alsa-project.org/alsa-doc/
contains almost as many broken links etc.
Here's the s
Hi --
The soundcard matrix needs attention.
http://www.alsa-project.org/~goemon/
I ran a basic link-checker on it.
The error-log is so large that I hesitate to
send the whole thing by email. Here's the summary:
Code Occurrences What to do
200 1 There are broken fragments which must be fixed.
Patrick Shirkey wrote:
I have added a link to the documentation page now.
I assume the page in question is:
http://www.alsa-project.org/documentation.php3
That is a useful page.
Suggestion: Include that page, verbatim, in the
distribution, in
-- lib/doc/
-- driver/alsa-kernel/Documentati
I wrote:
>>From the keen-grasp-of-the-obvious department:
>>This project would be a lot better off if there were
>>better documentation, and (some) comments in the code.
Then on Thu, 05 Dec 2002 10:23:08 -0500, Paul Davis wrote:
>
>actually, i have to note that this is not so obvious. there are *
; alsactl -f /tmp/foo.ctl store
alsactl: get_control:202: Cannot read control '2,0,0,Digital In Playback
Source,0': Invalid argument
alsactl: get_control:202: Cannot read control '2,0,0,3D Stereo Extender
Switch,0': Invalid argument
alsactl: get_control:202: Cannot read control '2,0,0,Up Down Sw
Uros Bizjak wrote:
Could you put a printk() in snd_sb16_*_pointer() functions
(sb16_main.c souce)? This printk() should print dma channel and value of
ptr, so we can see when/if DMA channels gets stuck.
Done. The result put 2.6 megabytes into /var/log/messages.
The head -10 and tail -50 of t
Clemens Ladisch wrote:
Now when I look at the specifications at it turns out that
Creative isn't outright lying, only being _extremely_ misleading
Whaaat?? Hype and deception from Creative Labs???
Apparently that only happens on days when the sun
rises in the east and sets in the west.
> To
The same program that causes sb16 to become completely
wedged causes milder errors in the cs4239 module.
Reference: see thread starting at:
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg05525.html
The program runs for a while (sometimes 8 minutes,
sometimes less than one minute)
Clemens Ladisch wrote:
USB devices announce their capabilities in their descriptors. Please
post the output of lsusb and the output of "od -t x1
/proc/bus/usb/001/xxx" (xxx is the device number; try all files
there, the one I want to see has "1E 04" somewhere in the first
line).
As requested:
Uros Bizjak wrote:
From the error message you posted about this bug, it looks that driver
is trying to call prepare() operator on a substream that is still
in SNDRV_PCM_STATE_RUNNING state. Perhaps Jaroslav could tell us if this
can happen if hardware pointers are not updated anymore (because s
Uros Bizjak wrote:
Did you try to set 16bit DMA allocation flag to Playback or Capture?
I tried setting it to Capture.
No joy. ALSA gets wedged just the same as before.
By the way, is this DMA Allocation thingy documented anywhere?
I had to do a huge find|grep to figure out what this
s
This is a slightly-updated clone of item
#636948 on the sourceforge bug/patch reporting
system. I'm moving it to here (the alsa-devel
mailing list) at the request of Jaroslav.
It is also a duplicate of something I sent a
few minutes ago with the wrong Subject: li
This is a slightly-updated clone of item
#648063 on the sourceforge bug/patch reporting
system. I'm moving it to here (the alsa-devel
mailing list) at the request of Jaroslav.
hard crash when snd-ice1712 loads
Using snd-ice1712 under rc6 (but not rc3) I observe:
ini
This is a slightly-updated clone of item
#636948 on the sourceforge bug/patch reporting
system. I'm moving it to here (the alsa-devel
mailing list) at the request of Jaroslav.
When talking to Extigy on the USB bus:
alsactl -f /tmp/foo store
alsactl: get_control:202:
This is a slightly-updated clone of item
#636946 on the sourceforge bug/patch reporting
system. I'm moving it to here (the alsa-devel
mailing list) at the request of Jaroslav.
I bought an Extigy, which is capable of 24-bit i/o. It is
also capable of digitizing 96000 fram
This is a slightly-updated clone of item
#648232 on the sourceforge bug/patch reporting
system. I'm moving it to here (the alsa-devel
mailing list) at the request of Jaroslav.
Things run OK for a few minutes (sometimes 30 seconds,
sometimes 5+ minutes) then ALSA gets wedged. Every
17 matches
Mail list logo