date:20040406

Pedro Lopez-Cabanillas wrote:
 This patch adds three new options to arecordmidi.

Committed, with some changes.


Thanks,
Clemens




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] src pointer parameter in copy operator

On Mon, 5 Apr 2004, Mathieu Rondonneau wrote:

 I don't use aplay to play the wav file but i use:
 dd of=thefile.wav of=/dev/audio0

This is definitely wrong. The /dev/audio devices expect mu-Law
format at 8000Hz.

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] Bug in sis7012 driver - or probably I'm doing something wrong ?

Robert Rozman wrote:
 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.a {
 type plug
 slave.pcm ch12
 }

 pcm.b {
 type plug
 slave.pcm ch34
 }

 Now I do:

 - alsaplayer with mp3 file on device plug:a

a is already defined as a plug plugin on top of ch12, it's exactly
the same as plug:ch12.  Adding another plug layer (plug:plug:ch12)
wouldn't make much sense.

 - aplay -D plug:ch12 (funny is that plug:a doesn't work)
 - everything is ok and mixed properly

 - but if I start another alsaplayer on plug:b (probably also plug:c would be
 the same), then aplay produces sound that is interleaved in short chunks
 and also sound from alsaplayer on plug:b is also heard in addition to
 original mp3 and aplay sound.

Please try the a,b,c pcm devices without the plug: prefix.

Does it work if you run aplay on devices a and b?


Regards,
Clemens




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

Tom Browne wrote:
 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 /proc/asound/cardX/pcm0p/*)

 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.

How do you start the pcm?  If you're using the start threshold, it may
be too big, too.


HTH
Clemens




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] DigiDesign MBox USB Audio device

2004-04-06 Thread Patrick Boettcher

On Mon, 5 Apr 2004, Eliot Blennerhassett wrote:

 TAS1020:

 http://focus.ti.com/docs/prod/folders/print/tas1020b.html

 But I guess the exact features depend on firmware...

OK, I think this is the most difficult option which is possible?! What
should I do now, is reverse engineering possible at all? Analyse the
firmware?

What do you suggest?

Patrick


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] cannot submit datapipe for urb 0 on /dev/dsp access -extigy

John H. wrote:

 the usb 2.0 hub was at fault,. thanks!

I have heard rumors that the latest 2.6.5 kernel is supposed to have
support for playing audio data through 2.0 hubs to 1.x devices.


HTH
Clemens




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] DigiDesign MBox USB Audio device

Patrick Boettcher wrote:
 On Mon, 5 Apr 2004, Clemens Ladisch wrote:
  What sample rate/format uses 304000 bytes per second?

 I don't understand the question completely, what do you mean?

The descriptors say that the device can transfer up to 304000 bytes
per second in each direction.  What sample rate and formats does it
support?  (stereo 24 bits at 48 kHz would be 288000 bytes/s)

   2. Can I use somehow the i2c/cs8427.c?
  Probably not.  The CS8427 will be connected (via I2C) to some USB
  interface/controller chip.  Can you determine which one?

 TAS1020A, Texas Instrument USB Streaming Controller. I thought I have to
 talk to the sound chip directly and that the the usb chip is only
 for bus control?!

The USB chip manages communication on the bus, and contains an
embedded 8051(?)-compatible CPU which must be programmed to implement
the actual behaviour of the device (in this case, writing/reading
samples over the I2C bus).

 Beside of the a/d and d/a converter, there is only one bigger chip on the
 device board. It is an EEPROM, I suppose to take the firmware, the owner
 of the device told me, that sometimes he has to make a firmware update.

 What exactly does the firmware?

It's the code running on the TAS1020A's CPU.

  Sending/receiving sample data should work, but I guess this device
  needs vendor-specific commands to configure it.  These are control
  transfers, not isochronous; please look in the log file for them.

 There are only isochronous transfers (of course, there are only
 isoc-endpoints?) visible.

Each interface has an implicit control endpoint.

There are some control transfers in the UsbSnoop log, but those look
very much like standard USB Audio request.  It seems the device only
pretends to be vendor-specific.

I think I'll write a quirk for this ...


Regards,
Clemens




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

2004-04-06 Thread Tom Browne

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.

?!  See below...

 How do you start the pcm?  If you're using the start threshold, it may
 be too big, too.

The code is based on alsa-lib/test/pcm.c using the poll method, so if you
look at that, you'll see how most of the parameters are set in my code.  I
had to change to alsa_buffer_size-1 after upgrading to ALSA 0.9rc6 (I was
using rc2, if memory serves) otherwise it never started playing... it seems
something had changed in alsa-lib around this time.

 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 = snd_pcm_sw_params_set_start_threshold(handle, swparams,
alsa_buffer_size-1)
 err = snd_pcm_sw_params_set_avail_min(handle, swparams, alsa_period_size);

- Tom.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

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.
 
 ?!  See below...
 
  How do you start the pcm?  If you're using the start threshold, it may
  be too big, too.
 
 The code is based on alsa-lib/test/pcm.c using the poll method, so if you
 look at that, you'll see how most of the parameters are set in my code.  I
 had to change to alsa_buffer_size-1 after upgrading to ALSA 0.9rc6 (I was
 using rc2, if memory serves) otherwise it never started playing... it seems
 something had changed in alsa-lib around this time.
 
  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 = snd_pcm_sw_params_set_start_threshold(handle, swparams,
 alsa_buffer_size-1)

It's not correct and it was never correct, but the pcm.c was buggy, too.
Look to the latest version.

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

2004-04-06 Thread Tom Browne

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 = snd_pcm_sw_params_set_start_threshold(handle, swparams,
 alsa_buffer_size-1)
 It's not correct and it was never correct, but the pcm.c was buggy,
 too. Look to the latest version.

Running a file compare, I see only one line of significant difference
between the version in 0.9rc2 and 1.0.4 pcm.c...

 err = snd_pcm_sw_params_set_start_threshold(handle, swparams, (buffer_size
/ period_size) * period_size);

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?

Why does changing to mmap writes make the blocking problem go away?  And as
I said, the problem only has been made to occur at 88.2 and 96K sampling
rates...

- Tom.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

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);
  ...
   err = snd_pcm_sw_params_set_start_threshold(handle, swparams,
  alsa_buffer_size-1)
  It's not correct and it was never correct, but the pcm.c was buggy,
  too. Look to the latest version.
 
 Running a file compare, I see only one line of significant difference
 between the version in 0.9rc2 and 1.0.4 pcm.c...
 
  err = snd_pcm_sw_params_set_start_threshold(handle, swparams, (buffer_size
 / period_size) * period_size);
 
 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 just 
before the block occurs?

 Why does changing to mmap writes make the blocking problem go away?  And as
 I said, the problem only has been made to occur at 88.2 and 96K sampling
 rates...

mmap does never block

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] snd_pcm_writei not returning (?!?)

2004-04-06 Thread Tom Browne

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
 just before the block occurs?

Sure... but it doesn't seem to show any anomalies... I've also included the
matching status report from /proc...


state: PREPARED
trigger_time: 1081246741.324684000
tstamp  : 1081246792.298694000
delay   : 0
avail   : 8
avail_max   : 7229
-
hw_ptr  : 0
appl_ptr: 6545

--

Hardware PCM card 0 'Hoontech SoundTrack Audio DSP24' device 0 subdevice 0

Its setup is:
stream   : PLAYBACK
access   : RW_INTERLEAVED
format   : S32_LE
subformat: STD
channels : 10
rate : 88200
exact rate   : 88200 (88200/1)
msbits   : 24
buffer_size  : 6553
period_size  : 3276
period_time  : 37142
tick_time: 1000
tstamp_mode  : NONE
period_step  : 1
sleep_min: 0
avail_min: 3276
xfer_align   : 1
start_threshold  : 6552
stop_threshold   : 6553
silence_threshold: 0
silence_size : 0
boundary : 1717829632


 Why does changing to mmap writes make the blocking problem go away?
 And as I said, the problem only has been made to occur at 88.2 and
 96K sampling rates...
 mmap does never block

That'd explain why it doesn't halt like snd_pcm_writei, then... :)

... but if it was having to throw away data, surely wouldn't it drop out
when I swap in mmap?  Because it doesn't... snd_pcm_mmap_writei *seems* to
work perfectly...

I'm suspecting an off by one calculation error somewhere.

- Tom.



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] Re: Tascam US-224 progress report (was: USB224_usbsnoop1.log captured on WinXP)

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.

 My way of building the kernel modules is from stock tarball, and is pretty
 canonical, as literally as follows (all as root):

   tar -jxf alsa-driver-1.0.4.tar.bz2
   cd alsa-driver-1.0.4
   gzip -dc ../alsa-driver-1.0.4p1.patch.gz# see attachment
   ./configure --with-isapnp=no --with-sequencer=yes --with-oss=yes
 --with-cards=all --with-debug=full
   make
   make install

 As stated, the INPUT MONITOR LED does not get lit if I take out the clause
 --with-debug=full.

 How come?
You don't use --with-kernel option.
Are you shure ALSA build sees the correct linux-kernel source?
What distro are you using?
On some (i.e. fc1) you'd have to specify a special gcc like 
export CC=gcc32
befure ./configure.
I'm building a no debug ALSA here with a 2.6.5-aa1 kernel.
maybe I'll find something.

Cheers,
Karsten


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

[Alsa-devel] problem while opening device

2004-04-06 Thread Pavana Sharma

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 soundcard registered as card0 .
Can anyone give ideas where can be the problem ..??

this is the error msg I am getting..
snip---
ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0

FYI ..when I use

 cat test.raw  /dev/dsp

 is working.

Thanks
Pavana S



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] problem while opening device

2004-04-06 Thread Florian Schmidt

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 created sound driver files with
   snddevices.sh In /proc/asound i have the soundcard registered as
   card0 . Can anyone give ideas where can be the problem ..??
 
   this is the error msg I am getting..
 snip---
 ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
 
   FYI ..when I use
 
cat test.raw  /dev/dsp
 
is working.

I would think that this sounds like a version mismatch. How do i come to
this result? Well, alsamodules seem to be laoded fine [as you have
checked /proc/asound/cards]. Oss emu is working too [as you /dev/dsp
test shows]. The OSS emu [modules] don't interact with alsa-lib. But the
pcm-test program uses alsa-lib..

which version of alsa-drivers do you use [cat /proc/asound/version]?
which verison of alsa-utils do  you use [aplay --version]
which version of alsa-lib do you use? [$EDITOR
/usr/include/alsa/version.h]?

Flo

P.S.: oh i just see you use ARM. I have no idea, if that platform has
specific issues, so this post could be void afterall..

-- 
kT



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

RE: [Alsa-devel] problem while opening device

2004-04-06 Thread Pavana Sharma

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 Kysela [EMAIL PROTECTED]

which version of alsa-lib do you use? [$EDITOR
/usr/include/alsa/version.h]?
 SND_LIB_VERSION_STR 1.0.3

Thanks
Pavana S

-Original Message-
From: Florian Schmidt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004 5:11 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] problem while opening device


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 created sound driver files with
   snddevices.sh In /proc/asound i have the soundcard registered as
   card0 . Can anyone give ideas where can be the problem ..??

   this is the error msg I am getting..
 snip---
 ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
 
   FYI ..when I use

cat test.raw  /dev/dsp

is working.

I would think that this sounds like a version mismatch. How do i come to
this result? Well, alsamodules seem to be laoded fine [as you have
checked /proc/asound/cards]. Oss emu is working too [as you /dev/dsp
test shows]. The OSS emu [modules] don't interact with alsa-lib. But the
pcm-test program uses alsa-lib..

which version of alsa-drivers do you use [cat /proc/asound/version]?
which verison of alsa-utils do  you use [aplay --version]
which version of alsa-lib do you use? [$EDITOR
/usr/include/alsa/version.h]?

Flo

P.S.: oh i just see you use ARM. I have no idea, if that platform has
specific issues, so this post could be void afterall..

--
kT




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] problem while opening device

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 snddevices.sh
   In /proc/asound i have the soundcard registered as card0 .
   Can anyone give ideas where can be the problem ..??
 
   this is the error msg I am getting..
 snip---
 ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
 

/usr/share/alsa/alsa.conf is missing.

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] Re: Tascam US-224 progress report (was: USB224_usbsnoop1.log captured on WinXP)

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 kernel tree, and already tested with 2.6.4 and
  latest 2.6.5.
 
  My way of building the kernel modules is from stock tarball, and is
  pretty canonical, as literally as follows (all as root):
 
tar -jxf alsa-driver-1.0.4.tar.bz2
cd alsa-driver-1.0.4
gzip -dc ../alsa-driver-1.0.4p1.patch.gz  # see attachment
./configure --with-isapnp=no --with-sequencer=yes --with-oss=yes
  --with-cards=all --with-debug=full
make
make install
 
  As stated, the INPUT MONITOR LED does not get lit if I take out the
  clause --with-debug=full.
 
  How come?

 You don't use --with-kernel option.
 Are you shure ALSA build sees the correct linux-kernel source?
 What distro are you using?
 On some (i.e. fc1) you'd have to specify a special gcc like
   export CC=gcc32
 befure ./configure.
 I'm building a no debug ALSA here with a 2.6.5-aa1 kernel.
 maybe I'll find something.
Yes, same odd behavior here: built without --with-debug=full, 
nothing is sent from us428control to the us428. So your build process is 
propably ok.

Cheers,
Karsten


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] Re: Tascam US-224 progress report (was: USB224_usbsnoop1.log captured on WinXP)

2004-04-06 Thread Rui Nuno Capela

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 modules is from stock tarball, and is
 pretty canonical, as literally as follows (all as root):

   tar -jxf alsa-driver-1.0.4.tar.bz2
   cd alsa-driver-1.0.4
   gzip -dc ../alsa-driver-1.0.4p1.patch.gz   # see attachment
   ./configure --with-isapnp=no --with-sequencer=yes --with-oss=yes
 --with-cards=all --with-debug=full
   make
   make install

 As stated, the INPUT MONITOR LED does not get lit if I take out the
 clause --with-debug=full.

 How come?
 You don't use --with-kernel option.
 Are you shure ALSA build sees the correct linux-kernel source?

My current linux kernel source is always under /usr/src/linux, a pretty
standard place. I always build the alsa-driver's under and for the current
running kernel.

But as I said, the issue is only triggered by whether the --with-debug
configure option is there. The build environment remains exactly the same,
so I think.

 What distro are you using?

SUSE 9.0 on a desktop, and Mandrake 10.0 on a laptop. The results are, not
surprisingly, the same (the build steps are the same too, without
--with-kernel option).

 On some (i.e. fc1) you'd have to specify a special gcc like
   export CC=gcc32
 befure ./configure.

Is there any issue with gcc 3.3, which I think is the one I'm using ?


 I'm building a no debug ALSA here with a 2.6.5-aa1 kernel.
 maybe I'll find something.


Thanks for the patience.
-- 
rncbc aka Rui Nuno Capela
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

RE: [Alsa-devel] problem while opening device

2004-04-06 Thread Gupta, Kshitij

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 meant to be read ??? 
Some other points :
- Alsa driver is statically loaded into the kernel.  We are also able to see
that /proc/asound directory is being populated correctly.
- the /dev/snd nodes are like this 
 
hwC0D0 midiC0D1   midiC2D2   pcmC0D1p   pcmC1D2c   pcmC2D2p   pcmC3D3c
hwC0D1 midiC0D2   midiC2D3   pcmC0D2c   pcmC1D2p   pcmC2D3c   pcmC3D3p
hwC0D2 midiC0D3   midiC2D4   pcmC0D2p   pcmC1D3c   pcmC2D3p   pcmC3D4c
hwC0D3 midiC0D4   midiC2D5   pcmC0D3c   pcmC1D3p   pcmC2D4c   pcmC3D4p
hwC1D0 midiC0D5   midiC2D6   pcmC0D3p   pcmC1D4c   pcmC2D4p   pcmC3D5c
hwC1D1 midiC0D6   midiC2D7   pcmC0D4c   pcmC1D4p   pcmC2D5c   pcmC3D5p
hwC1D2 midiC0D7   midiC3D0   pcmC0D4p   pcmC1D5c   pcmC2D5p   pcmC3D6c
hwC1D3 midiC1D0   midiC3D1   pcmC0D5c   pcmC1D5p   pcmC2D6c   pcmC3D6p
hwC2D0 midiC1D1   midiC3D2   pcmC0D5p   pcmC1D6c   pcmC2D6p   pcmC3D7c
hwC2D1 midiC1D2   midiC3D3   pcmC0D6c   pcmC1D6p   pcmC2D7c   pcmC3D7p
hwC2D2 midiC1D3   midiC3D4   pcmC0D6p   pcmC1D7c   pcmC2D7p   seq
hwC2D3 midiC1D4   midiC3D5   pcmC0D7c   pcmC1D7p   pcmC3D0c   timer

Do some older versions use hw00 as nodes ???

- Is there a way around these aliases hw:0,0 like can;t we open the
device without this alias ???

warm regards
-kshitij

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jaroslav
Kysela
Sent: Tuesday, April 06, 2004 6:20 PM
To: Pavana Sharma
Cc: [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] problem while opening device


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 snddevices.sh
   In /proc/asound i have the soundcard registered as card0 .
   Can anyone give ideas where can be the problem ..??
 
   this is the error msg I am getting..
 snip---
 ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0
 

/usr/share/alsa/alsa.conf is missing.

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

RE: [Alsa-devel] problem while opening device

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, ALSA library does not use shell.

 And this file /usr/share/alsa/alsa.conf is only meant to be read ??? 

It contains the definitions for the PCM device names.

 - Is there a way around these aliases hw:0,0 like can;t we open the
 device without this alias ???

hw:0,0 is logical device name for alsa-lib only. The definition for hw
PCM device is stored in the alsa.conf file which should be accessible
for alsa-lib or you have to move the definition in your local ~/.asoundrc 
configuration file.

Also note that you may override the location of this file with 
ALSA_CONFIG_PATH environment variable. For example:

export ALSA_CONFIG_PATH=/etc/alsa/alsa.conf

To include more files:

export ALSA_CONFIG_PATH=/etc/alsa/alsa.conf:/etc/alsa/alsa1.conf

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] problem while opening device

2004-04-06 Thread James Courtier-Dutton

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 /proc/asound i have the soundcard registered as card0 .
Can anyone give ideas where can be the problem ..??
this is the error msg I am getting..
snip---
ALSA lib pcm.c:1947:(snd_pcm_open_noupdate) Unknown PCM hw:0,0

FYI ..when I use
	 cat test.raw  /dev/dsp

	 is working.

Thanks
Pavana S
cat /proc/asound/cards

Sounds like your kernel is using low level oss drivers and not alsa for 
that card.

Cheers
James


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] problem while opening device

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 Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] DigiDesign MBox USB Audio device

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 2004
@@ -2640,6 +2640,7 @@
struct audioformat *fp;
struct usb_host_interface *alts;
int stream, err;
+   int *rate_table = NULL;
 
fp = kmalloc(sizeof(*fp), GFP_KERNEL);
if (! fp) {
@@ -2647,16 +2648,30 @@
return -ENOMEM;
}
memcpy(fp, quirk-data, sizeof(*fp));
+   if (fp-nr_rates  0) {
+   rate_table = kmalloc(sizeof(int) * fp-nr_rates, GFP_KERNEL);
+   if (!rate_table) {
+   kfree(fp);
+   return -ENOMEM;
+   }
+   memcpy(rate_table, fp-rate_table, sizeof(int) * fp-nr_rates);
+   fp-rate_table = rate_table;
+   }
+
stream = (fp-endpoint  USB_DIR_IN)
? SNDRV_PCM_STREAM_CAPTURE : SNDRV_PCM_STREAM_PLAYBACK;
err = add_audio_endpoint(chip, stream, fp);
if (err  0) {
kfree(fp);
+   if (rate_table)
+   kfree(rate_table);
return err;
}
if (fp-iface != get_iface_desc(iface-altsetting[0])-bInterfaceNumber ||
fp-altset_idx = iface-num_altsetting) {
kfree(fp);
+   if (rate_table)
+   kfree(rate_table);
return -EINVAL;
}
alts = iface-altsetting[fp-altset_idx];
diff -urN alsaold/alsa-kernel/usb/usbquirks.h alsa/alsa-kernel/usb/usbquirks.h
--- alsaold/alsa-kernel/usb/usbquirks.h Thu Mar 18 21:45:03 2004
+++ alsa/alsa-kernel/usb/usbquirks.hTue Apr  6 13:44:07 2004
@@ -838,6 +886,72 @@
.product_name = PHASE 26,
.ifnum = 3,
.type = QUIRK_MIDI_STANDARD_INTERFACE
+   }
+},
+
+{
+   USB_DEVICE(0x0dba, 0x1000),
+   .driver_info = (unsigned long)  (const snd_usb_audio_quirk_t) {
+   .vendor_name = Digidesign,
+   .product_name = MBox,
+   .ifnum = QUIRK_ANY_INTERFACE,
+   .type = QUIRK_COMPOSITE,
+   .data = (const snd_usb_audio_quirk_t[]) {
+   {
+   /*
+* The MBox has both endpoints in interface 1,
+* but we need one interface for each
+* direction, so use interface 0 here.
+*/
+   .ifnum = 0,
+   .type = QUIRK_AUDIO_FIXED_ENDPOINT,
+   .data =  (const struct audioformat) {
+   .format = SNDRV_PCM_FORMAT_S24_3BE,
+   .channels = 2,
+   .iface = 1,
+   .altsetting = 1,
+   .altset_idx = 1,
+   .attributes = EP_CS_ATTR_SAMPLE_RATE,
+   .endpoint = 0x81,
+   .ep_attr = EP_ATTR_ASYNC | 0x01,
+   .maxpacksize = 0x130,
+   .rates = SNDRV_PCM_RATE_44100 |
+   SNDRV_PCM_RATE_48000,
+   .rate_min = 44100,
+   .rate_max = 48000,
+   .nr_rates = 2,
+   .rate_table = (unsigned int[]) {
+   44100, 48000
+   }
+   }
+   },
+   {
+   .ifnum = 1,
+   .type = QUIRK_AUDIO_FIXED_ENDPOINT,
+   .data =  (const struct audioformat) {
+   .format = SNDRV_PCM_FORMAT_S24_3BE,
+   .channels = 2,
+   .iface = 1,
+   .altsetting = 1,
+   .altset_idx = 1,
+   .attributes = EP_CS_ATTR_SAMPLE_RATE,
+   .endpoint = 0x02,
+   .ep_attr = 0x01,
+   .maxpacksize = 0x130,
+   .rates = SNDRV_PCM_RATE_44100 |
+   SNDRV_PCM_RATE_48000,
+   .rate_min = 44100,
+   .rate_max =

Re: [Alsa-devel] alsa driver

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
 transmitted every 32 milliseconds. For the GSM-06.10
 codec, packets are transmitted at alternate intervals
 of 64 milliseconds or 96 milliseconds.
 Why is this?

Busy system?

Jaroslav

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] alsa driver

2004-04-06 Thread Brian Furey

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 of 64 msecs and 96 msecs.Both are multiples of 32 msecs.
Surely it's to do with the period size being added to the driver sending buffer. The thing is I have got all the info about the period size,no of periods ..etc but it's not adding up yet.

Brian.Jaroslav Kysela [EMAIL PROTECTED] wrote:
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 transmitted every 32 milliseconds. For the GSM-06.10 codec, packets are transmitted at alternate intervals of 64 milliseconds or 96 milliseconds. Why is this?Busy system?Jaroslav-Jaroslav Kysela <[EMAIL PROTECTED]>Linux Kernel Sound MaintainerALSA Project, SuSE Labs---This SF.Net email is sponsored by: IBM Linux TutorialsFree Linux tutorial presented by Daniel Robbins, President and CEO ofGenToo technologies. Le!
arn
everything from fundamentals to systemadministration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click___Alsa-devel mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/alsa-devel

Yahoo! Messenger - Communicate instantly..."Ping" your friends
today! Download Messenger Now

Re: [Alsa-devel] Re: Tascam US-224 progress report (was: USB224_usbsnoop1.log captured on WinXP)

  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
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usbusx2y.c,v
retrieving revision 1.8
diff -u -r1.8 usbusx2y.c
--- alsa-driver/usb/usx2y/usbusx2y.c	17 Feb 2004 15:28:31 -	1.8
+++ alsa-driver/usb/usx2y/usbusx2y.c	6 Apr 2004 16:51:22 -
@@ -118,7 +118,6 @@
 static void snd_usX2Y_usb_disconnect(struct usb_device* usb_device, void* ptr);
 static void snd_usX2Y_card_private_free(snd_card_t *card);
 
-#ifdef CONFIG_SND_DEBUG
 /* 
  * pipe 4 is used for switching the lamps, setting samplerate, volumes    
  */
@@ -128,14 +127,15 @@
 void snd_usX2Y_Out04Int(struct urb* urb)
 #endif
 {
+#ifdef CONFIG_SND_DEBUG
 	if (urb-status) {
 		int 		i;
 		usX2Ydev_t*	usX2Y = urb-context;
 		for (i = 0; i  10  usX2Y-AS04.urb[i] != urb; i++);
 		snd_printd(snd_usX2Y_Out04Int() usX2Y-Seq04=%i urb %i status=%i\n, usX2Y-Seq04, i, urb-status);
 	}
-}
 #endif
+}
 
 #ifndef OLD_USB
 void snd_usX2Y_In04Int(struct urb* urb, struct pt_regs *regs)
