From owner-freebsd-current Wed Apr 15 23:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23937 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:21:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23930 for ; Wed, 15 Apr 1998 23:21:14 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id AAA28394; Thu, 16 Apr 1998 00:17:30 -0600 (MDT) Date: Thu, 16 Apr 1998 00:17:30 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804160617.AAA28394@narnia.plutotech.com> To: Tom cc: current@FreeBSD.ORG Subject: Re: Help - please... Adaptec 1542 and Exabyte tape problem... Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > On Thu, 16 Apr 1998, Kerry Morse wrote: > >> Apr 16 13:35:05 proxy /kernel: aha0: DMA beyond end Of ISA: 0x357cd10 > > Bounce buffers are required to DMA above the 16MB for ISA devices. > However, bounce buffers do not work for the aha driver (it is unclear > whether the driver or the bounce buffers are broken). It's not the driver, and it's not the bounce buffers. It's the fact that several portions of the SCSI layer allocate objects that are the targets of DMA on the kernel stack and that a clude in scsi_scsi_cmd() to detect this and properly bounce the data does not work. > This is any old problem. See the archives. It seems that any developer > who has more than 16MB of RAM has also decided to upgrade to non-ISA > controllers. Bah. I implemented the Bus DMA version of bounce buffers just so ISA AdvanSys and Adaptec cards could be properly supported. The 1542 driver simply hasn't been completed yet for CAM. > Tom -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message