From owner-freebsd-hardware Thu Apr 24 10:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20277 for hardware-outgoing; Thu, 24 Apr 1997 10:44:10 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA20227 for ; Thu, 24 Apr 1997 10:44:03 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id LAA12904; Thu, 24 Apr 1997 11:43:12 -0600 (MDT) Message-Id: <3.0.1.32.19970424112814.0070acb4@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 24 Apr 1997 11:28:14 -0600 To: Peter Dufault From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@freebsd.org In-Reply-To: <199704240938.FAA02994@hda.hda.com> References: <3.0.1.32.19970423175524.006f61c4@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:38 AM 4/24/97 -0400, Peter Dufault wrote: >Use a 1542B only to remove the lack of another adapter as a block >in the software development path, and only use 16MB of memory if >you do that. I strongly recommend the NCR where you'll have multiple >vendors and control over the firmware. But can I use FreeBSD in the embedded system? Is there a target mode driver for any of the NCR chips? --Brett