From: "Abhijit Bhopatkar" <bain@devslashzero.com>
To: "Ivan N. Zlatev" <contact@i-nz.net>
Cc: "Takashi Iwai" <tiwai@suse.de>, "Jaroslav Kysela" <perex@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
Date: Tue, 4 Sep 2007 09:12:32 +0530 [thread overview]
Message-ID: <2ff216280709032042t4a507feci8d5759526971ae7b@mail.gmail.com> (raw)
In-Reply-To: <3db1ec7f0709030506j5fe6dbc3w6c7ae8daa94c3323@mail.gmail.com>
On 9/3/07, Ivan N. Zlatev <contact@i-nz.net> wrote:
> On 9/3/07, Ivan N. Zlatev <contact@i-nz.net> wrote:
> > On 9/3/07, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Mon, 3 Sep 2007 15:55:18 +0530,
> > > Abhijit Bhopatkar wrote:
> > > >
> > > > commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all
> > > > pin configs for intel macs, but it breaks sound on
> > > > Macbook first
> > >
> > > Please elaborate how does it break. "it breaks sound" is too
> > > ambigious like the most popular bug reports "sound doesn't work" :)
Apologies for the terse report,
On my macbook with latest kernels
1. Alsamixer is showing only three controlls in total,
Master PCM and Digital.
2. There is absolutely no output sound what so ever.
3. There is no capture sound being captured either.
Reverting back the pin config to the one in previous kernels is
working (although not perfect e.g. to enable input sound we need to
toggle the capture device to mic and linein atlease once, no idea
whats the deal with that)
I am willing to do whatever test you people want, though I do not know
where to look for more info at this point. So please feel free direct
me to arrive at a better soultion or better info.
Thanks
Abhijit
PS:
lspci -v shows
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 02)
Subsystem: Unknown device 8384:7680
Flags: us master, fast devsel, latency 0, IRQ 21
Memory at 90440000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Capabilities: [70] Express Unknown type IRQ 0
Let me know if you need output dump of other stuff.
next prev parent reply other threads:[~2007-09-04 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 10:25 Abhijit Bhopatkar
2007-09-03 10:36 ` Takashi Iwai
2007-09-03 11:07 ` Ivan N. Zlatev
2007-09-03 12:06 ` Ivan N. Zlatev
2007-09-04 3:42 ` Abhijit Bhopatkar [this message]
2007-09-04 12:56 ` Takashi Iwai
2007-09-04 14:18 ` Abhijit Bhopatkar
2007-09-04 15:00 ` Alistair John Strachan
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=2ff216280709032042t4a507feci8d5759526971ae7b@mail.gmail.com \
--to=bain@devslashzero.com \
--cc=contact@i-nz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--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
all inboxes | Powered by JetHome®