From owner-freebsd-hackers@FreeBSD.ORG  Sat May  6 07:46:18 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3A78316A40B
	for <freebsd-hackers@freebsd.org>; Sat,  6 May 2006 07:46:18 +0000 (UTC)
	(envelope-from avalonwallace@gmail.com)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9004343D75
	for <freebsd-hackers@freebsd.org>; Sat,  6 May 2006 07:46:07 +0000 (GMT)
	(envelope-from avalonwallace@gmail.com)
Received: by py-out-1112.google.com with SMTP id e30so972690pya
	for <freebsd-hackers@freebsd.org>; Sat, 06 May 2006 00:46:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=CEfvIv+/bCD0wYg4Upu3o8WfW3bwseU7f0+4EtK6XObjBpq3kjISV1GoxSgGQbRk4qtuHxWh8YOc9lC1UAEd7Ht5kWEKB+K6cYi2hXRTu3V2pJjGc6Y1FCHq4Q0FSsD2ePwH5/YG/dA0mKu4JxXiQs23d5lNTT22q0A/LVlcgkg=
Received: by 10.35.88.17 with SMTP id q17mr193532pyl;
	Sat, 06 May 2006 00:46:06 -0700 (PDT)
Received: by 10.35.105.6 with HTTP; Sat, 6 May 2006 00:46:06 -0700 (PDT)
Message-ID: <3a60de0b0605060046l134240det7a900d556a74527f@mail.gmail.com>
Date: Sat, 6 May 2006 15:46:06 +0800
From: "Wallace William" <avalonwallace@gmail.com>
To: freebsd-hackers@freebsd.org, jhb@freebsd.org, imp@bsdimp.com
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: 
Subject: Re: misc questions about the device&driver arch
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 May 2006 07:46:18 -0000

I have seen this in the freebsd 5 road map,have the hotplug of pci already
merged into the RELENG_5 branch?

PCI resource allocation: PC2003 compliance requires that x86 systems no
longer configure PCI devices from the system BIOS, leaving this task solely
to the OS. FreeBSD must gain the ability to manage and allocate PCI memory
resources on its own. Implementing this should take into account cardbus,
PCI-HotPlug, and laptop dock station requirements. This feature will become
increasingly critical through the lifetime of RELENG_5, and therefore is a
requirement for the RELENG_5 branch.

On Thursday 10 November 2005 05:48 am, kylin wrote:
> Sir ,i am still puzzled by the windows and freebsd arch similar.
> 1
> the window TPS say that windwo allocate the resource window in default
> size of 1M or 2M,so there may be hole ,does that happen in freebsd 5
> or 6?


No.


> 2
> in my view i believe that freebsd us the "just enough "tactics,so
> the nexus level of resource view is =3D=3D=3Dcontinuous=3D=3D=3D=3Dwith N=
O hole in
> a boot up system, IF hot remove do not happen .am i right?


Sorta. We actually will use whatever the BIOS uses by default. We only try
to alloc resources if the BIOS doesn't, and I'm not sure how we handle a
bridge running out of resources. I think we might just fail the allocation.