From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 16:53:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 7285816A4CF; Sun, 25 Jan 2004 16:53:27 -0800 (PST) In-Reply-To: <20040125215957.GF4510@bombur.guldan.demon.nl> from Robert Blacquiere at "Jan 25, 2004 10:59:57 pm" To: freebsd-current@guldan.demon.nl (Robert Blacquiere) Date: Sun, 25 Jan 2004 16:53:27 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040126005327.7285816A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 00:53:27 -0000 > On Sat, Jan 24, 2004 at 07:49:00PM -0800, Bill Paul wrote: > > > If you have a system with one of these chipsets, please give the > > NDISulator a try. Note: you do NOT have to recompile your kernel to > > test it. Find the .sys and .inf files from your Windows driver media > > and do the following: > > > > # cp foo.sys foo.inf /sys/modules/if_ndis > > # cd /sys/modules/ndis > > # make; make load > > # cd /sys/modules/if_ndis > > # ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h > > # make; make load > > > > You don't even have to reboot. Well, not unless the driver causes > > a panic. :/ > > > > > Please correct me if i'm wrong but does this mean you can only use one single > instance of the ndis driver? If this stuff is really working i think we should > see more instances of the ndis, true? example a wireless card and a onboard > ethernet? Maybe more. How can you work around that problem? Yes you're wrong: you can use more than one NDIS driver. Say you want "bwe" (broadcom wireless) and "iwe" (Intel wireless) devices on the same machine: # mkdir /sys/modules/if_bwe # mkdir /sys/modules/if_iwe # cp /sys/modules/if_ndis/Makefile /sys/modules/if_bwe # cp /sys/modules/if_ndis/Makefile /sys/modules/if_iwe # cp bwe.sys bwe.inf /sys/modules/if_bwe # cp iwe.sys iwe.inf /sys/modules/if_iwe # cd /sys/modules/if_bwe # ndiscvt -n bwe -i bwe.inf -s bwe.sys ndis_driver_data.h # make # cp if_ndis.ko if_bwe.ko # cd /sys/modules/if_iwe.ko # ndiscvt -n iwe -i iwe.inf -s iwe.sys ndis_driver_data.h # make # cp if_ndis.ko if_iwe.ko You now have both if_bwe.ko and if_iwe.ko drivers. > It's just a thought, nothing more, i really like this thing because it helps > using strange hardware buildin laptops for example. Really cool stuff. You should have read the ndiscvt(8) man page before asking. Now, is anyone going to actually test Project Evil with their cards like I asked, or is everyone just going to use this as an excuse to ask me questions? -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================