@@ -194,7 +194,7 @@
 int j, send = us428ctls-p4outSent + 1;
 if (send = N_us428_p4out_BUFS)
 	send = 0;
-for (j = 0; j  URBS_AsyncSeq; ++j)
+for (j = 0; j  URBS_AsyncSeq!err; ++j)
 	if (0 == usX2Y-AS04.urb[j]-status) {
 		us428_p4out_t *p4out = us428ctls-p4out + send;	// FIXME if more then 1 p4out is new, 1 gets lost.
 		usb_fill_bulk_urb(usX2Y-AS04.urb[j], usX2Y-chip.dev,
@@ -204,7 +204,7 @@
 #ifdef OLD_USB
 		usX2Y-AS04.urb[j]-transfer_flags = USB_QUEUE_BULK;
 #endif
-		usb_submit_urb(usX2Y-AS04.urb[j], GFP_ATOMIC);
+		err = usb_submit_urb(usX2Y-AS04.urb[j], GFP_ATOMIC);
 		us428ctls-p4outSent = send;
 		break;
 	}
Index: alsa-driver/usb/usx2y/usbusx2y.h
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usbusx2y.h,v
retrieving revision 1.3
diff -u -r1.3 usbusx2y.h
--- alsa-driver/usb/usx2y/usbusx2y.h	19 Jan 2004 18:43:28 -	1.3
+++ alsa-driver/usb/usx2y/usbusx2y.h	6 Apr 2004 16:51:22 -
@@ -58,10 +58,6 @@
 void snd_usX2Y_In04Int(struct urb* urb);
 #endif
 
-#ifndef CONFIG_SND_DEBUG
-#define snd_usX2Y_Out04Int 0
-#endif
-
 #define NAME_ALLCAPS US-X2Y
 
 #endif
Index: alsa-driver/usb/usx2y/usbusx2yaudio.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usbusx2yaudio.c,v
retrieving revision 1.9
diff -u -r1.9 usbusx2yaudio.c
--- alsa-driver/usb/usx2y/usbusx2yaudio.c	30 Mar 2004 08:27:16 -	1.9
+++ alsa-driver/usb/usx2y/usbusx2yaudio.c	6 Apr 2004 16:51:25 -
@@ -1245,7 +1245,7 @@
 		 snd_dma_continuous_data(GFP_KERNEL),
 		 usX2Y_capt_substream-endpoints * 64*1024,
 		 usX2Y_capt_substream-endpoints * 128*1024)) ||
