Moving alsa to the kernel will certainly increase the projects momentum, but
do keep the framebuffer story in mind.
Heres what google dragged in:
http://eca.cx/lad/2000/Jun/0106.html
I would regret to see something like that happening to alsa. Please do not
compromise in exchange for
On Wed, 28 Nov 2001, Paolo Meglio wrote:
Hello, came to buy a SB Audigy Soundcard.
Whitch version of ALSA support the Audigy Soundcard?
If not ready yet, when will appear the ALSA-driver with support for SB
Audigy??
We have no programming information regarding the new EMU chip in Audigy
Jaroslav Kysela wrote:
On Wed, 28 Nov 2001, Paolo Meglio wrote:
Hello, came to buy a SB Audigy Soundcard.
Whitch version of ALSA support the Audigy Soundcard?
If not ready yet, when will appear the ALSA-driver with support for SB
Audigy??
We have no programming information regarding the
Hi folks,
Ok, I had made some tests yesterday evening and I will go on this evening.
I tried the magic key and the insert (actually now I get what it is
doing and this is very nice!).
But I did those things in the wrong order and I have to start again the
'get ready and freeze' session
On Wed, Nov 28, 2001 at 05:32:15PM +0100, Jaroslav Kysela wrote:
It's very much better to use the alsa-driver/utils/insert script, and look
to alsa-driver/snd.map file for the IP address, where driver crashed. We
can determine easily the function.
OK, done that now. I'm a bit lost now though.
On Thu, 29 Nov 2001, Steve Harris wrote:
On Wed, Nov 28, 2001 at 05:32:15PM +0100, Jaroslav Kysela wrote:
It's very much better to use the alsa-driver/utils/insert script, and look
to alsa-driver/snd.map file for the IP address, where driver crashed. We
can determine easily the function.
Hello I took the advice of installation which you give and I have use
the last drivers of alsa but my chipset its ac97 is still not
recognized when I make 'make' after './configure' ,it occurs errors of
compilation. Thank
you to advise me.
make[1]: Entering directory
On Thu, Nov 29, 2001 at 09:54:08AM -0500, Paul Davis wrote:
those messages don't show up in these cases. i have seen 1 or examples
of them in /var/log/messages, but none during the tests i have been
running. all day yesterday, i got just one.
$ arecord -f dat -F 677 -M 2000 /dev/null
will
the problem with the trident driver is definitely the spurious
irqs. the driver doesn't print all such spurious interrupts, which is
why they don't show up in my logs. when i changed my trace code, its
became clear that they definitely occur quite often.
the problem with dropping spurious irqs
On Thu, Nov 29, 2001 at 04:21:31PM +0100, Jaroslav Kysela wrote:
Can you try the lasest CVS code or this patch?
Nice one. Tried CVS, seems to have fixed it. I got a segfault from ardour,
and my machine is still up.
I'l stress it some more, and shout if I manage to make it lock up.
Thanks,
I have a via8233 (part of the kt266a chip set) on a shuttle ak31a
motherboard.
On Thu, 29 Nov 2001, Jaroslav Kysela wrote:
On 29 Nov 2001, John Covici wrote:
I am using kernel 2.4.16-pre1 and the latest cvs alsa drivers, etc.,
but I still get wrong interrupt acknowledged from alsalib --
i needed this in order to compile alsa with kernel-2.5.1-pre3 + jens axboe patch
bio-4 :
diff -ru drivers/sound/alsa2/seq/seq_clientmgr.c drivers/sound/alsa/seq/seq_clientmgr.c
--- drivers/sound/alsa2/seq/seq_clientmgr.c Wed Nov 28 02:38:05 2001
+++ drivers/sound/alsa/seq/seq_clientmgr.c Wed
[ i thought sent a message about this earlier, but didn't see it ]
i was looking at the full duplex poll code that jaroslav provided
for josh. i noticed that it doesn't expect or require to find that
read+write are possible at the same time.
do we have any expectation of generally supporting
On Thu, 29 Nov 2001, Joshua Jacobs wrote:
I'm looking to get a sound card for my linux box which supports S/PDIF output
(Toslink preferred, but coax can work too). I've done alot of research
online, and I just can't find information about drivers supporting sound
card's digital outputs.
background: afaik, with the ice1712 for example it is possible to
run two or more cards in sync. will this be as simple as calling
snd_pcm_open for n streams, and snd_pcm_link (stream[0]) for
streams [1, n - 1]?
no, i don't think that's the plan. you use the multi PCM device type
in an
Er... do you mean...
ftp://ftp.alsa-project.org/pub/manuals/
?
- Tom.
- Original Message -
From: Paul Davis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 29, 2001 6:01 PM
Subject: [Alsa-devel] where are the reference files we have?
there's a hidden link
Hello
With the following card: -
YMF744 - Yamaha DS-XG PCI (YMF744) (ymfpci driver)
Why does: -
tmp = snd_pcm_hw_params_set_period_size_near(this-audio_fd, params,
period_size, 0);
give tmp=257 no matter what value you give period_size ?
Is the period_size fixed on this card?
Cheers
James
What more info can I provide?
_J
In the new year, Jeremy Hall wrote:
Here is a segment of my .asoundrc.
pcm_slave.rme9652_s {
pcm rme9652_0
}
pcm.rme9652_1 {
type hw
card 1
}
ctl.rme9652_1 {
type hw
card 1
}
pcm.rme9652_0 {
type hw
On Thu, 29 Nov 2001, James Courtier-Dutton wrote:
Source code: -
err=snd_pcm_open(this-audio_fd, pcm_device, direction, open_mode);
if(err 0 ) {
printf (audio_alsa_out: snd_pcm_open() failed: %s\n,
snd_strerror(err));
Output:
snd_pcm_open() failed: -22
Where can I find out info
In message [EMAIL PROTECTED]you write:
dave willis wrote:
On Thu, 29 Nov 2001, Abramo Bagnara wrote:
Q: with the ice1712 it is possible to run two or more cards in sync
A: Yes, if you're not thinking to share the same clock chip (i.e. some
drift is possible).
why can't i share the
Q: with the ice1712 it is possible to run two or more cards in sync
A: Yes, if you're not thinking to share the same clock chip (i.e. some
drift is possible).
My interpretation: two cards will drift. or something. can you be more
clear about what you mean? they will drift if you do use the same
Paul Davis wrote:
Q: with the ice1712 it is possible to run two or more cards in sync
A: Yes, if you're not thinking to share the same clock chip (i.e. some
drift is possible).
My interpretation: two cards will drift. or something. can you be more
clear about what you mean? they will
On Thu, 29 Nov 2001, Paul Davis wrote:
It looks like that the capture direction receives an interrupt before the
capture pointer has reached the period size boundary. You can increase the
insterrupt delay, something like this:
i'll check on that, but i don't think thats what happened above.
23 matches
Mail list logo
