Date: Sun, 13 Dec 1998 15:21:25 -0800 From: Mike Smith <mike@smith.net.au> To: Atsushi Furuta <furuta@sra.co.jp> Cc: dfr@nlsystems.com, mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? Message-ID: <199812132321.PAA00350@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 13 Dec 1998 19:23:08 %2B0900." <199812131023.TAA05525@sramhc.sra.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> In article <Pine.BSF.4.01.9812112302020.1148-100000@herring.nlsystems.com>, > Doug Rabson <dfr@nlsystems.com> 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. Flags are bad. They exist at all because it was hard to specify meaningful options to drivers via config (which couldn't know anything about the driver structure). Drivers should export a set of options that are a union of the set of options the driver supports plus a subset of the options for a device provided by the bus. This can be determined by examining the driver and bus data at probe/attach time; something that's easy with KLD/ newbus/loader, but would require a bolt-on for newconfig. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812132321.PAA00350>