Date: Tue, 6 Apr 1999 11:05:34 -0700 (PDT) From: wpaul@FreeBSD.ORG (Bill Paul) To: dcs@newsguy.com (Daniel C. Sobral) Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man4/man4.i386 ti.4 src/release/textsHARDWARE.TXT RELNOTES.TXT src/release/sysinstall devices.cs Message-ID: <19990406180535.1A735156CA@hub.freebsd.org> In-Reply-To: <370A44E1.BECA2307@newsguy.com> from "Daniel C. Sobral" at "Apr 7, 1999 2:31:13 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Bill Paul wrote: > > > > I have not added the 'device ti0' entry to GENERIC since the driver > > with all the firmware compiled in is quite large, and it doesn't really > > fit into the category of generic hardware. > > If one wants to net install through it, it needs to be in GENERIC. I seriously doubt you will find many people doing network installs over gigabit ethernet adapters. We don't have ATM drivers in the GENERIC kernel; why should we have gigabit ethernet. > Unless, of course, we (you... :) make a kld out of it. Oh sure, it's very easy to say that. Except DOESN'T WORK. I've been there. I've done that. I've watched it fail miserably. Linker sets are not resolved when a KLD is loaded so even if you pre-load the driver along with the kernel image, the probe routine is never called because the pci linker set is never updated to contain a pointer to the driver's set structure. And don't try to goad me into doing it. The people who designed/wrote the KLD support and then left it unfinished are the ones you should be pestering. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990406180535.1A735156CA>