hi all,
> NOTE: I am cc-ing this to the kernel list in hope someone there might
> have a better insight in this. For the kernel people who intend to
> respond to this, I would greatly appreciate it if you could CC me, as
> I am not subscribed to the kernel list.
i'm following ico's policy in this
Hi,
I am having trouble recording using Creative Labs Sound Blaster Audigy 2
NX. The linux rec program worked fine. But whenever I use arecord (e.g.
arecord test.wav), I got Segmentation fault. I pinpointed the problem to
the function pcm_read in aplay.c. Specifically it was the line:
r = readi
On Thu, 2004-03-18 at 23:03, Josh Green wrote:
> I have a laptop with the following hardware:
> P4 3.06Ghz CPU
> 82801DB AC'97 Audio Controller
> 82801DB AC'97 Modem Controller
> nVidia GeForce Go5200
>
>
> and software:
> Linux Kernel 2.6.3 (with some ACPI patches)
> Alsa 1.0.3
> Glibc 2.3.2
>
Hi all,
NOTE: I am cc-ing this to the kernel list in hope someone there might have a better
insight in this. For the kernel people who intend to respond to this, I would greatly
appreciate it if you could CC me, as I am not subscribed to the kernel list.
Summary:
snd-hdsp (RME Multiface cardbus
Pavana Sharma wrote:
> I am providing control interface for my driver to access from user space
> with functions get & put .
>
> * while creating new controls should I be allowed to create my hardware
> specific controls like gain, power, rate & other codec specific parameters.
All controls are h
On Fri, 26 Mar 2004, James Courtier-Dutton wrote:
> Extract from ./sound/pci/emu10k1/emupcm.c
>
> static unsigned int capture_period_sizes[31] = {
> 384,448,512,640,
> 384*2, 448*2, 512*2, 640*2,
> 384*4, 448*4, 512*4, 640*4,
> 384*8, 448*8,
Extract from ./sound/pci/emu10k1/emupcm.c
static unsigned int capture_period_sizes[31] = {
384,448,512,640,
384*2, 448*2, 512*2, 640*2,
384*4, 448*4, 512*4, 640*4,
384*8, 448*8, 512*8, 640*8,
384*16, 448*16, 512*16, 640*16,
384*3
On Fri, 26 Mar 2004, Yong, Chee Yeew wrote:
> alsa-0.9.4
^^
Too old.
> rat-4.2.24
Jaroslav
-
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
--
alsa-driver-1.0.3 with Linux 2.6.4 always has a FATAL modprobe error
when loading the ALSA modules for the first time. However, if you remove
the ALSA modules and then immediately re-load them, there is never an error
and ALSA works ok. Is this a bug or a modprobe.conf problem?
Exactly the same m
alsa-0.9.4
rat-4.2.24
> -Original Message-
> From: Jaroslav Kysela [mailto:[EMAIL PROTECTED]
> Sent: 26 March 2004 13:13
> To: Yong, Chee Yeew
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Alsa-devel] Has this patch been updated on any ALSA
> releases ?
>
>
> On Fri, 26 Mar 2004, Yong, Chee Y
On Fri, 26 Mar 2004, Yong, Chee Yeew wrote:
> Hi Jaroslav,
>
> Thanks for replying.
>
> > It would be better to specify your problem. The OSS emulation code was
> > changed a lot from this date and rat is working for me perfectly.
> > Jaroslav
>
> When I ru
Hi Jaroslav,
Thanks for replying.
> It would be better to specify your problem. The OSS emulation code was
> changed a lot from this date and rat is working for me perfectly.
> Jaroslav
When I run RAT, I get the warning:
audio_read: Resource temporarily un
On Fri, 26 Mar 2004, Yong, Chee Yeew wrote:
> Hi,
>
> I have the same problem as Andrea Mohr, and I wish to patch it. See:
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg09732.html
>
> The patch is posted by Jaroslav Kysela:
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg09781.html
>
>
Hi,
I have the same problem as Andrea Mohr, and I wish to patch it. See:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg09732.html
The patch is posted by Jaroslav Kysela:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg09781.html
I was wondering if:
a) The patch works as it is?
b) The patch h
Because Creative uses diffrent AC97 codec and this codec has same
controls as controls implemented in dsp. then on 9.8 it fails to
load.
Could you send me output of /proc/asound/card/codec97/ac97 <- this
is not exact name
/proc/asound/card/codec97/ac97reg
where card is card name
???
Peter Zub
From: p z <[EMAIL PROTECTED]>
Reply-To: p z <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: [Alsa-devel] Test: SBLive! (C) 2003 need extra effort on Rear
Analog Output
Date: Fri, 26 Mar 2004 08:27:57 +0100
In alsa-driver/alsa-kernel/emu10k1/emumixer there
On 25-Mar-2004 Brian Furey wrote:
> Thanks Giuliano,
>
> How can I get a dump of the current hardware configuration space?
Hmm, lspci ? :)
If you mean how to get the capabilities of the card, it's a bit
tricky. The caps are not a static thing. Each setting may rure
others. For example, a card ha
> My guess is that the problem is the pcmcia bus is somehow 2000 times
> slower than it should be.. csound seems to confirm this hypothesis
> from the command line when attempting realtime synthesis:
i seem to know this problem ...
first of all, which cardbus bridge do you have? (lspci -v)
here
hello,
I am providing control interface for my driver to access from user space
with functions get & put .
( driver is for arm platform ) .
I want to know
* while creating new controls should I be allowed to create my hardware
specific controls like gain, power, rate & other codec specific par
19 matches
Mail list logo
