mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Abhijit Bhopatkar" <bain@devslashzero.com>
Cc: "Ivan N. Zlatev" <contact@i-nz.net>,
	"Jaroslav Kysela" <perex@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
Date: Tue, 04 Sep 2007 14:56:21 +0200	[thread overview]
Message-ID: <s5hmyw28u8a.wl%tiwai@suse.de> (raw)
In-Reply-To: <2ff216280709032042t4a507feci8d5759526971ae7b@mail.gmail.com>

At Tue, 4 Sep 2007 09:12:32 +0530,
Abhijit Bhopatkar wrote:
> 
> 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.

OK, these are real problems.

> 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.

Just to be sure, doesn't none of intel-mac-[1-5] model match with your
machine?  If so, putting the pin-config back is the straightforward
solution indeed.

Anyway, it'd be helpful if someone else can check the same MacBook
(1st generation, not Pro?) whether the problem is reproducible.


thanks,

Takashi

  reply	other threads:[~2007-09-04 12:56 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
2007-09-04 12:56         ` Takashi Iwai [this message]
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=s5hmyw28u8a.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bain@devslashzero.com \
    --cc=contact@i-nz.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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®