Date: Wed, 6 May 1998 12:07:28 -0600 (MDT) From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> To: Jason Thorpe <thorpej@nas.nasa.gov> Cc: net@FreeBSD.ORG Subject: Re: ethernet Message-ID: <199805061807.MAA05103@narnia.plutotech.com> In-Reply-To: <199805051526.IAA22952@lestat.nas.nasa.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
> > device ed0 at isa? port 0x300 net irq 9 iomem 0xd8000 vector edintr > > > > from kernel configuration it does not assign a driver for the ethernet > > card... > > why is this happening? > > Because FreeBSD doesn't have a flexible autoconfiguration system, so they > require hacks that glue drivers for PCI devices which are similar to ISA > devices to the ISA drivers themselves. > > We addressed this in NetBSD ... quite some time ago. Although I will agree that FreeBSD's configuration system sucks rocks, your analysis here is incorrect. You can, with the exception of some trickery with unit number handling, cleanly create PCI/EISA/ISA attach stubs for a "generic" driver. All of the CAM SCSI drivers do this, but there are certainly "older drivers" that could use cleanup in this area. I'm still waiting to see NetBSD cleanly deal with LKMs in it's autoconfiguration code. Config.new is not the answer to all configuration problems, although I will admit that it is much better than FreeBSD's current config nightmare. > Jason R. Thorpe thorpej@nas.nasa.gov > NASA Ames Research Center Home: +1 408 866 1912 > NAS: M/S 258-5 Work: +1 650 604 0935 > Moffett Field, CA 94035 Pager: +1 415 428 6939 -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805061807.MAA05103>