Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754486AbbEPPZn (ORCPT ); Sat, 16 May 2015 11:25:43 -0400 Received: from mail-ie0-f171.google.com ([209.85.223.171]:34013 "EHLO mail-ie0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754089AbbEPPZl (ORCPT ); Sat, 16 May 2015 11:25:41 -0400 Date: Sat, 16 May 2015 10:25:37 -0500 From: Bjorn Helgaas To: Yinghai Lu Cc: David Miller , David Ahern , 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 Message-ID: <20150516152537.GJ31666@google.com> References: <1427857069-6789-1-git-send-email-yinghai@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1427857069-6789-1-git-send-email-yinghai@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 26 On Tue, Mar 31, 2015 at 07:57:46PM -0700, Yinghai Lu wrote: > 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. Ping, any updates on this? AFAICT, we should add a new pci_bus_addr_t distinct from dma_addr_t, but Ben raised an issue that needs to be resolved first. Bjorn -- 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/