From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Abhijit Bhopatkar" <bain@devslashzero.com>
Cc: "Takashi Iwai" <tiwai@suse.de>,
"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, 4 Sep 2007 16:00:19 +0100 [thread overview]
Message-ID: <200709041600.19498.alistair@devzero.co.uk> (raw)
In-Reply-To: <2ff216280709040718y4b8e1fa7x1f51cc68f1d18de9@mail.gmail.com>
On Tuesday 04 September 2007 15:18:23 Abhijit Bhopatkar wrote:
[snip]
> > Anyway, it'd be helpful if someone else can check the same MacBook
> > (1st generation, not Pro?) whether the problem is reproducible.
>
> To be precise its Macbook 1st Generation non pro. with subsystem id
> 0x106b0a00
>
> Well a friend of mine has the same model and i tried things out on his
> machine. to my surprise :(, the original 2.6.23-rc5 is working fine on his
> machine.
>
> So on my machine we booted to windows and tested things out. The sound
> on my machine doesn't work in windows either, although its working in
> OSX.
>
> So sorry for all the noise its most likely a hardware problem after all.
> Although i am baffled as to why old pin config works on this
> particular broken hardware.
>
> I hope i didn't bug you too much, i appreciate your quick responses.
I think the first generation macbook firmwares weren't completely other-OS
ready when they were shipped (no bootcamp in firmware, iirc). Have you
applied all available firmware updates? Do you use bootcamp?
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
prev parent reply other threads:[~2007-09-04 15:04 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
2007-09-04 14:18 ` Abhijit Bhopatkar
2007-09-04 15:00 ` Alistair John Strachan [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=200709041600.19498.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=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®