From owner-freebsd-current@FreeBSD.ORG Thu Sep 15 19:02:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD45516A41F for ; Thu, 15 Sep 2005 19:02:41 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2CAD43D49 for ; Thu, 15 Sep 2005 19:02:40 +0000 (GMT) (envelope-from minimarmot@gmail.com) Received: by xproxy.gmail.com with SMTP id h27so71882wxd for ; Thu, 15 Sep 2005 12:02:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=XipSSkYGMI9tRrWobOrgRDYVALE6tG7DzpuzMbzxsr7XCeQuwl26uBG8JP+0R1JGqW9ePXc2SOgrTg8ovgFQ5A7kLCqPUt/nGOe+faO4sd42DLVZN0R43eOA+REORUDD8LLCRfK8Sn3LtDYJb7cqN5rMGZOm6lVNIvWWKRNI7Zo= Received: by 10.70.12.20 with SMTP id 20mr442257wxl; Thu, 15 Sep 2005 11:34:38 -0700 (PDT) Received: by 10.70.9.2 with HTTP; Thu, 15 Sep 2005 11:34:38 -0700 (PDT) Message-ID: <47d0403c050915113475b8e99d@mail.gmail.com> Date: Thu, 15 Sep 2005 18:34:38 +0000 From: Ben Kaduk To: Bachilo Dmitry In-Reply-To: <200509151735.06711.root@solink.ru> Mime-Version: 1.0 References: <200509151735.06711.root@solink.ru> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: 3com wireless pccard X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: minimarmot@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2005 19:02:41 -0000 On 9/15/05, Bachilo Dmitry wrote: >=20 > Hello >=20 > I am having a problem with my 3com card. On my 5.4 i had to compile NDIS > drivers using original Windows XP drivers presented on drivers disk=20 > included > in this 3Com wirless device box. And it worked fine. >=20 > Now the system still compiles with device ndis and options NDISAPI but it > writes cardbus0: at device 0.0 (no driver attached) > instead of creating ndis0 device. >=20 > By the way device ath and device ath_hal do not compile since 5.4, but=20 > that's > other story, because this driver actually does not suppord my NIC. >=20 > Did I miss something about ndis in 6.0-CURRENT or do i do something wrong= ? >=20 > Best regards, Bachilo Dmitry. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >=20 The way the ndis driver works has been changed -- the ndis option/module=20 only generates infrastructure, it doesn't pull in the actual windows driver= s=20 anymore -- a separate utility (shell script) ndisgen is now used for this.= =20 Just type ndisgen at a root prompt and it should be fairly self-explanatory= .=20 This change allows the ndis framework to support more than one type of=20 windows driver at a time -- I have a BCMWL5_SYS.ko module for my wireless= =20 card, but I could also have a bcm4324.ko module for my onboard card (which= =20 is actually natively supported) and use them both at the same time. It is m= y=20 understanding that such dual-use was not possible before this change. Unfortunately, the documentation of this change is not in a prominent place= =20 (I missed it myself). Hope this solves your problem Ben Kaduk