From owner-freebsd-hackers Thu Oct 7 15:52:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 75DB8153CC for ; Thu, 7 Oct 1999 15:52:15 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA97898; Thu, 7 Oct 1999 16:50:02 -0600 (MDT) (envelope-from ken) Message-Id: <199910072250.QAA97898@panzer.kdm.org> Subject: Re: Turbochannel based Alpha, quickie question In-Reply-To: <199910072201.AAA43983@yedi.iaf.nl> from Wilko Bulte at "Oct 8, 1999 00:01:34 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Thu, 7 Oct 1999 16:50:02 -0600 (MDT) Cc: FreeBSD-hackers@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote... > As Kenneth D. Merry wrote ... > > Wilko Bulte wrote... > > > > I have the distinct (bad) feeling this is due to: > > > > > > # A single entry for any of these controllers (ncr, ahb, ahc, amd) is > > > # sufficient for any number of installed devices. > > > controller ncr0 > > > controller isp0 > > > #controller esp0 > > > > > > in GENERIC. I mean, esp is the driver for the 53C94 ncr scsi chip. > > > Is there any particular reason why it is commented out in GENERIC? > > > Floppy disk size limit maybe? > > > > The esp driver hasn't been ported to CAM. Are you volunteering? :) > > I noticed that when I tried to compile a TC-enabled kernel on my Aspen > Alpine. Sort of familiar looking header files were missing ;-) Pre-CAM > files obviously. > > Volunteering... if I could find the time. Unlikely.. Bummer. > Is there a description somewhere how I can create my own test boot > floppies? (I have a SCSI-interfaced floppy disk; works great BTW). > I found write_mfs_in_kernel but the Makefile in /usr/src/release sort of > escapes me in this respect (also in other respects to be honest..) You should probably look at the PicoBSD stuff. > How difficult would CAMifying a driver be? Like the esp driver? I dunno. I haven't done it, so I can't say for sure. It looks like the esp-type chips don't have an on-board phase engine, so the driver has to do the work. So the driver behavior may be a little bit more complicated than a driver for a mailbox-type card. My guess is that it would be easier to write a TC front end for the amd driver. > > One other, perhaps easier task might be to write a TurboChannel front end > > for the AMD driver. Supposedly the AMD 53c974 and NCR 53C94 are pretty > > much the same chip. > > Sounds like one needs to dig into the TC idiosyncrasies. I'd rather not. I think that writing a TC attach routine for the AMD driver would be a good deal easier than porting the esp driver to CAM. It seems like the NCR 53C94 and AMD 53C974 chips are pretty similar. I tell you what -- if you're serious about getting this working, talk to me offline, and maybe I'll do the driver. I'd obviously need hardware, though, since I don't have any of the hardware in question. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message