From owner-freebsd-arch@freebsd.org Thu Jan 7 04:23:00 2021 Return-Path: Delivered-To: freebsd-arch@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3C5D14C2535 for ; Thu, 7 Jan 2021 04:23:00 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail01.asahi-net.or.jp (mail01.asahi-net.or.jp [202.224.55.13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DBCl61nfWz4Vyk for ; Thu, 7 Jan 2021 04:22:57 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from localhost (cpe-184-152-96-96.nj.res.rr.com [184.152.96.96]) (Authenticated sender: NR2Y-OOT) by mail01.asahi-net.or.jp (Postfix) with ESMTPSA id 1AEEE112F8E for ; Thu, 7 Jan 2021 13:22:53 +0900 (JST) Date: Wed, 6 Jan 2021 23:20:38 -0500 From: Yoshihiro Ota To: freebsd-arch@freebsd.org Subject: Re: RFC: removing ndis(4) Message-Id: <20210106232038.9fd928646cb34933578fd29c@j.email.ne.jp> In-Reply-To: <178622db-7dcd-fcae-743c-883711121733@kondratyev.su> References: <20201203001247.GF18452@spindle.one-eyed-alien.net> <178622db-7dcd-fcae-743c-883711121733@kondratyev.su> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; i386-portbld-freebsd12.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4DBCl61nfWz4Vyk X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ota@j.email.ne.jp designates 202.224.55.13 as permitted sender) smtp.mailfrom=ota@j.email.ne.jp X-Spamd-Result: default: False [0.37 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:202.224.55.0/24]; TO_DN_NONE(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; RECEIVED_SPAMHAUS_PBL(0.00)[184.152.96.96:received]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[202.224.55.13:from]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:4685, ipnet:202.224.32.0/19, country:JP]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_IN_DNSWL_LOW(-0.10)[202.224.55.13:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.17)[0.173]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; DMARC_NA(0.00)[email.ne.jp]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[202.224.55.13:from:127.0.2.255]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arch] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2021 04:23:00 -0000 On Thu, 3 Dec 2020 06:28:00 +0300 Vladimir Kondratyev wrote: > On 03.12.2020 03:12, Brooks Davis wrote: > > I'd like to propose that we remove the ndis(4) driver prior to FreeBSD > > 13. It was a clever idea in the early 2000's when the market was > > flooded with 10/100 NICs with Windows-only drivers, but that hasn't been > > the case for ages and the driver has had no meaningful maintenance in > > ages[0]. I'd be a bit surprised if it worked at all today (it surely > > won't work with modern Windows drivers). > > > > To try to examine the popularity of ndis, I checked dmesgd.nycbug.org > > and there are 5 total entries with the most recent being 2007. > > > > The PC Card attachments are currently marked for deletion prior to > > FreeBSD 13. > > > > Unless there is surprising outcry I plan to add (and MFC) deprecation > > notices in about a week's time and remove the driver shortly thereafter. > > > > -- Brooks > > > > [0] I noticed today that part of the ndis 802.11 ioctl handler has been > > broken since 2005. > > ndis(4) was functional at least in 2015 and at that time it was the only > way to utilize BCM's wi-fi built in my "Asus EEEPC" ndis is still functional and indeed I have one of Asus that only works NDIS BCM. A problem is an old hardware needs existing code working although new hardware gets new hardware and driver. It was indeed broken long while ago but my fix was merged. If I remember correctly, my fix went to 11.0-RELEASE. It will be nice if we can wait after 13-release branching. Hiro