From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: linux-next: build failure after merge of the final tree Date: Mon, 27 Feb 2012 20:19:20 +1100 Message-ID: <1330334360.11728.3.camel@pasglop> References: <20120227173747.853e7fbe3ce3afab8939720b@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:46249 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751250Ab2B0JTk (ORCPT ); Mon, 27 Feb 2012 04:19:40 -0500 In-Reply-To: <20120227173747.853e7fbe3ce3afab8939720b@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Jesse Barnes , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Helgaas , ppc-dev On Mon, 2012-02-27 at 17:37 +1100, Stephen Rothwell wrote: > pci_add_resource_offset(resources, res, > - (resource_size_t) hose->io_base_virt - _IO_BASE); > + (resource_size_t)(unsigned long)hose->io_base_virt - _IO_BASE); We have to be careful here as we do want sign extension to happen (yeah it's odd, but it's the way we do IOs on ppc32 :-) Maybe I should change it one day). So we probably want to do: (resource_size_t)(long long)(hose->io_base_virt - _IO_BASE) Basically, IO resources are relative to _IO_BASE which on ppc32 is basically the virtual address where we map the first PHB IO space. Subsequent PHB mappings can end up below _IO_BASE, leading to negative resource values for IO BARs on those busses. It all works fine because even an unsigned addition will do the right thing as long as the value is fully sign extended. Cheers, Ben.