On a Slackware 7.0 system, kernel 2.2.23 I have the following
situation:
alsa-0.9-rc7 works (driver, lib, tools).
Due to some isapnp related problems, Takashi Iwai sent me a patch and
asked me to try in on the cvs version. While I still have problems with
the driver part, when I tried to
Hi,
At Tue, 4 Mar 2003 19:35:35 -0400,
mjander wrote:
Hi,
I started writing a new driver for the Aureal Vortex soundcards.
wow, how did you get hardware information?
Now the howto is pretty good, and the basic stuff is nearly
complete, but
how do i integrate my driver into the
At 05 Mar 2003 00:02:30 +,
Bob Ham wrote:
Hi all,
The new pcm_jack thing presents a bit of a chicken and egg problem; I
just compiled alsa-lib twice because jack depends on alsa-lib and if you
configure alsa-lib with jack support, it depends on jack.
yep.
Would it be
possible for
On Wed, 2003-03-05 at 00:22, Paul Davis wrote:
This is a new version of the previous patch, but now also includes:
* use of udelay to force timed loops rather than count-based loops
* fix hdsp_is_9652()
* don't include unnecessary playback mixer controls for Multiface
*
- removed old module name snd-usb-midi from messages
- use snd_printk
- improved debugging output
Index: alsa-kernel/usb/usbmidi.c
===
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbmidi.c,v
retrieving revision 1.19
diff -u -r1.19
Bob Ham [EMAIL PROTECTED] wrote:
The new pcm_jack thing presents a bit of a chicken and egg problem; I
just compiled alsa-lib twice because jack depends on alsa-lib and if you
configure alsa-lib with jack support, it depends on jack. Would it be
possible for pcm_jack to be distributed
At Wed, 5 Mar 2003 10:11:57 +0100,
Maarten de Boer wrote:
Bob Ham [EMAIL PROTECTED] wrote:
The new pcm_jack thing presents a bit of a chicken and egg problem; I
just compiled alsa-lib twice because jack depends on alsa-lib and if you
configure alsa-lib with jack support, it depends on
I seem to have problems opening many devices quickly.
I use Mandrake 9, kernel 2.4.19-16mdkenterprise and
gcc-3.2.1 (GCC) 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)
When I do this:
x=32
while [ $x -ne 0 ]
do
let x=x-1
aplay /usr/share/sounds/phone.wav bomb.$x 21
done
I get a large
On Wed, 5 Mar 2003, alfp wrote:
Also, dmesg gives me
Unable to handle kernel NULL pointer dereference at virtual address 0008
printing eip:
f8b410b7
*pde =
Oops: 0002
CPU:0
EIP:0010:[f8b410b7]Not tainted
EFLAGS: 00010296
eax: f6384bd8 ebx: ecx:
On Wed, 2003-03-05 at 10:02, Thomas Charbonnel wrote:
I'm experiencing complete system lockups with this, in every possible
situation:
* cold boot
* reboot
* post boot module insertion
I did power off the card after updating, so the firmware has to be
loaded.
I get no message from the
Hi,
At 04 Mar 2003 21:47:34 -0500,
jfm3 wrote:
I think snd-serialmidi is broken for MS-124W MIDI interfaces in MB mode,
and that it has something to do with running status not being handled
correctly.
You need my patch, which I posted previously, to get MB mode working at
all.
the patch
On Tue, Mar 04, 2003 at 01:38:32PM +0100, Jordi Mallach wrote:
The Debian BTS has a few bugs against alsa-utils and alsa-driver. I
promised to forward them a few weeks ago, but have had no time to do
so...
We'll try our best to have a report written by tomorrow night.
Damn, forgot to say, if
On Wed, 5 Mar 2003, Andrei Boros wrote:
On a Slackware 7.0 system, kernel 2.2.23 I have the following
situation:
alsa-0.9-rc7 works (driver, lib, tools).
Due to some isapnp related problems, Takashi Iwai sent me a patch and
asked me to try in on the cvs version. While I still have
is anybody else using gcc 3.2.2 to compile their kernel and ALSA CVS?
i switched in the last couple of days, and have found:
* just trying to load wavefront driver causes lockup without oops message.
* use of trident driver causes oops whenever used.
i haven't tried the hammerfall/hdsp
Even stranger then .. when I did my last CVS update.. the mtpav driver
was one that did update... that is why I rechecked behaviour.. however I
did not use the panic button last time .. so maybe I am at fault
On Tue, 2003-03-04 at 01:56, Takashi Iwai wrote:
At 03 Mar 2003 14:51:15 +1100,
Allan
At Wed, 5 Mar 2003 07:42:44 -0500,
Paul Davis wrote:
is anybody else using gcc 3.2.2 to compile their kernel and ALSA CVS?
i switched in the last couple of days, and have found:
* just trying to load wavefront driver causes lockup without oops message.
* use of trident driver causes
If I try to get out of hanged state with the magic sysrq sigterm or
sigkill sequence, I get a flood of snd_printk messages from the
hdsp_fifo_wait(...) function in hdsp.c (line 501), with count = 127.
There are two places where hdsp_fifo_wait is called with count = 127:
hdsp_write_gain (line 550)
in short, i am confused :) :(
but ... help is at hand. i checked my mail archives:
The fifo status counts the number of words waiting in the FIFO. A value of
128 means that the fifo is full. 0 means the fifo is empty.
OK, so this means that
hdsp_fifo_wait (hdsp, 0, some_count);
is
Paul Davis wrote:
did you compile the kernel itself with the same gcc?
the combination of gcc-2.x and gcc-3.x on the kernel space will likely
cause oops.
no, i knew about that issue, and thats why i had to recompile
everything. i am tempted to go back to my older ALSA CVS tree (i
tar'ed it
Hi,
0.9 is nearly perfect, but the way of reporting bugs isn't so. Maybe we
should remove those links to sourceforge's bugtracking system and create a
mailling list like alsa-bug instead or redirect them to alsa-user or
anything else which is more effective.
But to offer sourceforge's
On Wed, 5 Mar 2003, Martin Langer wrote:
Hi,
0.9 is nearly perfect, but the way of reporting bugs isn't so. Maybe we
should remove those links to sourceforge's bugtracking system and create a
mailling list like alsa-bug instead or redirect them to alsa-user or
anything else which is more
-Forwarded Message-
From: alfp [EMAIL PROTECTED]
To: Erik Inge Bolsø [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] crash with rc8
Date: 05 Mar 2003 14:08:03 +0200
Sending the output as is.
alf
BTW, I changed
/lib/modules/2.4.19-16mdkenterprise/build/include/linux/version.h
to
OK, so this means that
hdsp_fifo_wait (hdsp, 0, some_count);
is waiting till the FIFO is empty. by contrast,
hdsp_fifo_wait (hdsp, 127, some_count);
waits till there is 1 word available in the FIFO, meaning that we can
write to it.
How is that we can write to it if it is
At 05 Mar 2003 16:24:37 +0200,
alfp wrote:
-Forwarded Message-
From: alfp [EMAIL PROTECTED]
To: Erik Inge Bols [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] crash with rc8
Date: 05 Mar 2003 14:08:03 +0200
Sending the output as is.
alf
BTW, I changed
On 5 Mar 2003, alfp wrote:
Trace; f8b561a3 [snd-pcm]snd_pcm_lib_malloc_pages+d3/e0
Code; f8b410b7 [snd-page-alloc]snd_dma_alloc_pages+17/e0
Please, try this patch (already in CVS):
diff -u -r1.19 pcm_memory.c
--- pcm_memory.c28 Feb 2003 14:29:19 - 1.19
+++ pcm_memory.c
On Wed, 2003-03-05 at 15:41, Paul Davis wrote:
i agree. i can't see why it doesn't, unless the LONG_WAIT delays us
for so long that it looks like a freeze ...
It doesn't, as after hitting the magic sysrq sigterm sequence I can see
the hdsp_fifo_wait's snd_printks appear on a regular basis
Hi,
Another question... :)
The Aureal Vortex has Scatter Gather DMA's for each audio channel.
But these SG DMA
support only max 4 pages. Each page can have a programable size of
upto 4 KB.
I was studying the ALSA SG scheme and it doesnt seme to fit into
the aureal vortex
SG buffer scheme,
On Wed, 2003-03-05 at 15:41, Paul Davis wrote:
i agree. i can't see why it doesn't, unless the LONG_WAIT delays us
for so long that it looks like a freeze ...
It doesn't, as after hitting the magic sysrq sigterm sequence I can see
the hdsp_fifo_wait's snd_printks appear on a regular basis
At Wed, 5 Mar 2003 12:09:21 -0400,
mjander wrote:
Hi,
Another question... :)
The Aureal Vortex has Scatter Gather DMA's for each audio channel.
But these SG DMA
support only max 4 pages. Each page can have a programable size of
upto 4 KB.
I was studying the ALSA SG scheme and it
On Wed, 5 Mar 2003, mjander wrote:
Hi,
Another question... :)
The Aureal Vortex has Scatter Gather DMA's for each audio channel.
But these SG DMA
support only max 4 pages. Each page can have a programable size of
upto 4 KB.
I was studying the ALSA SG scheme and it doesnt seme to fit
On Wed, 2003-03-05 at 17:34, Paul Davis wrote:
eh? if it returns any non-zero value, we return from
hdsp_initialize_firmware() with -EIO, surely?
You're perfectly right, sorry, I've been mixing things up... :)
I guess a reason for it was that getting all those snd_printks from
hdsp_fifo_wait
I don't see a problem here. The PAGE_SIZE is 4kB for i386. Simply
follow the code in the via82xx driver and limit the maximum count of
periods to 4.
This is easy solution, but a bit limiting. For example cs4281 supports max 2
periods. It is rather hard to work with it. There is a patch for
At Wed, 5 Mar 2003 09:52:49 -0500,
Ivica Bukvic wrote:
Hi all,
A while ago I posted this message, although mixed with some other false
assumptions of mine -- apologies for my ignorance( see:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg05286.ht
ml thread) and then did the same thing
is anybody else using gcc 3.2.2 to compile their kernel and ALSA CVS?
I'm currently using gcc-3.2 (default redhat compiler for 8.0- not 3.2.2,
I know) for a preliminary planet ccrma kernel. I'm currently running it
in my laptop and a couple other computers. I did not have any problems
so far
Hi all,
A while ago I posted this message, although mixed with some other false
assumptions of mine -- apologies for my ignorance( see:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg05286.ht
ml thread) and then did the same thing just a couple days ago with the
whole output log as requested
At 04 Mar 2003 19:01:24 -0800,
Fernando Pablo Lopez-Lezcano wrote:
lists about this and to do it cleanly it would be nice to have available
in /proc/asound the list of modules currently loaded. That is not
available today (I think Takashi said he might add that).
cat
Hi all,
I've just released compilation fixes for driver and library. The
main change in library is that the pcm jack plugin is separated now and
must be build manually in the alsa-lib/src/pcm/ext directory to avoid
circular dependency jack - alsa-lib. The jack plugin installs itself to
Hi,
I know this is the developers list but this problem is really odd and it
seems to me it fits better in this ML.
Here is the problem. I am the author of the eMoviX package, a micro
Linux distro that makes a CD able to boot and autoplay [with MPlayer]
all audio/video files it contains.
My hw
Hi,
I'm sorry to report that I've been unable to get alsa to build the
snd-sbawe driver with 2.5.64. Both the kernel's version and 0.9.0rc8
fail. I've attached the output of both build attempts.
Bob
--
Bob Ham [EMAIL PROTECTED]
make[1]: Entering directory
Thanks! I started working on differentiating in the alsasound alsa
startup script between a full start (all modules are loaded when
alsasound executes) and a partial start (some of the modules are already
loaded when alsasound executes and it has to load the rest).
The first naive
On Wed, 5 Mar 2003, Roberto De Leo wrote:
Hi,
I know this is the developers list but this problem is really odd and it
seems to me it fits better in this ML.
Here is the problem. I am the author of the eMoviX package, a micro
Linux distro that makes a CD able to boot and autoplay [with
It works now, thanks a million!
alf
On Wed, 2003-03-05 at 16:55, Jaroslav Kysela wrote:
On 5 Mar 2003, alfp wrote:
Trace; f8b561a3 [snd-pcm]snd_pcm_lib_malloc_pages+d3/e0
Code; f8b410b7 [snd-page-alloc]snd_dma_alloc_pages+17/e0
Please, try this patch (already in CVS):
diff -u
On Thu, 6 Mar 2003, Ivica Bukvic wrote:
Hi all,
I have this small question:
Is it possible (I presume it is) to alter mixer settings in Alsa by
invoking some kind of a system call using shell (i.e. how the RME hdsp
can have its stuff altered)?
Use amixer.
If so, what is the range of
alsasound script calls alsactl and card-specific scripts (if any).
this should be avoided in the case of partial load.
Yes, I took care of executing them just for the cards that had been
loaded.
IIRC, modprobe returns 0 even if called with the existing module.
(if the load failed,
44 matches
Mail list logo
