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..
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..)
How difficult would CAMifying a driver be?
> 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.
> The NetBSD esp driver might be a good place to look for clues.
>
> Until the esp driver is ported, or someone makes the AMD driver work with
> those chips, you'll have to boot the machine diskless.
Yuck.
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
