From owner-freebsd-current Mon Dec 14 01:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03205 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:43:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03199 for ; Mon, 14 Dec 1998 01:43:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA49992; Mon, 14 Dec 1998 09:42:22 GMT Date: Mon, 14 Dec 1998 09:42:22 +0000 (GMT) From: Doug Rabson To: Atsushi Furuta cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812131023.TAA05525@sramhc.sra.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Dec 1998, Atsushi Furuta wrote: > >> In article , > Doug Rabson writes: > > > The softc issue is addressed by the new device framework. The pci support > > code has not yet been updated to the new interface but when it is, it will > > get this for free. The flags field can also be easily added. > > I wonder how a user specifies flags to pci bus. I seems that there > is no generic way to specify flags in current subr_bus.c, and it is up > to each bus codes how to provide ivers and flags. It is true that there is no flags field hardcoded into the device. As you have noted, it is easy for any bus for which it is relavent to implement one using ivars. It is also easy for a bus implementation to pick up flags and device wiring preferences from config(8). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message