mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing	Beep
Date: Thu, 29 Jul 2010 15:33:42 +0200	[thread overview]
Message-ID: <s5hfwz2s98p.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100729132532.GA18108@darkside.kls.lan>

At Thu, 29 Jul 2010 15:25:32 +0200,
Mario 'BitKoenig' Holbe wrote:
> 
> On Thu, Jul 29, 2010 at 11:42:44AM +0200, Takashi Iwai wrote:
> > OK, then try the patch below (over my previous two patches).  It
> > enables PC-beep for your device forcibly.
> 
> Yes, it does and it works. Thank you very much again.
> 
> I just checked 2 more boards - the P5E-VM HDMI (P5E-V HDMI's little
> brother) is already covered by the quirk and P5Q-EM (G45) seems to
> specify it correctly (subsystem_id = 0x104382fe - seems I got the logic
> wrong before - LSB isn't set here and it works).

So, it's likely a bad luck about the SSID of P5E-V.  I guess this
unexpectedly matches with the value Realtek codec expected, and
unluckily the value had side-effects.

Anyway, I applied the patch now.


thanks,

Takashi

      reply	other threads:[~2010-07-29 13:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 14:49 Mario 'BitKoenig' Holbe
2010-07-28 15:35 ` [alsa-devel] " Takashi Iwai
2010-07-28 16:03   ` Takashi Iwai
2010-07-28 21:27     ` Mario 'BitKoenig' Holbe
2010-07-29  5:44       ` Takashi Iwai
2010-07-29  8:09         ` Mario 'BitKoenig' Holbe
2010-07-29  8:26           ` Takashi Iwai
2010-07-29  8:41             ` Mario 'BitKoenig' Holbe
2010-07-29  8:52               ` Takashi Iwai
2010-07-29  9:15                 ` Mario 'BitKoenig' Holbe
2010-07-29  9:42                   ` Takashi Iwai
2010-07-29 13:25                     ` Mario 'BitKoenig' Holbe
2010-07-29 13:33                       ` 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=s5hfwz2s98p.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Mario.Holbe@TU-Ilmenau.DE \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®