From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 8 23:49:37 2007 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B4EB16A418 for ; Sat, 8 Dec 2007 23:49:37 +0000 (UTC) (envelope-from vk3qq@optusnet.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id ECA2213C44B for ; Sat, 8 Dec 2007 23:49:36 +0000 (UTC) (envelope-from vk3qq@optusnet.com.au) Received: from LISA.optusnet.com.au (c220-237-172-76.lowrp1.vic.optusnet.com.au [220.237.172.76]) (authenticated sender vk3qq@optusnet.com.au) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lB8Nm9BL020372; Sun, 9 Dec 2007 10:48:11 +1100 Message-Id: <200712082348.lB8Nm9BL020372@mail03.syd.optusnet.com.au> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 09 Dec 2007 10:48:02 +1100 To: Sam Leffler , Bob Bishop From: Tony & Heather Tregale In-Reply-To: <475ACB7C.7050004@errno.com> References: <200712080701.lB871hI0022552@mail15.syd.optusnet.com.au> <475ACB7C.7050004@errno.com> Mime-Version: 1.0 X-Antivirus: avast! (VPS 071208-0, 08/12/2007), Outbound message X-Antivirus-Status: Clean Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-mobile@freebsd.org Subject: Re: Firmware Upgrade MA311 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2007 23:49:37 -0000 OK guys, but I'm not sure what all this means in real terms....... Do I understand right that the Hardware and Firmware are fine for WPA, but one needs the right Software (?) Regards, Tony Melbourne, Australia. At 03:51 9/12/2007, Sam Leffler wrote: >Bob Bishop wrote: >>Hi, >> >>On 8 Dec 2007, at 07:01, Tony & Heather Tregale wrote: >>>Can this wireless card decode WPA - PSK, please? If so, how? >> >>I don't believe the Prism 2.5 chipset can do WPA. See `man wi' > >I believe the fw is capable of supporting WPA starting with 1.7 or >possibly an earlier rev. The problem is entirely in in the wi driver. > >Note that "decode WPA - PSK" is actually a misnomer as most all the >work ends up happening in the host--all the fw needs to do is "get >out of the way". > > Sam >