Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752853AbbDBUhT (ORCPT ); Thu, 2 Apr 2015 16:37:19 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:41304 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752540AbbDBUhR (ORCPT ); Thu, 2 Apr 2015 16:37:17 -0400 Date: Thu, 02 Apr 2015 16:37:15 -0400 (EDT) Message-Id: <20150402.163715.643586069492103151.davem@davemloft.net> To: yinghai@kernel.org Cc: bhelgaas@google.com, david.ahern@oracle.com, linux-pci@vger.kernel.org, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] PCI/sparc: Fix booting with T5-8 From: David Miller In-Reply-To: <1427857069-6789-1-git-send-email-yinghai@kernel.org> References: <1427857069-6789-1-git-send-email-yinghai@kernel.org> X-Mailer: Mew version 6.5 on Emacs 24.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 02 Apr 2015 13:37:17 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 25 From: Yinghai Lu Date: Tue, 31 Mar 2015 19:57:46 -0700 > Fix regression by commit d63e2e1f3df9 ("sparc/PCI: Clip bridge windows to > fit in upstream windows"). > > That cause bridge bar get clipped wrongly. > > The sparc64 dma_addr_t is 32-bit, we can not use it to check if we can > use 64bit bar, introduce pci_bus_addr_t. > > sparc ofpci does not parse 64bit mem for root bus, add code to > make sure that we get correct resource for root. > > Also there are device 64-bit res does not have pref bit flag, but bridges > do have pref bit set, that cause extra "no compatible window". > Set pref bit for them according to the errata. Just to be clear, who is going to merge this? :-) -- 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/