From: Tony Hoyle <tmh@nodomain.org>
To: linux-kernel@vger.kernel.org
Subject: snd_hda_intel on linux 2.6.30
Date: Mon, 22 Jun 2009 20:49:09 +0100 [thread overview]
Message-ID: <4A3FE035.2010804@nodomain.org> (raw)
Hi,
I've been trying to get sound working on a Poulsbo board using 2.6.30.
Previously, with the available patches sound worked OK.
2.6.30 has most of the patches already in, and the the Intel HDA is
indeed recognized, but no sound appears. Boot logs show:
[ 30.948427] HDA Intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 30.958108] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low)
-> IRQ 16
[ 30.968030] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 31.192916] input: HDA Intel MID Line In at Ext Rear Jack as
/class/input/input3
[ 31.204980] input: HDA Intel MID Mic at Ext Front Jack as
/class/input/input4
[ 31.218872] input: HDA Intel MID Line Out at Ext Rear Jack as
/class/input/input5
[ 31.234356] input: HDA Intel MID HP Out at Ext Front Jack as
/class/input/input6
followed later by
[ 50.875374] hda-intel: Invalid position buffer, using LPIB read
method instead.
[ 50.875416] hda-intel: IRQ timing workaround is activated for card
#0. Suggest a bigger bdl_pos_adj.
I tried backporting (forward porting?) the missing fixups from the older
patch, but apart from adding the message:
[ 30.968039] Do fixup for Poulsbo <6>D0 or newer stepping
I still didn't work (of course the possibility I stuffed up my patching
looms large there, and I'd rather work with virgin source if it's possible).
What's the best way to go about debugging this? Is there an official
(or unofficial) patch for Poulsbo on 2.6.30 knocking around somewhere?
Tony
next reply other threads:[~2009-06-22 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 19:49 Tony Hoyle [this message]
2009-07-02 16:25 ` Takashi Iwai
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=4A3FE035.2010804@nodomain.org \
--to=tmh@nodomain.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
Powered by JetHome