From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Bdale Garbee <bdale@gag.com>, linux-kernel@vger.kernel.org
Subject: Re: problem with codec discovery on HP 2530p
Date: Thu, 12 Nov 2009 19:26:53 +0000 [thread overview]
Message-ID: <20091112192653.GA12310@srcf.ucam.org> (raw)
In-Reply-To: <s5hljicdytp.wl%tiwai@suse.de>
On Thu, Nov 12, 2009 at 07:47:14AM +0100, Takashi Iwai wrote:
> BTW, with your laptop, which option is more suitable, model=laptop or
> model=mobile?
> I'm going to add a quirk entry for your device, but I need to know
> which model is most appropriate.
The 2530p seems to work fine with current upstream - it's caught by one
of the generic HP laptop quirks.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2009-11-12 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 14:53 problem with codec discovery on HP 2530p Bdale Garbee
2009-11-10 16:43 ` Takashi Iwai
2009-11-10 20:56 ` Bdale Garbee
2009-11-11 6:36 ` Takashi Iwai
2009-11-11 21:48 ` Bdale Garbee
2009-11-12 6:47 ` Takashi Iwai
2009-11-12 19:26 ` Matthew Garrett [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=20091112192653.GA12310@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=bdale@gag.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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