public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Bdale Garbee <bdale@gag.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with codec discovery on HP 2530p
Date: Thu, 12 Nov 2009 07:47:14 +0100	[thread overview]
Message-ID: <s5hljicdytp.wl%tiwai@suse.de> (raw)
In-Reply-To: <1257976083.5237.1.camel@rover>

At Wed, 11 Nov 2009 16:48:03 -0500,
Bdale Garbee wrote:
> 
> On Wed, 2009-11-11 at 07:36 +0100, Takashi Iwai wrote:
> 
> > But, single_cmd=1 is obviously not good.  This options is just for
> > debugging purpose.  That's why that commit hits.
> 
> Ok, thanks, that fixed it.  
> 
> I wasn't aware that I'd done something to set that option, but indeed I
> had.  Perhaps it fixed a problem in some earlier kernel revision... I
> really do not recall!

Good to hear now it's fixed.

I guess that the latest Linus tree would work now even with
single_cmd=1 option since a fix patch was merged.  But, single_cmd
isn't really for normal purpose, so avoid it as much as possible.

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.


thanks,

Takashi

  reply	other threads:[~2009-11-12  6:47 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 [this message]
2009-11-12 19:26           ` Matthew Garrett

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=s5hljicdytp.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bdale@gag.com \
    --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