From owner-freebsd-current Sat Mar 20 11:37:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles95.castles.com [208.214.165.95]) by hub.freebsd.org (Postfix) with ESMTP id 5BC9514F93 for ; Sat, 20 Mar 1999 11:36:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA12494 for ; Sat, 20 Mar 1999 11:30:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903201930.LAA12494@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 10:58:56 +0100." <199903200958.KAA35050@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Mar 1999 11:30:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But hey, I don't have the time to work on ATAPI. Soren does, so he g= ets > > to call the shots. > = > Right :) =2E.. so we lose. 8( Soren, please take a little time to understand what Justin is talking = about. The parts of CAM that are relevant to you are the queueing = support, infrastructure, and the separation between the "interface = controller" and the "peripheral driver", something that you've = indicated to me several times that you simply don't grasp. Taking advantage of all the code and design that's already been = implemented in the CAM framework will make your life easier, not = harder. It's not necessary to write a translation layer at all, if = such a thing offends your sensibilities. -- = \\ 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