From: Jack Howarth <howarth@bromo.msbb.uc.edu>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: macbook2,2 latest git mmconfig issues
Date: Sat, 19 Jul 2008 11:14:53 -0400 [thread overview]
Message-ID: <20080719151453.GA13792@bromo.msbb.uc.edu> (raw)
In-Reply-To: <dd18b0c30807190753q22259690jcae780de13c8560d@mail.gmail.com>
On Sat, Jul 19, 2008 at 07:53:34AM -0700, Justin Mattock wrote:
> >
>
> could be; but loading an iso works i.g.
> after installing it and starting up.
> these two messages came from after applying
> the two patches(keep in mind I was tired so maybe
> plugged them in wrong) before the two patches
> the MMCONFIG disable message with f0000000
> that you where receiving. maybe the manufacture
> on mine needs to be MacBookPro2,2 and the 0x3f
> needs to be 0x1f. Where do I find these numbers
> and names on the system? I've done dmidecode
> but can't seem to make out any of the info
>
> --
> Justin P. Mattock
Justin,
I am attempting to build kernel rpms with tip right now.
My first effort would boot because somehow the modules weren't
being found (paths were being used with -tip in them). I've removed
the localversion file from the top level of tip and hope that fixes
the packaging issues. This issue didn't occur when I used a git
from the linus kernel branch.
Jack
next prev parent reply other threads:[~2008-07-19 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 3:39 Justin Mattock
2008-07-19 4:45 ` Yinghai Lu
2008-07-19 5:54 ` Justin Mattock
2008-07-19 6:54 ` Justin Mattock
2008-07-19 6:58 ` Yinghai Lu
2008-07-19 7:30 ` Justin Mattock
2008-07-19 13:10 ` Jack Howarth
2008-07-19 14:53 ` Justin Mattock
2008-07-19 15:14 ` Jack Howarth [this message]
2008-07-19 15:54 ` Justin Mattock
2008-07-19 16:28 ` Jack Howarth
2008-07-19 17:15 ` Justin Mattock
2008-07-19 17:58 ` Jack Howarth
2008-07-19 19:35 ` Justin Mattock
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=20080719151453.GA13792@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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®