From: Steven Newbury <steve@snewbury.org.uk>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Barnes, Jesse" <jesse.barnes@intel.com>,
Dave Airlie <airlied@linux.ie>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: PCI resources above 4GB
Date: Sun, 15 Apr 2012 11:20:12 +0100 [thread overview]
Message-ID: <4F8AA0DC.6010902@snewbury.org.uk> (raw)
In-Reply-To: <CAE9FiQVwDNM9MkqG_g139LDf6Ypjx0uygzVqosDe=fF=c_Y3gA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14/04/12 21:48, Yinghai Lu wrote:
> On Sat, Apr 14, 2012 at 12:21 PM, Steven Newbury
> <steve@snewbury.org.uk> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 14/04/12 20:08, Steven Newbury wrote:
>>> On 14/04/12 19:42, Steven Newbury wrote:
>>>> On 14/04/12 19:05, Steven Newbury wrote:
>>>>> On 14/04/12 18:37, Steven Newbury wrote:
>>>>>> On 12/04/12 17:40, Steven Newbury wrote:
>>>>>>> On Thu, 12 Apr 2012, 17:07:33 BST, Yinghai Lu
>>>>>>> <yinghai@kernel.org> wrote:
>>>
>>>>>>>> On Thu, Apr 12, 2012 at 4:22 AM, Steven Newbury
>>>>>>>> <steve@snewbury.org.uk> wrote:
>>>>>>>>> Thanks, that fixed it! :) I had a similar patch
>>>>>>>>> I've been working on but I had my fix in the wrong
>>>>>>>>> place!
>>>>>>>>>
>>>>>>>>> In the working case, initially the BIOS has set
>>>>>>>>> GMA to within the low system DRAM 0xC0000000
>>>>>>>>> obviously invalid. This conflict is detected and
>>>>>>>>> it's relallocated to 0x12000000.
>>>>>>>>>
>>>>>>>>> I've attempted to modify probe.c to disable 64-bit
>>>>>>>>> BARs not allocated above 4G so they get
>>>>>>>>> reallocated above when possible later. It seemed
>>>>>>>>> to work, but again broke GMA despite the BAR
>>>>>>>>> originally containing an invalid address as
>>>>>>>>> mentioned above, it seems for some reason
>>>>>>>>> something is different when the conflict is
>>>>>>>>> detected and rellocated, compared to disabling it
>>>>>>>>> early then allocating a valid value..?
>>>>>>>>>
>>>>>> I've created a new quirk utilising an extra PCI resource
>>>>>> flag to force reallocation of the resource. It's the
>>>>>> first approach I've had any success at. It does work.
>>>>>> Only "Intel Page Flush" now gets allocated @0xe0000000!
>>>
>>>
>>>>> Hopefully this should fix "Intel Flush Page"
>>>> Need to export pci_bus_alloc_resource_fit for intel-gtt.
>>> Nearly worked... Or at least it should have worked, but for
>>> some reason the allocator failed to utilise
>>> 0xe0000000-0xefffffff for 04:00.0 BAR0..?
>>>
>>>
>>> pci 0000:03:08.0: BAR 15: can't assign mem pref (size
>>> 0x18000000)
>> Ah! Not enough space for the bridge window!:(
>>
>
> please append pci=norom ...
>
That worked. Except of course the radeon driver can't POST the card
without the ROM! :-P
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+KoNwACgkQGcb56gMuC62uAACfdaoIb/NT7+7xGIa4G+Wtw0K0
/IsAoL8NIg6g4q3qoTJuQpp6WyqDYUfu
=OzC5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-04-15 10:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1333968563.5678.19.camel@infinity>
[not found] ` <CAErSpo7hGvJSmq4U37XN9T7ZaYn55fyy9t3ER5BBCDdQ3XZxqw@mail.gmail.com>
[not found] ` <4F84110E.3000400@snewbury.org.uk>
[not found] ` <CAE9FiQVHf_pcXUspOtLXx4XminmzdWja3Ra2Wh5jQRbfNOQ1eQ@mail.gmail.com>
[not found] ` <4F8467AA.90305@snewbury.org.uk>
[not found] ` <CAE9FiQWaop0NE7ZJu6jVW3SnxLkOJ9hRKh4xMNk64XjCAMRMMw@mail.gmail.com>
[not found] ` <4F848357.3060007@snewbury.org.uk>
[not found] ` <CAE9FiQXTgh3X4x+xD1T0ipsEbhbPtctYucfGeuWK=cq7kHeZ1Q@mail.gmail.com>
[not found] ` <4F848E10.1090703@snewbury.org.uk>
[not found] ` <CAE9FiQXvwYrJhLi91VDVtD4+OOfbGQ1U20-Cap+8tBZUt7QCkA@mail.gmail.com>
[not found] ` <1334089568.4083.2.camel@Nokia-N900>
[not found] ` <CAE9FiQWnvB2VbBQQaEnDE0nf+Zwy6nyoGrEuVrUesQEzgYfbvA@mail.gmail.com>
[not found] ` <4F84A3EC.6030903@snewbury.org.uk>
2012-04-12 0:57 ` PCI resources above 4GB Yinghai Lu
2012-04-12 11:22 ` Steven Newbury
2012-04-12 16:07 ` Yinghai Lu
2012-04-12 16:40 ` Steven Newbury
2012-04-13 8:26 ` Yinghai Lu
2012-04-13 8:34 ` Steven Newbury
2012-04-13 11:45 ` Steven Newbury
2012-04-13 11:58 ` Steven Newbury
2012-04-13 12:49 ` Steven Newbury
2012-04-13 13:26 ` Steven Newbury
2012-04-13 13:52 ` drm-next i915 regression? ( was: Re: PCI resources above 4GB) Steven Newbury
2012-04-13 14:08 ` Steven Newbury
2012-04-13 14:13 ` Daniel Vetter
2012-04-13 14:19 ` Steven Newbury
2012-04-13 15:23 ` Steven Newbury
2012-04-13 15:49 ` Steven Newbury
2012-04-13 16:17 ` Yinghai Lu
2012-04-13 17:12 ` btrfs oops [was Re: drm-next i915 regression? ( was: Re: PCI resources above 4GB)] Steven Newbury
2012-04-13 17:38 ` drm-next i915 regression? ( was: Re: PCI resources above 4GB) Steven Newbury
2012-04-13 18:12 ` Steven Newbury
2012-04-13 21:51 ` Btrfs corruption Oops " Steven Newbury
2012-04-14 17:37 ` PCI resources above 4GB Steven Newbury
2012-04-14 18:05 ` Steven Newbury
2012-04-14 18:42 ` Steven Newbury
2012-04-14 19:08 ` Steven Newbury
2012-04-14 19:21 ` Steven Newbury
2012-04-14 20:48 ` Yinghai Lu
2012-04-15 10:19 ` Steven Newbury
2012-04-15 10:20 ` Steven Newbury [this message]
2012-04-15 11:37 ` Steven Newbury
2012-04-15 17:25 ` Steven Newbury
2012-04-15 17:31 ` Steven Newbury
2012-04-15 20:05 ` Yinghai Lu
2012-04-15 20:06 ` Yinghai Lu
2012-04-16 6:54 ` Yinghai Lu
2012-04-16 7:01 ` Steven Newbury
2012-04-16 17:29 ` Yinghai Lu
2012-04-18 7:21 ` Steven Newbury
2012-04-24 9:49 ` Steven Newbury
[not found] ` <4FB227D3.7090002@snewbury.org.uk>
[not found] ` <CAE9FiQX48eCS85eWMFxm6fCWgu2zwxvSywtQhsf-35WEvBfJVQ@mail.gmail.com>
2012-05-17 12:27 ` Steven Newbury
2012-05-17 12:34 ` Steven Newbury
2012-05-17 16:36 ` Yinghai Lu
2012-05-18 7:45 ` Yinghai Lu
2012-05-18 9:08 ` Yinghai Lu
2012-05-21 17:27 ` Steven Newbury
2012-05-29 23:19 ` Bjorn Helgaas
2012-06-01 23:06 ` Bjorn Helgaas
2012-04-15 3:21 ` Yinghai Lu
2012-04-15 10:18 ` Steven Newbury
2012-04-15 11:31 ` Steven Newbury
2012-04-12 16:29 ` Steven Newbury
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=4F8AA0DC.6010902@snewbury.org.uk \
--to=steve@snewbury.org.uk \
--cc=airlied@linux.ie \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/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