From owner-freebsd-current@FreeBSD.ORG Mon Aug 4 11:13:16 2003 Return-Path: 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 7C1DD37B401 for ; Mon, 4 Aug 2003 11:13:16 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78E2443FCB for ; Mon, 4 Aug 2003 11:13:13 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h74IDBFL013100; Mon, 4 Aug 2003 12:13:12 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 04 Aug 2003 12:13:06 -0600 (MDT) Message-Id: <20030804.121306.56057503.imp@bsdimp.com> To: brad.knowles@skynet.be From: "M. Warner Losh" In-Reply-To: References: <20030804044432.GV95375@wantadilla.lemis.com> <20030803.235155.123970624.imp@bsdimp.com> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Lucent IBSS mode doesn't work in -CURRENT? 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, 04 Aug 2003 18:13:16 -0000 In message: Brad Knowles writes: : bit annoying, but it seems to me that he's asking a perfectly : legitimate question -- if things worked fine in the past (including : the firmware versions at the time), and they don't work now, then why : is a firmware update needed? The problem is that the driver maintainers know it is a problem, know that newer firmware is a workaround and haven't had the time to find and fix the underlying bug. Having people say that it isn't a fix only a workaround repeatedly is annoying, since that's the position we've taken from the get go. The driver was massively rewritten to speed up intersil cards. The reason that a firmware update is needed is that the old driver worked around bugs in the firmware, but the new driver doesn't. The new driver tries to increase performance on prism cards by using newer features of the firmware. These features aren't present in the older wavelan firmwares. Trouble is, I'm not exactly sure which of the new, cool things causes the problems. I've already identified 3 or 4, which makes some lucent cards work on some systems, but I don't know the others. Warner