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 so
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 settings, which give a period size of 4410. If I chang
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 b
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 Main
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 gen
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
snd_pcm_rea
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: /cvsroot/als
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-p
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 faile
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 H.
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
i
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 a
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, hurr
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 matter
14 matches
Mail list logo
