From: Jack Howarth <howarth@bromo.msbb.uc.edu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.26-rc9-git9 doesn't boot on Macintel
Date: Thu, 17 Jul 2008 23:06:32 -0400 [thread overview]
Message-ID: <20080718030632.GA31508@bromo.msbb.uc.edu> (raw)
In-Reply-To: <86802c440807171825m24ffe140o81bb76286823568e@mail.gmail.com>
YH,
The line...
DMI_MATCH(DMI_PRODUCT_NAME, "MacBookPro2"),
works fine in your mmconfig patch. I'll post the dmesg output to my
bugzilla report shortly. It will take me a little longer to the
early_config_dump since the fedora kernel rpms are using the
vanilla 2.6.26 source code which appears to lack your patch.
Is...
http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-05/msg11336.html
the final one that went into the linus kernel tree? Hopefully I can
just apply that to vanilla 2.6.26-git4.
Jack
next prev parent reply other threads:[~2008-07-18 3:06 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:52 2.6.26-rc9-git9 doesn't boot on Macintel Justin Mattock
[not found] ` <20080715231118.GA26807@bromo.msbb.uc.edu>
2008-07-16 0:26 ` Justin Mattock
[not found] ` <20080716012427.GA27398@bromo.msbb.uc.edu>
2008-07-16 3:05 ` Justin Mattock
[not found] ` <20080716035830.GA27935@bromo.msbb.uc.edu>
2008-07-16 5:30 ` Justin Mattock
2008-07-16 7:44 ` Yinghai Lu
2008-07-16 7:50 ` Justin Mattock
2008-07-16 8:36 ` Yinghai Lu
2008-07-16 14:08 ` Jack Howarth
2008-07-16 15:12 ` Justin Mattock
2008-07-16 17:30 ` Yinghai Lu
2008-07-16 17:29 ` Yinghai Lu
2008-07-16 22:35 ` Yinghai Lu
[not found] ` <20080717004004.GA17792@bromo.msbb.uc.edu>
2008-07-17 0:49 ` Yinghai Lu
2008-07-17 1:21 ` Jack Howarth
2008-07-17 2:29 ` Yinghai Lu
2008-07-17 2:40 ` Jack Howarth
2008-07-17 1:25 ` Justin Mattock
2008-07-17 2:35 ` Jack Howarth
2008-07-17 2:59 ` Yinghai Lu
2008-07-17 3:15 ` Jack Howarth
2008-07-17 4:04 ` Yinghai Lu
2008-07-17 3:44 ` Jack Howarth
2008-07-17 4:13 ` Yinghai Lu
2008-07-17 6:18 ` Jack Howarth
2008-07-17 6:48 ` Yinghai Lu
2008-07-17 11:56 ` Jack Howarth
2008-07-17 12:47 ` Jack Howarth
2008-07-17 14:13 ` Jack Howarth
2008-07-17 16:26 ` Jack Howarth
2008-07-17 16:42 ` Yinghai Lu
2008-07-17 18:39 ` Justin Mattock
[not found] ` <20080717195039.GA28694@bromo.msbb.uc.edu>
2008-07-17 22:09 ` Justin Mattock
2008-07-18 1:15 ` Jack Howarth
2008-07-18 1:25 ` Yinghai Lu
2008-07-18 1:46 ` Jack Howarth
2008-07-18 3:06 ` Jack Howarth [this message]
2008-07-18 6:09 ` Jack Howarth
2008-07-18 6:22 ` Yinghai Lu
2008-07-18 12:02 ` Jack Howarth
2008-07-18 12:09 ` Jack Howarth
2008-07-18 16:19 ` Yinghai Lu
2008-07-18 16:29 ` Jack Howarth
2008-07-18 16:36 ` Yinghai Lu
2008-07-18 18:20 ` Justin Mattock
2008-07-18 18:45 ` Yinghai Lu
2008-07-18 18:56 ` Justin Mattock
2008-07-18 16:07 ` Jack Howarth
2008-07-18 16:17 ` Yinghai Lu
2008-07-16 22:51 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2008-07-15 14:17 Jack Howarth
2008-07-15 2:00 Jack Howarth
2008-07-15 2:04 ` Justin Mattock
2008-07-14 13:51 Jack Howarth
2008-07-14 16:26 ` Justin Mattock
2008-07-14 17:02 ` Stefan Richter
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=20080718030632.GA31508@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.