From owner-freebsd-stable@FreeBSD.ORG Tue Jul 5 13:19:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22DFB16A41C for ; Tue, 5 Jul 2005 13:19:32 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E40143D45 for ; Tue, 5 Jul 2005 13:19:31 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 8597 invoked from network); 5 Jul 2005 13:19:28 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[83.129.48.47]) (envelope-sender ) by smtprelay02.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 5 Jul 2005 13:19:28 -0000 Date: Tue, 5 Jul 2005 15:19:32 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20050705151932.783200e6@localhost> X-Mailer: Sylpheed-Claws 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Signature_Tue__5_Jul_2005_15_19_32_+0200_65ok7v5pxIJ+Arjc; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: ndisgen intended to be the only way to generate ndis? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2005 13:19:32 -0000 --Signature_Tue__5_Jul_2005_15_19_32_+0200_65ok7v5pxIJ+Arjc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi all, as you probably have noticed, the amount of mails about problems with compiling ndis has increased in the last four weeks. The "old" way to compile ndis was to go to=20 /usr/src/sys/modules/if_ndis/, use ndiscvt to create a header file containing the windows driver and to make;make install. =20 It was fast and well documented in the handbook and on the web in general. Later Bill Paul wrote /usr/sbin/ndisgen to automate these steps. ndisgen is an interactive shell script, it is user friendly and describes what it's doing. However, using it is slower than the "old" way was. You can't use shell auto completion to specify the location of the drivers sys and inf files, some steps are done, even if they aren't needed each time you recompile ndis. ATM the existence of ndisgen is poorly documented. It's not mentioned in the handbook, not in the man pages and seldom appears on other websites. If you don't read the mailing lists or the cvs logs, you probably won't know about it. =20 For a while the "new" and the "old" way coexisted, everybody was happy. Since perhaps four weeks, the "old" way stopped working for many (all?) people. You can still build and kldload the needed modules without error, but they will not work. Most of the time (every time?) ndisgen still does. AFAIK, nobody has announced that the "old" way is death, therefore I would like to know if the breakage is intentional and if it is, if there's a technical reason why these methods can no longer coexists.=20 Mark A-J. Raught wrote on freebsd-mobile yesterday:=20 "I prefer the old way, but as long as it works I'll suffer through the wizard feel." So do I, I guess we're not alone. Fabian --=20 http://www.fabiankeil.de/ --Signature_Tue__5_Jul_2005_15_19_32_+0200_65ok7v5pxIJ+Arjc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCyoj0oomUOj0wp30RAk1nAJ90Ngs3ONV2pmlkV+LFkg5fJApqAwCfYq5v aqezgkEvFYqN8+zWH+jTnkM= =U385 -----END PGP SIGNATURE----- --Signature_Tue__5_Jul_2005_15_19_32_+0200_65ok7v5pxIJ+Arjc--