alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zbigniew Luszpinski <zbiggy@o2.pl>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsa-1.0.24 realtek hda codec patch
Date: Thu, 19 May 2011 07:48:50 +0200	[thread overview]
Message-ID: <s5hei3v1br1.wl%tiwai@suse.de> (raw)
In-Reply-To: <201105082357.07564.zbiggy@o2.pl>

At Sun, 8 May 2011 23:57:07 +0200,
Zbigniew Luszpinski wrote:
> 
> Hello,
> 
> maybe you do not know but Realtek has in download section its own alsa 
> 1.0.24 source package with additional code for Realtek codecs.
> Because this code has almost zero chance to reach end users because 
> everyone uses vanilla alsa from alsa site or from kernel.org or alsa from 
> distro package I thought it would be good to exctract it and put it here 
> for inclusion in mainstream/kernel alsa. This way all users will benefit 
> from it and code will not be wasted. The attached patch contains cleaned 
> up diff between: alsa-driver-1.0.24.tar.bz2 from alsa-project site and 
> LinuxPkg_5.16rc12.tar.bz2 dated 2011/4/28 from realtek.com.tw site.
> 
> Its strange that Realtek cooks this in silence instead posting it to alsa 
> for everyone. I hope Realtek will have nothing against merging these 
> changes mainstream. This way Realtek hardware will be better supported by 
> Linux distros.

Don't worry, usually Realtek guys sync with the upstream occasionally,
once or twice per kernel release, and send us the patches.  You can
see the author in each commit of sound/pci/hda/patch_realtek.c in
kernel git tree.


Takashi

      parent reply	other threads:[~2011-05-19  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 21:57 [PATCH] alsa-1.0.24 realtek hda codec patch Zbigniew Luszpinski
2011-05-19  0:52 ` Lenny Story
2011-05-19  5:49   ` Takashi Iwai
2011-05-19  5:48 ` Takashi Iwai [this message]

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=s5hei3v1br1.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=zbiggy@o2.pl \
    /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;
as well as URLs for NNTP newsgroup(s).