On Tue, 6 Apr 2004, Tom Browne wrote:
Clemens Ladisch wrote:
state: PREPARED
The pcm isn't (yet) running.
avail : 5
And the buffer is almost full. snd_pcm_writei blocks because it
cannot write more data to the buffer, probably because the transfer
threshold is too high.
Jaroslav Kysela wrote:
alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
err = snd_pcm_hw_params_set_period_time_near(handle, params,
alsa_period_time, dir);
alsa_period_size = snd_pcm_hw_params_get_period_size(params, dir);
...
err =
On Tue, 6 Apr 2004, Tom Browne wrote:
Jaroslav Kysela wrote:
alsa_buffer_size = snd_pcm_hw_params_get_buffer_size(params);
err = snd_pcm_hw_params_set_period_time_near(handle, params,
alsa_period_time, dir);
alsa_period_size = snd_pcm_hw_params_get_period_size(params, dir);
...
Jaroslav Kysela wrote:
Which gives threshold = 6552 from buffer=6553, period=3276...
exactly the same value as the code I was already using gives! What
else am I missing from the garish red and yellow blocks of WinDiff?
Then it really appears like a bug. Could you add snd_pcm_dump() call
Am Dienstag 06 April 2004 02:10 schrieb Rui Nuno Capela:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6 kernel tree, and already tested with 2.6.4 and
latest 2.6.5.
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with snddevices.sh
In /proc/asound i have the
On Tue, 6 Apr 2004 16:44:56 +0530
Pavana Sharma [EMAIL PROTECTED] wrote:
Hi,
I am running a test application on my alsa driver for arm
platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have
Hi,
chekout these versions ..I am using,
which version of alsa-drivers do you use [cat /proc/asound/version]?
Advanced Linux Sound Architecture Driver Version 1.0.2c (Thu Feb 05 15:41:49
2004 UTC).
which verison of alsa-utils do you use [aplay --version]
aplay: version 1.0.3 by Jaroslav
On Tue, 6 Apr 2004, Pavana Sharma wrote:
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with
Am Dienstag 06 April 2004 12:52 schrieb Karsten Wiese:
Am Dienstag 06 April 2004 02:10 schrieb Rui Nuno Capela:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6
Karsten Wiese wrote:
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
FYI, I'm stick with 2.6 kernel tree, and already tested with 2.6.4 and
latest 2.6.5.
My way of building the kernel
hi Jaroslav,
This file is present. The only other thing which I wanted to bring
into your notice is that the file system we are using is a busybox file
system, with no bash. Instead it has smaller shell ash. Will that make a
difference.
And this file /usr/share/alsa/alsa.conf is only
On Tue, 6 Apr 2004, Gupta, Kshitij wrote:
hi Jaroslav,
This file is present. The only other thing which I wanted to bring
into your notice is that the file system we are using is a busybox file
system, with no bash. Instead it has smaller shell ash. Will that make a
difference.
No,
Pavana Sharma wrote:
Hi,
I am running a test application on my alsa driver for arm platform.Driver
is statically built.
The test application calls the snd_pcm_open.
With device hw:0,0
At the target I have created sound driver files with snddevices.sh
In
Pavana Sharma wrote:
ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
Please show the output of aplay -l and aplay -L.
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by
I wrote:
I think I'll write a quirk for this ...
Please try the attached patch.
HTH
Clemens
diff -urN alsaold/alsa-kernel/usb/usbaudio.c alsa/alsa-kernel/usb/usbaudio.c
--- alsaold/alsa-kernel/usb/usbaudio.c Tue Mar 30 13:51:30 2004
+++ alsa/alsa-kernel/usb/usbaudio.c Tue Apr 6 13:20:36
On Tue, 6 Apr 2004, Brian Furey wrote:
Hi all,
i'm running the alsa-driver-1.0.0. Im using it with
the OpenH323 application. Packets are transmitted or
received in 32 millisecond intervals or multiples of
32 millisecond intervals.
For example using the G711 codec, packets are
Jaroslav,
Busy system cant explain something as consequent as this.
When the packet size being transmitted is 30 msecs(240bytes) or 32 msecs(240bytes), the OpenH323 app sends packets every 32 msecs.
When the packet size is 80 msecs(132 bytes), the OpenH323 app sends packets at alternate intervals
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
Attached diff fixed it here.
Please verify.
CU
Index: alsa-driver/usb/usx2y/usbusx2y.c
On Tue, 6 Apr 2004, Clemens Ladisch wrote:
I wrote:
I think I'll write a quirk for this ...
Please try the attached patch.
Sorry, don't have lots time now, I only applied the patch, loaded the
module, pluged in the device ... result is attached.
Unfortunately I'm (still) not familar with
Karsten Wiese
Now comes the weird part. No, I couldn't get it to work unless I set
--with-debug=full on configure line. And I've tested several times,
believe me.
Attached diff fixed it here.
Please verify.
CU
First try and it works, that is without debug enabled.
Thankful.
--
I can't find any way to detect the running ALSA version, for diagnostic
purposes. It can't be derived from the library name, which doesn't seem
to change (it's always libasound.so.2.0.0 here, which has no relation
to the actual version).
It's frustrating to receive bug reports like
I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo
Hi Jaroslav,
Please commit this with comments
- US224 support
- FIX for build without CONFIG_SND_DEBUG
Thanks,
Karsten
Index: usb/usx2y/usX2Yhwdep.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usX2Yhwdep.c,v
Glenn Maynard wrote:
On Tue, Apr 06, 2004 at 05:04:34PM -0400, Paul Davis wrote:
I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
That's the driver version, which I'm already logging. Like I said, I
want the alsa-lib version that's being linked
On Tue, Apr 06, 2004 at 11:16:17PM +0100, James Courtier-Dutton wrote:
cat /usr/include/alsa/version.h tells you the currently installed version.
Nope. That only works if the development files are installed; on user
systems, they usually aren't. I can't simply #include it; that'll tell
me
agreed. but its much more likely to be something about the cardbus
support under linux than the hdsp driver, and neither side (the
cardbus people or us hdsp people) knows the other side at all.
to figure that out, someone who knows what's going on in the hdsp driver
has to tell the pcmcia guys,
Despite the indifference to this issue, I thought it only fair to say that
switching to mmap seems to have stopped the problem from occuring.
- Tom.
Tom Browne wrote:
Hi all,
I am having serious trouble with ALSA using the poll method as shown
in the pcm.c test app...
Under certain
Tom Browne wrote:
Under certain conditions (yet to be established properly - it doesn't
happen every single time) with this ICE1712 card (DSP24),
snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when this happens?
(see /proc/asound/cardX/pcm0p/*)
Patrick Boettcher wrote:
I'm using a usbsnoop program to do some basic sniffing. Logs are
really big :/.
Try to play some 0.01-seconds wave file, and don't connect any other
USB devices.
After plugging in, the device shows like this in /proc/bus/usb/devices:
I: If#= 0 Alt= 0 #EPs= 0
John H. wrote:
see, this is what is weird, it worked last week, now it doesn't
work with exaudio or alsa! same errors!
Then it's not a problem of the sound driver.
cannot submit datapipe for urb 0, err = -38
-38 means not implemented. Probably some bug in the USB core in
your kernel.
Have
Clemens Ladisch wrote:
Tom Browne wrote:
Under certain conditions (yet to be established properly - it doesn't
happen every single time) with this ICE1712 card (DSP24),
snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when this happens?
(see
On Mon, Apr 05, 2004 at 06:00:01PM +0200, Clemens Ladisch wrote:
Patrick Boettcher wrote:
I'm using a usbsnoop program to do some basic sniffing. Logs are
really big :/.
Try to play some 0.01-seconds wave file, and don't connect any other
USB devices.
Check the log of the init phase.
Am Samstag 03 April 2004 03:24 schrieb Rui Nuno Capela:
I have news, and they're good this time.
After some juggling and persistance around compiling and patching the
snd-usb-usx2y module, I've finally got that dreaded INPUT MONITOR LED come
to light and, as Karsten rightly predicted,
Hi Clemens,
On Mon, 5 Apr 2004, Clemens Ladisch wrote:
Class 0xff means vendor-specific. This is not a USB Audio Device as
defined in the USB specifications.
Yes, I noticed it already, but I hoped that the vendor-specific part is
not so much vendor-specific, because they use a normal sound
Hi martin,
On Mon, 5 Apr 2004, Martin Langer wrote:
Check the log of the init phase. Perhaps the MBox needs a firmware download
at first.
I don't think so, as I wrote in the last answer to Clemens, the owner
told, me that he has to do a static firmware update (like a bios update).
And the
Hi,
small supplement:
http://vaasa.wi-bw.tfh-wildau.de/~pboettch/digi_mbox/
there is the 0.04-wave file played with winamp on WinXP, and the
appropriate log file produced by usbsnoop.
Patrick
---
This SF.Net email is sponsored by: IBM Linux
TAS1020:
http://focus.ti.com/docs/prod/folders/print/tas1020b.html
The TAS1020B integrated circuit (IC) is a universal serial bus (USB) peripheral
interface device designed specifically for applications that require isochronous
data streaming. Applications include digital speakers, which require
I don't use aplay to play the wav file but i use:
dd of=thefile.wav of=/dev/audio0
Do you think i should use aplay instead?
Is this the problem?
I'm trying to cross-compile the alsa-util library but, i have some trouble
at the compilation (configure: error: No linkable libasound was found).
Karsten Wiese wrote:
Am Samstag 03 April 2004 03:24 schrieb Rui Nuno Capela:
I have news, and they're good this time.
After some juggling and persistance around compiling and patching
the snd-usb-usx2y module, I've finally got that dreaded INPUT
MONITOR LED come to light and, as Karsten
On Sat, 3 Apr 2004, Mathieu Rondonneau wrote:
Hi all,
I have question according to the src pointer in the copy operator:
I'm writing an ALSA driver for the cogent CSB337 board. I'm testing the
driver but there are some problem.
I'm trying to playback a wav file, but i hear some strange
hi ico,
you did a good job in documenting this problem ...
TODO:
1) Log the Jack -R output (likely to be ridden with xrun's)
i suppose, we will get the same result as me, with jack complaining
about latency problems...
2) You tell me :-)
i suppose, what we are able to do, has been done ...
Hi,
This patch adds three new options to arecordmidi.
-d,--dump
Shows the received events as text on standard output.
-m,--metronome=client:port
Plays a metronome signal on the specified sequencer port.
Metronome sounds are played on
mainly the alsa guys who wrote the driver and know, how they access the
bus system and the hardware, have to tell the pcmcia guys, who know,
what's going on in the bus ... i CC'd this mail to the thomas
charbonnel, paul davis and winfried ritsch, who wrote or maintain this
driver and the
Hello ml,
I borrowed a DigiDesign MBox USB Audio device from a friend of mine, with
the aim to get this thing running in Linux. The Mbox is a high-quality
device for professional recording and playing back. (at least the product
description is promissing this)
I quite new to programming a
On Sun, Apr 04, 2004 at 05:46:35PM +0100, Rui Nuno Capela wrote:
damned. What's that? A dial-in account for spammers from netcabo.pt???
No dial-in but cable. Netcabo.pt is my ISP, and rncbc.org is just my own
dynamic DNS domain name, although it's IP address hasn't change for almost
more
Hi,
I have Asus pundit with sis7012 sound device and alsa 1.0.4 under Suse 9.0.
I've got advice how to use this 6 channel device as 3 stereo channels but
there seems something not to be right (it could be my mistake).
I have /etc/asound.conf :
pcm_slave.sis {
pcm hw:0
channels 6
rate 48000
On Sun, 04 Apr 2004 10:53:28 -0400
Paul Davis [EMAIL PROTECTED] wrote:
mainly the alsa guys who wrote the driver and know, how they access
the bus system and the hardware, have to tell the pcmcia guys, who
know, what's going on in the bus ... i CC'd this mail to the thomas
charbonnel, paul
and it HAS do be a software issue, since at least on ico's and my
machine, the hdsp works flawless with winxp ...
agreed. but its much more likely to be something about the cardbus
support under linux than the hdsp driver, and neither side (the
cardbus people or us hdsp people) knows the other
On Fri, 2 Apr 2004, Tim Hollingsworth wrote:
Thanks for your help so far Jaroslav.
I have taken another look at my project and now it's behaving
differently! It still won't go down to a period size of 128.
I have downloaded the example sine wave generator. It works with the
default
Hello all,
the 1.0.4 release is out. It contains mostly bug-fixes and
cleanups for the 2.6 kernel driver code.
alsa-driver
- recoded the configuration system to use 2.6 Kconfig files
as the dependency source
- updated/simplifies Kconfig files and Make files
- driver DMA API
Hi all,
I have question according to the src pointer in the copy operator:
I'm writing an ALSA driver for the cogent CSB337 board. I'm testing the
driver but there are some problem.
I'm trying to playback a wav file, but i hear some strange noise, not the
data corresponding to the wav file.
I
On Sat, 3 Apr 2004, Andrew Gaydenko wrote:
Just have tried 1.0.4. etc/init.d/alsasound restart gives:
Starting sound driver: snd-ice1724
/lib/modules/2.4.25-lck1/kernel/sound/acore/snd-pcm.o: unresolved symbol
snd_dma_alloc_pages_Rsmp_2cbfa9e2
At Sat, 3 Apr 2004 21:54:03 +0200 (CEST),
Jaroslav wrote:
On Sat, 3 Apr 2004, Andrew Gaydenko wrote:
Just have tried 1.0.4. etc/init.d/alsasound restart gives:
Starting sound driver: snd-ice1724
/lib/modules/2.4.25-lck1/kernel/sound/acore/snd-pcm.o: unresolved symbol
Thanks, rmmod snd-page-alloc have helped.
Andrew
=== On Sunday 04 April 2004 0:01, Takashi Iwai wrote: ===
At Sat, 3 Apr 2004 21:54:03 +0200 (CEST),
Jaroslav wrote:
On Sat, 3 Apr 2004, Andrew Gaydenko wrote:
Just have tried 1.0.4. etc/init.d/alsasound restart gives:
Starting
Rui,
damned. What's that? A dial-in account for spammers from netcabo.pt???
Still in hope that you're not the reason for my virus/worm traffic explosion.
Please, don't take it personally. It's only the spam/virus traffic I hate.
The reason, why you are on the IP blacklist is obvious: You are
Hi All,
still trying to get the hardware and software
runtime paramters of the driver...
In alsa-driver*/alsa-kernel/core there is the pcm.c
file.
There are 2 functions in this file
snd_pcm_substream_proc_hw_params_read
and
snd_pcm_substream_proc_sw_params_read
Both of these print out to
It shows the same light switching as is already implemented:
grep -n : 19 USB224_usbsnoop1.log
gives us pre INPUT MONITOR pressed
21501:: 19 00 1a 00 1b 00 1c 00 1d 11 1e 00 1f 00
and post
21941:: 19 00 1a 00 1b 00 1c 02 1d 01 1e 00 1f 00
the 8th
On Fri, 2 Apr 2004, Brian Furey wrote:
Hi All,
still trying to get the hardware and software
runtime paramters of the driver...
cat /proc/asound/card0/pcm0p/sub0/*
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound
Ron Cococcia wrote:
In a setup I'm working with, I have a motherboard (815 w/82801BA-ICH2) that
has an onboard/primary (00) AC97 codec (AD1885). We've been playing around
with adding a CNR card that would have a different/secondary (01) codec on
it (CS4299). [...]
The onboard chip is
alsa-lib contains a test program pcm.c that tests playback using all the
different modes alsa-lib can do.
Can we have a similar application for capture.
When developing an alsa driver, it works fine with arecord, but fails
with jackd, and the only difference is that arecord just uses
On Thu, Apr 01, 2004 at 11:23:00PM +0200, Jaroslav Kysela wrote:
On Thu, 1 Apr 2004, Martin Langer wrote:
It's still there, but this patch will fix it:
Index: alsa-driver/usb/Kconfig
===
RCS file:
On Sun, 28 Mar 2004 09:54:46 +0200 (CEST)
Jaroslav Kysela [EMAIL PROTECTED] wrote:
On Sat, 27 Mar 2004, Giuliano Pochini wrote:
I'm not sure if this is alsa's fault. It happens when I unload the module.
Yup, snd_gina24 is the driver I'm developing, but it also happens with
snd-powermac
see, this is what is weird, it worked last week, now it doesn't work with exaudio or
alsa! same errors!
line in works, but not pcm/oss.\
aplay file.wav does not work
after i ran aplay foo.wav i tried xmms, and it said
ALSA lib pcm_hw.c:1057:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
oh, play had gotten stuck on playing a gaim sound. it sticks until you kill it.
once killed, xmms says this
** WARNING **: alsa_free(): snd_pcm_start() failed: Broken pipe
ALSA lib pcm_hw.c:494:(snd_pcm_hw_start) SNDRV_PCM_IOCTL_START failed: Broken pipe
--- On Fri 04/02, John
and dmesg says
ALSA /tmp/alsa-driver-1.0.4rc2/usb/usbaudio.c:811: cannot submit datapipe for urb 0,
err = -38
ALSA /tmp/alsa-driver-1.0.4rc2/usb/usbaudio.c:811: cannot submit datapipe for urb 0,
err = -38
Debug: sleeping function called from invalid context at include/asm/semaphore.h:119
sorry, and it's uhci.
--- On Fri 04/02, John H. [EMAIL PROTECTED] wrote:
From: John H. [mailto: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Fri, 2 Apr 2004 16:45:41 -0500 (EST)
Subject: Re: [Alsa-devel] cannot submit datapipe for urb 0 on /dev/dsp
I have news, and they're good this time.
After some juggling and persistance around compiling and patching the
snd-usb-usx2y module, I've finally got that dreaded INPUT MONITOR LED come
to light and, as Karsten rightly predicted, playback has shown its ugly
head on my Tascam US-224. Hip, hip,
Hi all,
I've tinkered even further with the stuff and I do have my lspci and other
logs (will post them shortly). I've tried now runnning card with the
external Word Clock -- the results are the same (distortion persists).
At this point what I know for a fact:
1) Soundcard is distorted no
Am Mittwoch 31 März 2004 20:57 schrieb Martin Langer:
On Wed, Mar 31, 2004 at 09:10:17AM +0200, Jaroslav Kysela wrote:
On Wed, 31 Mar 2004, Karsten Wiese wrote:
..., which is not built.
this is for kernel 2.4.
/etc/asound/driver_args:
on this chip is philips logo ??? I think yes.
A1334
this is Philips UDA1334 2 channel DAC user for rear channel. On 2003
this is missing,
then rear channels must go out throught other chip (I think through
AC97).
Last try,
Change this in alsa-driver/alsa-kernel/pci/emu10k1/emufx.c
if
On Wed, 31 Mar 2004, James Courtier-Dutton wrote:
Is there any reason why this patch was not added to the alsa-lib cvs ?
It's better to put this information to configure.in?
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound
On Thu, 1 Apr 2004, Clemens Ladisch wrote:
I wrote:
Now the modules load. However, loading snd-usb-audio doesn't do
anything, and unloading and reloading it results in a crash or a hang.
Fixed. Apparently, snd-usb-audio has never been working on 2.2.x, and
nobody noticed ...
No
Hi,
I am new to ALSA driver impementation. I am registering the driver
interface functions like (probe,remove) using driver_register call. I expect
that the probe function will be called in which I am allocating sound card
and registering the card using snd_card_register. When I compile the sound
Hi,
I am new to ALSA driver impementation. I am registering the driver
interface functions like (probe,remove) using driver_register call. I expect
that the probe function will be called in which I am allocating sound card
and registering the card using snd_card_register. When I compile the
On Thu, 1 Apr 2004, Pavana Sharma wrote:
Hi,
I am new to ALSA driver impementation. I am registering the driver
interface functions like (probe,remove) using driver_register call. I expect
that the probe function will be called in which I am allocating sound card
and registering the card
Jaroslav Kysela wrote:
On Wed, 31 Mar 2004, James Courtier-Dutton wrote:
Is there any reason why this patch was not added to the alsa-lib cvs ?
It's better to put this information to configure.in?
No, because it selects which version of aclocal etc. that are used,
which is before configure.in
Hi
I have a problem concerning the format of the alsa lib
api. In the program I use the format
SND_PCM_FORMAT_S16_LE and therefore the data array is
decleared as a short int. But when the size of the
data array succeeds 512 I get a segmentation fault. To
me it looks like it's the readi() that
Am Dienstag 30 März 2004 22:51 schrieb Rui Nuno Capela:
the snd-usb-usx2y module. AFAICT it's not being included by
./configure --with-cards option, nor it gets built when one sets
--with-cards=all.
It is fixed in CVS now. Thanks.
Checked out today's alsa-driver-1.0.4rc2 where the
John H. wrote:
I get this error repeatedly
ALSA /tmp/alsa-driver-1.0.4rc2/usb/usbaudio.c:811:
cannot submit datapipe for urb 0, err = -38
whenever i try to use /dev/dsp now, and i can only get sound from line in.
i have kernel 2.6.4 and drivers 1.0.4rc2
What is in /proc/asound/cards?
Is
Karsten Wiese wrote:
the snd-usb-usx2y module. AFAICT it's not being included by
./configure --with-cards option, nor it gets built when one sets
--with-cards=all.
It is fixed in CVS now. Thanks.
Checked out today's alsa-driver-1.0.4rc2 where the missed snd-usb-usx2y
module gets built
On Thu, Apr 01, 2004 at 10:12:10AM +0200, Karsten Wiese wrote:
Am Mittwoch 31 März 2004 20:57 schrieb Martin Langer:
Yes! rm every file in alsa-driver, re-update from cvs and ./cvscompile.
There might be a simpler solution though...
Indeed. That solves it :) Thanks.
depmod: *** Unresolved
This might not be entirely alsa devel related, but it doesn't fit alsa user
either. I figured I'd ask anyway...
In a setup I'm working with, I have a motherboard (815 w/82801BA-ICH2) that
has an onboard/primary (00) AC97 codec (AD1885). We've been playing around
with adding a CNR card that
On Thu, 1 Apr 2004, Martin Langer wrote:
It's still there, but this patch will fix it:
Index: alsa-driver/usb/Kconfig
===
RCS file: /cvsroot/alsa/alsa-driver/usb/Kconfig,v
retrieving revision 1.2
diff -u -r1.2 Kconfig
---
On Thu, Apr 01, 2004 at 12:57:35PM +0100, James Courtier-Dutton wrote:
It's better to put this information to configure.in?
No, because it selects which version of aclocal etc. that are used,
which is before configure.in is even looked at.
I would recommend additionally using
Thank you very much. You have been teaching me a lot things. I will give it
a try.
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
On Wed, 31 Mar 2004, Russell King wrote:
On Wed, Mar 31, 2004 at 09:44:45AM +0200, Jaroslav Kysela wrote:
I think that the consensus was that using -nopage callback does not
make much sense for the DMA pages so remap_page_coherent_range() should be
used for this case when designed.
The
On Wed, Mar 31, 2004 at 10:10:22AM +0200, Jaroslav Kysela wrote:
Yes, but if we have at least one API solving this problem, the successors
should replace it completely. I think that it's much better solution than
having no way to support ARM or any other platforms with these problems in
From: p z [EMAIL PROTECTED]
Reply-To: p z [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] Need to know SBLive Chip difference
Date: Tue, 30 Mar 2004 14:09:20 +0200
Could you try change these lines in alsa-driver/alsa-
kernel/emu10k1/emufx.c
if
On Wed, 31 Mar 2004, Russell King wrote:
On Wed, Mar 31, 2004 at 10:10:22AM +0200, Jaroslav Kysela wrote:
Yes, but if we have at least one API solving this problem, the successors
should replace it completely. I think that it's much better solution than
having no way to support ARM or any
On Wed, 31 Mar 2004, Russell King wrote:
The correct interface is dma_mmap_coherent().
I'm actually tempted to provide dma_mmap_coherent() and just let
everyone else whinge and moan that the API doesn't meet their
expectations.
Thanks. Evolution is the best way.
BTW, ARM also needs the
On Wed, Mar 31, 2004 at 11:07:03AM +0200, Jaroslav Kysela wrote:
Do you see any reason to ommit this settings for some cases (including
for ISA bus)? I think that dma_alloc_coherent should offer consistent
API - thus mark all allocated pages as reserved for all cases.
That was another point I
On Wed, 31 Mar 2004, Russell King wrote:
I suggest we add a load of preprocessor junk into the ALSA core and
comment exactly _why_ its needed, thereby laying the reason completely
at the door of these ill-defined APIs where questions have been asked
and responses not been received.
I'm
On Wed, Mar 31, 2004 at 11:22:56AM +0200, Jaroslav Kysela wrote:
On Wed, 31 Mar 2004, Russell King wrote:
I suggest we add a load of preprocessor junk into the ALSA core and
comment exactly _why_ its needed, thereby laying the reason completely
at the door of these ill-defined APIs where
On Wed, Mar 31, 2004 at 10:29:06AM +0200, Jaroslav Kysela wrote:
On Wed, 31 Mar 2004, Russell King wrote:
Keeping the existing -nopage will not work - there is no way to get to
a struct page on ARM given the information available to the ALSA code.
Looking to arch/arm/mm/consistent.c -
On Wed, 31 Mar 2004, Clemens Ladisch wrote:
But now:
# modprobe snd
modprobe: Too deep recursion in module dependencies!
modprobe: Circular dependency? snd-page-alloc snd
snd_pci_compat_get_pci_driver() is called from
pci_compat_pm_callback() in misc.c. I think the 2.2.x CONFIG_APM
I
Thanks James,
i'm using the GSM-06.10 codec with my VoIP
application.The frame rate is 160 timestamp units or
20 millisecond frames.4 frames are added to a packet
and transmitted. Packets are transmitted at alternate
intervals of 64 and 96 milliseconds. This is due to
the soundcard driver and
Russell King wrote:
On Wed, Mar 31, 2004 at 11:22:56AM +0200, Jaroslav Kysela wrote:
On Wed, 31 Mar 2004, Russell King wrote:
I suggest we add a load of preprocessor junk into the ALSA core and
comment exactly _why_ its needed, thereby laying the reason completely
at the door of these
Greetings !
I have a brand new RME-9652 (Hammerfall HDSP Rev. 1.6)) hooked-up to the
two RME-AES 8i and 8o brackets which are mounted inside the computer. So,
I am not using any kind of external D/A converter.
Hardware is: Pentium IV CPU at 1.7 GHz, SCSI HD
Operative System is: LINUX Red Hat
The problem is that I cannot get the mixer to have any elements (or=20
elems as the alsamixer calls them) which thus makes the card un-openable=
=20
even with the alsamixer.
thats correct. the hdsp has no mixer that can be represented using
conventional mixer elements. there is nothing
501 - 600 of 10001 matches
Mail list logo
