From owner-freebsd-current Fri Aug 8 18:38:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29345 for current-outgoing; Fri, 8 Aug 1997 18:38:01 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29338 for ; Fri, 8 Aug 1997 18:37:58 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id TAA18122; Fri, 8 Aug 1997 19:37:55 -0600 (MDT) Message-Id: <199708090137.TAA18122@pluto.plutotech.com> To: Alex cc: current@FreeBSD.ORG Subject: Re: 93cx6.c?? In-reply-to: Your message of "Fri, 08 Aug 1997 17:26:39 MST." Date: Sat, 09 Aug 1997 01:37:43 +0000 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I read the comments at the beginning of this file, and it appears to be a >serial eeprom driver. So the question is, why's it in the scsi directory? > >- alex Because it is only used by the aic7xxx.c driver and it's interface, although somewhat generic, may not work for accessing 93cx6 seeproms on other devices. For example, I recently added support to read the seeprom on a 2842 to this code (not yet committed) and I had to make quite a few changes to the interface to make if flexible enough to be shared by the 2842 probe code and the aic78X0 probe code. I believe that the there are quite a few drivers (de??, fxp??) that access a 93cx6, so it may be worth changing the interface to make it even more flexible and making these other drivers use it, but until that happens, I don't think its worth moving it. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================