-	(usX2Y(card)-chip.dev-descriptor.idProduct == USB_ID_US428 
+	(usX2Y(card)-chip.dev-descriptor.idProduct != USB_ID_US122 
 	 0  (err = usX2Y_rate_set(usX2Y_stream, 44100 {	// Lets us428 recognize output-volume settings, disturbs us122.
 		snd_usX2Y_audio_stream_free(usX2Y_stream);
 		return err;

Re: [Alsa-devel] DigiDesign MBox USB Audio device

2004-04-06 Thread Patrick Boettcher

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 ksymoops to resolve a problem.
If there is more time, I will learn and hopefully understand.

So far,
PatrickUnable to handle kernel paging request at virtual address 2e2f2e2e
 printing eip:
c011999d
*pde = 
Oops:  [#1]
PREEMPT 
CPU:0
EIP:0060:[c011999d]Tainted: PF 
EFLAGS: 00010007   (2.6.5) 
EIP is at __wake_up_common+0x13/0x50
eax: cd963740   ebx: c5cf6000   ecx: 0001   edx: 2e2f2e2e
esi: 0292   edi: 0001   ebp: c5cf7ee4   esp: c5cf7ecc
ds: 007b   es: 007b   ss: 0068
Process sed (pid: 5839, threadinfo=c5cf6000 task=c7001260)
Stack:  400f007b 007b c5cf6000 0292 dfc8d45e c5cf7f04 c0119a0c 
   cd963740 0001 0001  c67f7b00 c5cf7f6c  c015cc1e 
   40018000 dfc8d45e 1000    c5cf6000 c5cf6000 
Call Trace:
 [c0119a0c] __wake_up+0x32/0x57
 [c015cc1e] pipe_readv+0x288/0x2d8
 [c015cca5] pipe_read+0x37/0x3b
 [c0150d74] vfs_read+0xd0/0x135
 [c0151007] sys_read+0x42/0x63
 [c01071ef] syscall_call+0x7/0xb

Code: 8b 32 74 31 8b 5a f4 8d 42 f4 8b 55 14 89 54 24 08 89 04 24 
 6note: sed[5839] exited with preempt_count 1
Unable to handle kernel paging request at virtual address 6273753b
 printing eip:
c0162216
*pde = 
Oops:  [#2]
PREEMPT 
CPU:0
EIP:0060:[c0162216]Tainted: PF 
EFLAGS: 00010002   (2.6.5) 
EIP is at fasync_helper+0x39/0xed
eax: c7162000   ebx:    ecx: cd963768   edx: 6273752f
esi: cedefb80   edi: cd963768   ebp:    esp: c7163f2c
ds: 007b   es: 007b   ss: 0068
Process usb.agent (pid: 5828, threadinfo=c7162000 task=d30d06a0)
Stack: c7162000 00030002  c67f7b68 c67f7b00 dfe9e300 c67f7b00 c015d244 
    cedefb80  cd963768 cedefb80 c015d36b c015d38a  
   cedefb80  c0151e50 c67f7b00 cedefb80 c5b34280 cedefb80  
Call Trace:
 [c015d244] pipe_read_fasync+0x48/0x68
 [c015d36b] pipe_read_release+0x0/0x3f
 [c015d38a] pipe_read_release+0x1f/0x3f
 [c0151e50] __fput+0x116/0x128
 [c0150562] filp_close+0x59/0x86
 [c01505f2] sys_close+0x63/0x96
 [c01071ef] syscall_call+0x7/0xb

Code: 39 72 0c 74 53 8d 4a 08 8b 52 08 85 d2 75 f1 85 ed 74 1f c7 
 6note: usb.agent[5828] exited with preempt_count 1

Re: [Alsa-devel] Re: Tascam US-224 progress report (was: USB224_usbsnoop1.log captured on WinXP)

2004-04-06 Thread Rui Nuno Capela


 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.
-- 
rncbc aka Rui Nuno Capela
[EMAIL PROTECTED]


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

[Alsa-devel] Detecting runtime ALSA library version

2004-04-06 Thread Glenn Maynard

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

  https://sourceforge.net/tracker/?func=detailatid=421366aid=930335group_id=37892
  
https://sourceforge.net/tracker/download.php?group_id=37892atid=421366file_id=82701aid=930335

and not being able to tell what version of alsa-lib is in use.

I'd recommend an entry point eg. const char *snd_lib_version() to get
this information.

As an aside: is it safe to assume that if /proc/asound/ doesn't exist,
ALSA is not in use?  It'd be useful to short circuit ALSA initialization
for OSS people, since they often have old, broken versions of alsa-lib
installed.

(I know that the converse isn't true--it's possible to load the basic
snd module, not load anything else, and then load OSS modules,
resulting in a working OSS environment but /proc/asound/ existing.)

-- 
Glenn Maynard


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: [Alsa-devel] Detecting runtime ALSA library version

2004-04-06 Thread Paul Davis

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 technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

[Alsa-devel] [PATCH]snd-usb-usx2y 0.6