All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Davis <tadavis@lbl.gov>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre4
Date: Thu, 30 Jan 2003 09:53:35 -0800	[thread overview]
Message-ID: <3E39669F.20302@lbl.gov> (raw)
In-Reply-To: <Pine.LNX.4.53L.0301290143350.27119@freak.distro.conectiva>

Alan Cox wrote:

> On Thu, 2003-01-30 at 17:26, Thomas Davis wrote:
>
> >>FM801 is still the card not the codec. Somewhere on the FM801 is a 
> 48pin AC97 codec,
> >>it may even vary by card version, much like I have intel i810 audio 
> with a variety
> >>of codec devices.
> >>
> >
> >Yes, I agree on that..  I'm just trying to get the name "Forte Media
> >FM801" instead of "Unknown" to show up in the ac97 list.
>
>
> Why ? How do you even know the codec is made by forte media ?
>

because the forte driver does this:

[tdavis@lanshark sound]$ grep ac97 forte.c
#include <linux/ac97_codec.h>
         spinlock_t              ac97_lock;
         struct ac97_codec       *ac97;
  * forte_ac97_wait:
forte_ac97_wait (struct forte_chip *chip)
  * forte_ac97_read:
forte_ac97_read (struct ac97_codec *codec, u8 reg)
         spin_lock (&chip->ac97_lock);
         if (forte_ac97_wait (chip)) {
                 printk (KERN_ERR PFX "ac97_read: Serial bus busy\n");
         if (forte_ac97_wait (chip)) {
                 printk (KERN_ERR PFX "ac97_read: Bus busy reading reg 
0x%x\n",
                 printk (KERN_ERR PFX "ac97_read: Invalid data port");
         spin_unlock (&chip->ac97_lock);
  * forte_ac97_write:
forte_ac97_write (struct ac97_codec *codec, u8 reg, u16 val)
         spin_lock (&chip->ac97_lock);
         if (forte_ac97_wait (chip)) {
                 printk (KERN_ERR PFX "ac97_write: Serial bus busy\n");
         if (forte_ac97_wait (chip)) {
                 printk (KERN_ERR PFX "ac97_write: Bus busy after write\n");
         spin_unlock (&chip->ac97_lock);
         file->private_data = chip->ac97;
         struct ac97_codec *codec = (struct ac97_codec *) 
file->private_data;
         if (!create_proc_read_entry("driver/forte/ac97", 0, 0, 
ac97_read_proc, forte->ac97)) {
         remove_proc_entry ("driver/forte/ac97", NULL);
         struct ac97_codec *codec;
         if ((codec = kmalloc (sizeof (struct ac97_codec), GFP_KERNEL)) 
== NULL)
         memset (codec, 0, sizeof (struct ac97_codec));
         codec->codec_read = forte_ac97_read;
         codec->codec_write = forte_ac97_write;
         if (ac97_probe_codec (codec) == 0) {
         chip->ac97 = codec;
         spin_lock_init (&chip->ac97_lock);
         unregister_sound_mixer (chip->ac97->dev_mixer);

ie, it has a ac97 support in the driver, it calls ac97_probe_codec?

Is that enough or not?


  parent reply	other threads:[~2003-01-30 17:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  3:44 Linux 2.4.21-pre4 Marcelo Tosatti
2003-01-29  6:29 ` John Kim
2003-01-29  8:03 ` Denis Vlasenko
2003-01-29  9:36   ` Alan Cox
2003-01-29 12:49 ` Eyal Lebedinsky
2003-01-29 13:04 ` Maciej Soltysiak
2003-01-29 21:53 ` Thomas Davis
2003-01-30 11:43   ` Alan Cox
2003-01-30 17:09     ` Thomas Davis
2003-01-30 18:17       ` Alan Cox
2003-01-30 17:26         ` Thomas Davis
2003-01-30 18:28           ` Alan Cox
2003-01-30  0:47 ` sys_sendfile64 not in " John Fremlin
2003-01-30  8:29   ` Christoph Hellwig
2003-01-30 11:33     ` Alan Cox
2003-01-30 11:02       ` Marc-Christian Petersen
2003-01-30 11:16         ` Christoph Hellwig
2003-01-30 17:53 ` Thomas Davis [this message]
2003-01-30 19:35   ` Alan Cox
2003-01-30 18:46 ` Thomas Davis
2003-01-30 23:13   ` Martin K. Petersen
2003-01-31  3:14     ` Thomas Davis
2003-01-31  4:09       ` Martin K. Petersen
2003-01-31  4:13         ` Thomas Davis
2003-01-31  4:31           ` Martin K. Petersen
2003-01-31  4:48             ` Thomas Davis
2003-01-31  6:16             ` Thomas Davis
2003-01-30 23:30 ` Thomas Davis
2003-02-01 23:24 ` Adrian Bunk
2003-02-02 11:06 ` Adrian Bunk
2003-02-02 13:38   ` Alan Cox
2003-02-10 16:08 ` Jörn Engel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E39669F.20302@lbl.gov \
    --to=tadavis@lbl.gov \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.