DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org;
	h=Received:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-Identified-User;
	b=j2TSysqkisDy54JU6vXcMw43rpY3kFcRzIvcRvbDoRPNRVHYWVLzxtgoRU0Ap1UidHH8Hvf9TC3OYKCm2Fk0k7Wx4AtH+ZE4DlLDRh7L9nbeNm08lIuh2crc4cSD5XTF;
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf
Date: Tue, 22 Jul 2008 17:23:04 -0700
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org
References: <20080722233722.GA12247@bromo.msbb.uc.edu>
In-Reply-To: <20080722233722.GA12247@bromo.msbb.uc.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200807221723.04654.jbarnes@virtuousgeek.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1004
Lines: 21

On Tuesday, July 22, 2008 4:37 pm Jack Howarth wrote:
> Jesse,
>     I am unclear on what you want to push. Are you referring
> to the mmconf_end_bus_num_detect.patch and
> mmconf_end_bus_num_detect_fix.patch fixes that are already in -tip? These
> work fine in allowing MMCONFIG to work on my MacBook Pro and should go into
> the stable kernel. If you are talking about blacklisting pcie pre1.1
> devices to solve the problems with ASPM, I really don't understand how I do
> that (in terms of finding out what devices to blacklist).

I was referring to the ASPM patch.  You reported that you needed to disable 
ASPM in order to boot without hanging, right?  I just wanted to make sure 
that Shaohua's patch allowed you to do that with ASPM=y.

Thanks,
Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/