Date: Fri, 06 Mar 1998 16:10:20 -0800 From: Julian Elischer <julian@whistle.com> To: Tom <tom@sdf.com> Cc: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>, hackers@FreeBSD.ORG Subject: Re: http://www.dpt.com/os2.htm Message-ID: <3500906C.7566F4CF@whistle.com> References: <Pine.BSF.3.95q.980305173821.15778E-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tom wrote: > > On Fri, 6 Mar 1998, Julian Elischer wrote: > > > Justin T. Gibbs wrote: > > > Last I looked at the DPT driver, it required the same software interrupt > > > hooks that CAM required. I don't think that we can make these changes > > > so close to the 2.2.6 release, but I will merge them in after 2.2.6 is > > > cut. > > > > the DPT driver for 2.2 (which I have in my tree ready to commit) > > supplies it's own software interrupt hooks which can be discarded when > > the CAM stuff is merged in. > > That is what I thought. > > Can those hooks be conditionally compiled to reassure those how are > skeptical about the DPT driver? At least the DPT driver can be shipped in > 2.2.6 tree then. I have done this.. I have checked in teh DPT driver into 2.2.x all the CHANGES (as opposed to new files) are conditional on DPTOPT. I thought it would be the safest way to do it so close to release time. so you need to add options DPTOPT to your config file as well as the more usual controller dpt0 the DPTOPT will go away after the release and when it's proven to work. > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3500906C.7566F4CF>