Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chris M <cmanougian@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Update patch for codecs alias name for Dell
Date: Fri, 21 Feb 2014 15:54:10 +0100	[thread overview]
Message-ID: <s5h1tywv7n1.wl%tiwai@suse.de> (raw)
In-Reply-To: <loom.20140218T221659-931@post.gmane.org>

At Tue, 18 Feb 2014 21:31:07 +0000 (UTC),
Chris M wrote:
> 
> Chris M <cmanougian <at> yahoo.com> writes:
> 
> > 
> > Takashi Iwai <tiwai <at> suse.de> writes:
> > 
> > > 
> > > At Thu, 28 Nov 2013 15:30:56 +0800,
> > > Kailang wrote:
> > > > 
> > > > Hi Takashi,
> > > > 
> > > > I remodified the code as belowing.
> > > > 
> > > > >From 888b51395ebab411660401f856e3af7988d9240b Mon Sep 17 00:00:00 2001
> > > > From: Kailang Yang <kailang <at> realtek.com>
> > > > Date: Thu, 28 Nov 2013 15:23:20 +0800
> > > > Subject: [PATCH] ALSA: hda/realtek - Add more codecs alias name for Dell
> > > > 
> > > > Dell assigned alias name for more codecs.
> > > > ALC3220 ALC3221 ALC3223 ALC3226 ALC3234 ALC3661.
> > > > 
> > > > Signed-off-by: Kailang Yang <kailang <at> realtek.com>
> > > 
> > > Thanks, applied now, but it's targeted for 3.14 kernel, as this is no
> > > urgent fixes.  You can find it in for-next branch of sound git tree.
> > > 
> > > Takashi
> > > 
> > 
> > Sorry for asking this on a developer forum, but I'm pretty sure I finally
> > found the answer here. I had considered the need to wait it out for a kernel
> > upgrade (beyond 3.12 in Debian Testing/Jessie). I have no sound right now.
> > How do I apply this patch? When I installed Debian Testing, I installed a
> > targeted initrd, and I was considering retrying with a generic initrd -
> > although I think this thread just saved me from that. Will an established
> > initrd come into play? Will I have to recompile the 3.12 kernel?
> > 
> > The Dell codec alias name is ALC3223.
> > 
> > Thanks
> 
> This is a follow up question for anyone.
> 
> This boils down to a general question about new kernel compilation.
> 
> To try and solve my no sound issue, I waited until 3.14-rc3 kernel went live.
> 
> In the 3.14-rc3 kernel source folder, this patch is located at:
> sound/pci/hda/patch_realtek.c
> 
> I thought that simply compiling the latest kernel, and then installing it,
> would apply all relevant patches (more than the realtek patch may be in
> play), but now I'm not so sure.
> 
> The question is this: Does a 3.14-rc3 compiled kernel already include the
> above patch? Or, because it is labeled as a "patch" within the source, do I
> have to actually patch the source before compiling?

Yes, it's already included in 3.14-rc3.

But I doubt it'll help anything for your "audio" problem.  The patch
merely changes the codec name string, nothing else.  You're chasing a
wrong fish.


Takashi

> IOW, does the patch get compiled, or does anything labeled as a patch within
> the source still have to be manually patched against the kernel?
> 
> Thanks to anyone who can answer this.  I complied and installed the 3.14-rc3
> kernel without a problem. It was the default kernel in grub. But I'm still
> dealing with the exact same no sound issue as if booting into 3.12.
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

  reply	other threads:[~2014-02-21 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 10:01 Update patch for codecs alias name for Dell Kailang
2013-11-27 10:51 ` Takashi Iwai
2013-11-28  7:30   ` Kailang
2013-11-28 10:56     ` Takashi Iwai
2014-02-02  0:20       ` Chris M
2014-02-18 21:31         ` Chris M
2014-02-21 14:54           ` Takashi Iwai [this message]
2014-03-05  7:16             ` Chris M

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=s5h1tywv7n1.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=cmanougian@yahoo.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