All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Vrihad Shoonya <vrihad@softhome.net>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: Is there plans to support SiS7019?
Date: Tue, 17 Aug 2004 11:38:35 +0200	[thread overview]
Message-ID: <s5h4qn29k9w.wl@alsa2.suse.de> (raw)
In-Reply-To: <35261.192.168.0.10.1092527328.squirrel@dev.datamax.co.in>

At Sun, 15 Aug 2004 05:18:48 +0530 (IST),
Vrihad Shoonya wrote:
> 
> Hi!
> 
> Thanks for the quick response.
> 
> > The question is whether SIS7019 is an AC97 chip, or it's the one to
> > control other AC97 chips.  If it's former, you should have another PCI
> > entry for the controller (check lspci).  In the latter case, you can
> > try snd-trident module with changes of pci id table from SIS7018 to
> > SIS7019.
> 
> SiS7019 controls other AC97 chips. The board which we have designed
> uses Real Tech's ALC202A (four channel) and ALC650 (six channel).
> Now what should I change in
> .../alsa-driver-1.0.0rc2/alsa-kernel/pci/trident/trident.c?
> I see following entries with SiS7018 mentioned:
> 
> <snip>
> 
> MODULE_DESCRIPTION("Trident 4D-WaveDX/NX & SiS SI7018");
> 
> <snip>
> 
> MODULE_DEVICES("{{Trident,4DWave DX},"
>                 "{Trident,4DWave NX},"
>                 "{SiS,SI7018 PCI Audio},"
>                 "{Best Union,Miss Melody 4DWave PCI},"
>                 "{HIS,4DWave PCI},"
>                 "{Warpspeed,ONSpeed 4DWave PCI},"
>                 "{Aztech Systems,PCI 64-Q3D},"
>                 "{Addonics,SV 750},"
>                 "{CHIC,True Sound 4Dwave},"
>                 "{Shark,Predator4D-PCI},"
>                 "{Jaton,SonicWave 4D},"
>                 "{Hoontech,SoundTrack Digital 4DWave NX}}");
> 
> <snip>
> 
> static struct pci_device_id snd_trident_ids[] = {
>         { 0x1023, 0x2000, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /* Trident
> 4DWave DX PCI Audio */
>         { 0x1023, 0x2001, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /* Trident
> 4DWave NX PCI Audio */
>         { 0x1039, 0x7018, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0, },   /* SiS
> SI7018 PCI Audio */
>         { 0, }
> };
> 
> <snip>
> 
> There are few more instances where related data structures are used
> in the code. In the declarations shown above, what changes should I
> make? Will changing the name part from 7018 to 7019 will be enough?

No, just change snd_trident_ids[] entry for 7018 to 7019's one (maybe
0x7019?).  Also, in trident_main.c, you need to change the line 3546

	trident->device = (pci->vendor << 16) | pci->device;

to
	trident->device = TRIDENT_DEVICE_ID_SI7018;

You can leave MODULE_* stuffs as they are.


Takashi


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

  reply	other threads:[~2004-08-17  9:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 11:19 Is there plans to support SiS7019? Peter Zubaj
2004-08-13 23:45 ` Vrihad Shoonya
     [not found]   ` <Pine.HPX.4.3 3n.0408161131450.27899-100000@studcom.urz.uni-halle.de>
2004-08-16  9:42   ` Clemens Ladisch
2004-08-14  3:30     ` Vrihad Shoonya
2004-08-16 13:10       ` Takashi Iwai
2004-08-14 23:48         ` Vrihad Shoonya
2004-08-17  9:38           ` Takashi Iwai [this message]
2004-08-17  4:57             ` Vrihad Shoonya
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 13:14 Peter Zubaj
2004-08-19 13:31 ` Vrihad Shoonya
2004-08-19  7:51 Peter Zubaj
2004-08-19  8:31 ` Vrihad Shoonya
2004-08-19 11:19   ` Clemens Ladisch
2004-08-19 11:54     ` Jaroslav Kysela
2004-08-19 13:33       ` Vrihad Shoonya
2004-08-19 13:30         ` Jaroslav Kysela
2004-08-18  7:02           ` Vrihad Shoonya
2004-08-19 13:37     ` Vrihad Shoonya
2004-08-19 21:26       ` Lee Revell
2004-08-18  6:56         ` Vrihad Shoonya
2004-08-19  7:32 Peter Zubaj
2004-08-17  5:04 ` Vrihad Shoonya
2004-08-17 10:57 Peter Zubaj
2004-08-17  4:42 ` Vrihad Shoonya
2004-08-13 10:34 Vrihad Shoonya

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=s5h4qn29k9w.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=clemens@ladisch.de \
    --cc=vrihad@softhome.net \
    /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.