From owner-freebsd-stable@FreeBSD.ORG  Thu Sep 18 01:39:22 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 05125106564A
	for <freebsd-stable@freebsd.org>; Thu, 18 Sep 2008 01:39:22 +0000 (UTC)
	(envelope-from kaho@ed.niigata-u.ac.jp)
Received: from mxav03.cc.niigata-u.ac.jp (mxav03.cc.niigata-u.ac.jp
	[133.35.17.131])
	by mx1.freebsd.org (Postfix) with ESMTP id B9F438FC17
	for <freebsd-stable@freebsd.org>; Thu, 18 Sep 2008 01:39:21 +0000 (UTC)
	(envelope-from kaho@ed.niigata-u.ac.jp)
Received: from mxav03.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP id 31F3A2900F5
	for <freebsd-stable@freebsd.org>; Thu, 18 Sep 2008 10:39:20 +0900 (JST)
Received: from pf2.ed.niigata-u.ac.jp (pf2.ed.niigata-u.ac.jp [133.35.172.22])
	by mxav03.cc.niigata-u.ac.jp (Postfix) with ESMTP id 11F392900A3
	for <freebsd-stable@freebsd.org>; Thu, 18 Sep 2008 10:39:20 +0900 (JST)
Received: from pf2.ed.niigata-u.ac.jp (localhost [127.0.0.1])
	by pf2.ed.niigata-u.ac.jp (8.14.3/8.14.3) with ESMTP id m8I1dJEt067791
	for <freebsd-stable@freebsd.org>; Thu, 18 Sep 2008 10:39:19 +0900 (JST)
	(envelope-from kaho@pf2.ed.niigata-u.ac.jp)
Message-Id: <200809180139.m8I1dJEt067791@pf2.ed.niigata-u.ac.jp>
To: freebsd-stable@freebsd.org
From: KAHO Toshikazu <vinwa@rocky.kais.kyoto-u.ac.jp>
References: <200809171137.32759.jhb@freebsd.org>
User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?S?=
	=?ISO-8859-4?Q?hij=F2?=) APEL/10.7 Emacs/21.3 (i386--freebsd) MULE/5.0
	(SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 18 Sep 2008 10:39:19 +0900
Sender: kaho@ed.niigata-u.ac.jp
Subject: Re: alpm(4) I/O range is claimed by ACPI
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2008 01:39:22 -0000

  Hello,

> Well, bus_alloc_resource() will allocate resources for the BAR and update the 
> BAR for you, the question is if you need to hardcode the range to 
> bus_alloc_resource() or not.

It is necessary for a pci device to set the BAR, if the device
would use memory or I/O space, isn't it? I don't know why the
BAR is not settable, but I think it is disabled by some reasons
and the BAR may be settable if the device could be enabled.

If the device have default I/O space, it needs to hardcode the
range or isa attach code. The device dose not seem to have
default I/O space.

This problem is not so important for myself, but it is a good if
it was solved.

-- 
KAHO Toshikazu