From owner-freebsd-current Thu Dec 10 21:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18762 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:46:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18755 for ; Thu, 10 Dec 1998 21:46:41 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA04099; Fri, 11 Dec 1998 14:43:38 +0900 (JST) Message-Id: <199812110543.OAA04099@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 17:01:56 PST." <199812110101.RAA01409@dingo.cdrom.com> Date: Fri, 11 Dec 1998 14:43:37 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want to bring PAO up to date, you should be looking at the > generic resource manager in sys/kern/subr_rman.c and the way that it > is integrated within the new bus architecture. I looked sys/kern/subr_rman.c, generic resource manager is quite correct. It is very necessary. Today's resource manager on PAO is quick and dirty hack, I agree. Because, until now we development 2.2-stable base and resource manager is necessary soon. In the future, we want to change generic resource manager base code. Does other PAO developer has different opinion? > If Garrett hasn't already contacted the entire PAO group, consider this > a formal request; if you're a PAO developer at all, and you're Sorry, I don't know. I will ask other PAO developer. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message