From owner-freebsd-hackers Sat Jan 13 7:30:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 8A25237B69C for ; Sat, 13 Jan 2001 07:29:54 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0DFTps26367; Sat, 13 Jan 2001 08:29:52 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101131529.f0DFTps26367@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Robert Lipe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bus_alloc_resource and RF_SHARABLE In-Reply-To: Your message of "Fri, 12 Jan 2001 22:39:49 CST." <20010112223949.R8978@rjlhome.sco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Jan 2001 08:29:51 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm on FreeBSD 4.1.1 and when I attempt multiple calls to >bus_alloc_resource on a PCI device for the same BAR, I run afoul of code >in resource_list_alloc: > > rle = resource_list_find(rl, type, *rid); > > if (!rle) > return 0; /* no resource of that type/rid */ > if (rle->res) > panic("resource_list_alloc: resource entry is busy"); > > >Even though I'm calling it with RF_SHARABLE RF_SHARABLE requests to share a resource with another device, not within the same device. Further, RF_SHARABLE only applies to IRQs, not BARs. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message