From owner-freebsd-mobile Mon Dec 11 22: 1:39 2000 From owner-freebsd-mobile@FreeBSD.ORG Mon Dec 11 22:01:37 2000 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AE82837B400 for ; Mon, 11 Dec 2000 22:01:36 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eBC61Zs72111; Mon, 11 Dec 2000 23:01:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA27185; Mon, 11 Dec 2000 23:01:35 -0700 (MST) Message-Id: <200012120601.XAA27185@harmony.village.org> Subject: Re: patch for wi driver To: YAMAMOTO Shigeru , freebsd-mobile@FreeBSD.org In-reply-to: Your message of "Mon, 11 Dec 2000 21:15:40 PST." References: Date: Mon, 11 Dec 2000 23:01:35 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Dirk-Willem van Gulik writes: : Thanks Yamamoto san ! This works really rather nicely and has reduce the : number of tx errors tremendously (Though not completely and xmit : failed/device timeout is still there). Yes. But it doesn't work with my 3com AirConnect (3crwe737a rev b) now. I get 'wi0: init failed' messages when I insert it, with and without the 0x10000 flag. :-(. The AirConnect is based on the prism II chipset. I'll have to see what other changes NetBSD has made to the wi driver to see if I can get that working.... That is assuming that Bill Paul's breaking it open at BSDcon didn't damage it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message