Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-21 Thread Masakazu Mokuno
Hi David, On Fri, 14 Dec 2007 01:48:52 -0500 David Woodhouse <[EMAIL PROTECTED]> wrote: > --- linux-2.6.23.ppc64/drivers/net/ps3_gelic_net.c~ 2007-12-14 > 01:31:50.0 -0500 > +++ linux-2.6.23.ppc64/drivers/net/ps3_gelic_net.c2007-12-14 > 01:39:25.0 -0500 > @@ -1139,

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-20 Thread Masakazu Mokuno
Hi Jouni, On Fri, 14 Dec 2007 17:42:44 -0800 Jouni Malinen <[EMAIL PROTECTED]> wrote: > However, there is a part that you are not going to like.. This is likely > using a private ioctl for some parts of the association requests, i.e., > no -Dwext.. I would assume that this could be cleane

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-16 Thread Jouni Malinen
On Sun, Dec 16, 2007 at 06:10:10PM -0500, Dan Williams wrote: > On Sun, 2007-12-16 at 10:11 -0800, Jouni Malinen wrote: > > It is a new key type regardless of whether it is PSK or passphrase. The > > current key types (IW_AUTH_CIPHER_*) are WEP40, TKIP, CCMP, and WEP104.. > Ah, it's a different ke

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-16 Thread Dan Williams
On Sun, 2007-12-16 at 10:11 -0800, Jouni Malinen wrote: > On Sun, Dec 16, 2007 at 12:49:14PM -0500, Dan Williams wrote: > > > Yeah, I was going to propose that on Friday but got side-tracked. What > > would require a new key type? Are there some firmwares that _only_ > > accept the WPA passphras

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-16 Thread Jouni Malinen
On Sun, Dec 16, 2007 at 12:49:14PM -0500, Dan Williams wrote: > Yeah, I was going to propose that on Friday but got side-tracked. What > would require a new key type? Are there some firmwares that _only_ > accept the WPA passphrase? Because if there aren't (PS3 accepts WPA hex > keys too) then

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-16 Thread Dan Williams
On Fri, 2007-12-14 at 17:42 -0800, Jouni Malinen wrote: > On Fri, Dec 14, 2007 at 07:58:47AM -0500, Dan Williams wrote: > > On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote: > > > The PS3 wireless device does the association and 4way handshake in its > > > firmware/hypervisor. No intervent

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-14 Thread Jouni Malinen
On Fri, Dec 14, 2007 at 07:58:47AM -0500, Dan Williams wrote: > On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote: > > The PS3 wireless device does the association and 4way handshake in its > > firmware/hypervisor. No interventions between them are allowed to the guest > > OSes. > That s

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-14 Thread Dan Williams
On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote: > On Thu, 13 Dec 2007 16:13:38 -0500 > Dan Williams <[EMAIL PROTECTED]> wrote: > > > One more question; does the driver work with wpa_supplicant for WPA, or > > does the firmware capture the EAPOL frames and handle the 4 way > > handshake i

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-13 Thread David Woodhouse
--- linux-2.6.23.ppc64/drivers/net/ps3_gelic_net.c~ 2007-12-14 01:31:50.0 -0500 +++ linux-2.6.23.ppc64/drivers/net/ps3_gelic_net.c 2007-12-14 01:39:25.0 -0500 @@ -1139,7 +1139,7 @@ static irqreturn_t gelic_card_interrupt( * * see Documentation/networking/netconsole.tx

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-13 Thread Masakazu Mokuno
On Thu, 13 Dec 2007 10:33:22 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: > You'll need to emit more NULL IWAP events on association failure. For > example, gelic_wl_assoc_worker() should probably send one right before > both instances of 'goto scan_lock_out' in that function (the first where >

Re: [PATCH] PS3: gelic: Add wireless support for PS3

2007-12-13 Thread Masakazu Mokuno
On Thu, 13 Dec 2007 16:13:38 -0500 Dan Williams <[EMAIL PROTECTED]> wrote: > One more question; does the driver work with wpa_supplicant for WPA, or > does the firmware capture the EAPOL frames and handle the 4 way > handshake internally? Ideally the firmware would have the ability to > pass tho