Bertrik Sikken | 3 Aug 22:53 2002
Picon

looking for PCI soundcard analysis tool

Hi all,

I have a PCI sound card based on a Cmedia 8738 chip, which has
windows drivers that can do various 3d effects (A3D, EAX 1.0
and 2.0) with very little impact on CPU usage.
So I assume these effects are done on the cmedia chip, not in
software.

The Linux drivers can only do the standard stuff, although the
sources indicate that there are some extended registers, possibly
used for the 3d processing. I'd like to figure out how the 3d
processing works by monitoring the data sent by the windows driver
to those registers and then try to resend that data under Linux.

For figuring out my HP3300c scanner I used a tool called USB snoopy
that helps monitor the traffic between driver and scanner over the
USB bus.

Is there a similar tool for PCI?

Kind regards,
Bertrik Sikken

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Yaman Salahi | 8 Aug 19:38 2002

Sound Blaster Audigy

Hello,

I just bought a new Sound Blaster Audigy for my system, and I just found
out there are no kernel drivers. I set up ALSA and got the sound to work,
but unfortunately, the sound quality is horrible.

Are there any other solutions? Is there an audigy driver in the works?

Thanks
Yaman Salahi

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Nerijus Baliunas | 22 Aug 13:46 2002
Picon
Picon

Re: Sound Blaster Audigy

On Thu, 8 Aug 2002 10:38:50 -0700 (PDT) Yaman Salahi <yaman <at> salahi-net.org> wrote:

> I just bought a new Sound Blaster Audigy for my system, and I just found
> out there are no kernel drivers. I set up ALSA and got the sound to work,
> but unfortunately, the sound quality is horrible.
> 
> Are there any other solutions? Is there an audigy driver in the works?

http://opensource.creative.com/

Regards,
Nerijus

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Yaman Salahi | 23 Aug 02:00 2002

Re: Sound Blaster Audigy

Nerijus Baliunas said:
> On Thu, 8 Aug 2002 10:38:50 -0700 (PDT) Yaman Salahi
> <yaman <at> salahi-net.org> wrote:
>
>> I just bought a new Sound Blaster Audigy for my system, and I just
>> found out there are no kernel drivers. I set up ALSA and got the sound
>> to work, but unfortunately, the sound quality is horrible.
>>
>> Are there any other solutions? Is there an audigy driver in the works?
>
> http://opensource.creative.com/
>
> Regards,
> Nerijus
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-sound"
> in the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Thanks a bunch!!

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Gerald Teschl | 24 Aug 23:26 2002
Picon

[PATCH] ad1848 infinite loop fix


I think I found the problem which causes the infinite loop
when the activation fails:

--- linux-2.4.19/drivers/sound/ad1848.c.orig    Sat Aug 24 23:19:54 2002
+++ linux-2.4.19/drivers/sound/ad1848.c Sat Aug 24 23:20:58 2002
 <at>  <at>  -3058,7 +3058,7  <at>  <at> 
        else
                printk(KERN_INFO "ad1848: Failed to initialize %s\n", 
devname);

-       return 0;
+       return -ENODEV;
 }

 static int __init ad1848_isapnp_probe(struct address_info *hw_config)

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Zwane Mwaikambo | 25 Aug 13:13 2002
Picon

Re: [PATCH] ad1848 infinite loop fix


> --- linux-2.4.19/drivers/sound/ad1848.c.orig    Sat Aug 24 23:19:54 2002
> +++ linux-2.4.19/drivers/sound/ad1848.c Sat Aug 24 23:20:58 2002
>  <at>  <at>  -3058,7 +3058,7  <at>  <at> 
>         else
>                 printk(KERN_INFO "ad1848: Failed to initialize %s\n", 
> devname);
> 
> -       return 0;
> +       return -ENODEV;
>  }
> 
>  static int __init ad1848_isapnp_probe(struct address_info *hw_config)

This will break the isapnp probe in ad1848, the problem could possibly be 
elsewhere. You have to be a bit careful when changing the return values of 
functions in some of the older OSS code.

	Zwane

--

-- 
function.linuxpower.ca

-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Gerald Teschl | 25 Aug 13:29 2002
Picon

Re: [PATCH] ad1848 infinite loop fix

On Sun, 25 Aug 2002, Zwane Mwaikambo wrote:

> 
> > --- linux-2.4.19/drivers/sound/ad1848.c.orig    Sat Aug 24 23:19:54 2002
> > +++ linux-2.4.19/drivers/sound/ad1848.c Sat Aug 24 23:20:58 2002
> >  <at>  <at>  -3058,7 +3058,7  <at>  <at> 
> >         else
> >                 printk(KERN_INFO "ad1848: Failed to initialize %s\n", 
> > devname);
> > 
> > -       return 0;
> > +       return -ENODEV;
> >  }
> > 
> >  static int __init ad1848_isapnp_probe(struct address_info *hw_config)
> 
> This will break the isapnp probe in ad1848, the problem could possibly be 
> elsewhere. You have to be a bit careful when changing the return values of 
> functions in some of the older OSS code.
> 
I just looked into some of the other drivers and they also use "return 0"
in case of failure. So you are right, this is not the proper
way to fix this! But this means that there are some generic problems
with the loading of kernel modules!?

If I use "return -ENODEV" the module will do the init stuff, fail, and
thats it. With the original "return 0" the module will do the init
stuff in an infinite loop. I do not think this is a problem inside
the module since it looks like the main init function gets
called over and over again (blocking the kernel and hence freezing
(Continue reading)


Gmane