From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Newbury Subject: Re: PCI resources above 4GB Date: Mon, 21 May 2012 18:27:10 +0100 Message-ID: <4FBA7AEE.3090402@snewbury.org.uk> References: <1333968563.5678.19.camel@infinity> <4F89CE43.7040200@snewbury.org.uk> <4F8AA0DC.6010902@snewbury.org.uk> <4F8AB312.7060606@snewbury.org.uk> <4F8B04A4.4070507@snewbury.org.uk> <4F8B0609.8010603@snewbury.org.uk> <4F96770D.2050606@snewbury.org.uk> <4FB227D3.7090002@snewbury.org.uk> <4FB4EE99.10509@snewbury.org.uk> <4FB4F039.2040308@snewbury.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Yinghai Lu Cc: linux-pci@vger.kernel.org, DRI mailing list List-Id: dri-devel@lists.freedesktop.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/05/12 10:08, Yinghai Lu wrote: > On Fri, May 18, 2012 at 12:45 AM, Yinghai Lu > wrote: >> On Thu, May 17, 2012 at 9:36 AM, Yinghai Lu >> wrote: >>> On Thu, May 17, 2012 at 5:34 AM, Steven Newbury >>> wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- Strange, the busn branch >>>> is merged with for-pci-res-alloc, but for some reason it >>>> isn't working. Only the bridge is detected, not the devices >>>> behind it. >>> >>> Can you post the boot log ? maybe recently reordering patches >>> applying sequence break it. >> >> Never mind, found the problem. > > updated for-pci-res-alloc branch. please check it. > Tested and working fine now. Some random update broke gnome-shell, so couldn't test it straight away. In the end I gave up fixing it and reverted to an earlier system snapshot. btrfs can be very useful! :) There is an outstanding issue with i915 though. With the moved BAR the screen remains blank when i915 loads (should show fbcon) and doesn't light up until X initialises. (X produces a modeset I assume.) After that everything works fine. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+6eu4ACgkQGcb56gMuC61InACfa+SvYmWXxJb3x1YTXOJhQWLE 0HkAoKcKhk7elSx1LIaxVdrxiBZibzDa =MaOP -----END PGP SIGNATURE-----