Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 7 Aug 2002 09:44:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 7 Aug 2002 09:44:47 -0400 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:4847 "EHLO passion.cambridge.redhat.com") by vger.kernel.org with ESMTP id ; Wed, 7 Aug 2002 09:44:46 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: David Woodhouse X-Accept-Language: en_GB In-Reply-To: References: To: "Scott Murray" Cc: Linux Kernel Mailing List Subject: Re: RFC: PCI hotplug resource reservation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Aug 2002 14:48:23 +0100 Message-ID: <22223.1028728103@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 19 scottm@somanetworks.com said: > However, it's entirely possible that you will be allocated resource > ranges that are intermingled with the ranges that are behind other > bridges or devices. There's no sane way to program the hotplug > bridge's BARs in such a situation. Why? Can't you just forward transactions for the whole of the range, including some addresses which are actually behind other bridges? -- dwmw2 - 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/