From: Takashi Iwai <tiwai@suse.de>
To: Wei Ni <wni@nvidia.com>
Cc: "'Pavel Hofman'" <pavel.hofman@insite.cz>,
"'alsa-devel'" <alsa-devel@alsa-project.org>,
"'linux-kernel'" <linux-kernel@vger.kernel.org>,
"'akpm'" <akpm@linux-foundation.org>
Subject: Re: [alsa-devel] [PATCH]Support MCP89 and GT21x hdmi audio
Date: Wed, 03 Mar 2010 22:49:03 +0100 [thread overview]
Message-ID: <s5htysxm5yo.wl%tiwai@suse.de> (raw)
In-Reply-To: <6B4D417B830BC44B8026029FD256F7F1C16A89A11C@HKMAIL01.nvidia.com>
At Wed, 3 Mar 2010 15:21:12 +0800,
Wei Ni wrote:
>
> Hi, Takashi
> I generate the new patch file, please check it.
Thanks. Review comments below:
> @@ -1367,6 +1368,7 @@ static void azx_bus_reset(struct hda_bus *bus)
>
> /* number of codec slots for each chipset: 0 = default slots (i.e. 4) */
> static unsigned int azx_max_codecs[AZX_NUM_DRIVERS] __devinitdata = {
> + [AZX_DRIVER_NVIDIA] = 8,
Are you sure that this works for all Nvidia controller chips including
the old nForce chipset?
> diff --git a/sound/pci/hda/Makefile b/sound/pci/hda/Makefile
> index 315a1c4..199f440 100644
> --- a/sound/pci/hda/Makefile
> +++ b/sound/pci/hda/Makefile
> @@ -17,7 +17,7 @@ snd-hda-codec-cirrus-objs := patch_cirrus.o
> snd-hda-codec-ca0110-objs := patch_ca0110.o
> snd-hda-codec-conexant-objs := patch_conexant.o
> snd-hda-codec-via-objs := patch_via.o
> -snd-hda-codec-nvhdmi-objs := patch_nvhdmi.o
> +snd-hda-codec-nvhdmi-objs := patch_nvhdmi.o hda_eld.o
> snd-hda-codec-intelhdmi-objs := patch_intelhdmi.o hda_eld.o
This is buggy. You cannot create multiple modules containing the
same *.o file that exports symbols.
Instead, put hda_eld.o to snd-hda-codec-* (currently commented out),
and remove hda_eld.o from snd-hda-codec-intelhdmi-objs.
Takashi
next prev parent reply other threads:[~2010-03-03 21:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6B4D417B830BC44B8026029FD256F7F1C068B2BA8B@HKMAIL01.nvidia.com>
2010-03-02 5:43 ` Wu Fengguang
2010-03-03 3:33 ` Wei Ni
2010-03-03 6:46 ` Takashi Iwai
2010-03-04 1:17 ` Wu Fengguang
2010-03-04 2:18 ` Wu Fengguang
2010-03-04 5:44 ` Wu Fengguang
2010-03-04 5:52 ` Wei Ni
2010-03-04 6:09 ` Wu Fengguang
2010-03-02 7:59 ` Takashi Iwai
2010-03-02 9:43 ` Wei Ni
2010-03-02 9:55 ` Takashi Iwai
2010-03-02 10:03 ` Wei Ni
2010-03-02 10:42 ` Takashi Iwai
2010-03-02 10:44 ` Wei Ni
2010-03-03 3:28 ` Wei Ni
2010-03-03 4:06 ` Wei Ni
2010-03-03 6:44 ` Takashi Iwai
2010-03-03 7:21 ` Wei Ni
2010-03-03 21:49 ` Takashi Iwai [this message]
2010-03-04 2:21 ` Wei Ni
2010-03-04 9:46 ` Takashi Iwai
2010-03-04 10:46 ` Wei Ni
2010-03-04 10:56 ` Takashi Iwai
2010-03-04 11:09 ` Wei Ni
2010-03-04 11:31 ` Takashi Iwai
2010-03-04 11:37 ` Wei Ni
2010-03-04 11:43 ` Takashi Iwai
2010-03-04 11:46 ` Wei Ni
2010-03-04 15:34 ` Takashi Iwai
2010-03-05 2:41 ` Wei Ni
2010-03-07 19:21 ` VDR User
2010-03-08 4:35 ` Wei Ni
2010-03-08 4:46 ` Wu Fengguang
2010-03-10 5:42 ` VDR User
2010-03-10 6:01 ` Wu Fengguang
2010-03-10 7:58 ` Jaroslav Kysela
2010-03-10 8:05 ` VDR User
2010-03-10 12:54 ` Wu Fengguang
2010-03-10 17:38 ` VDR User
2010-03-11 7:30 ` Jaroslav Kysela
2010-03-11 18:15 ` VDR User
2010-03-11 18:32 ` Jaroslav Kysela
2010-03-11 19:24 ` VDR User
2010-03-12 4:32 ` VDR User
2010-03-12 4:37 ` Wu Fengguang
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=s5htysxm5yo.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel.hofman@insite.cz \
--cc=wni@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®