From: Dan Williams <dcbw@redhat.com>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
geoffrey.levand@am.sony.com,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: Re: [PATCH] PS3: gelic: Add wireless support for PS3
Date: Fri, 14 Dec 2007 07:58:47 -0500 [thread overview]
Message-ID: <1197637127.16724.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20071214134918.275E.MOKUNO@sm.sony.co.jp>
On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote:
> On Thu, 13 Dec 2007 16:13:38 -0500
> Dan Williams <dcbw@redhat.com> 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 those frames up unmodified so the driver would at least have a
> > _hope_ of 802.1x capability. Does the firmware handle Dynamic WEP at
> > all?
> >
> > Basically, what happens when the AP you've just associated with starts
> > sending you EAPOL traffic to start the 802.1x process?
>
> The PS3 wireless device does the association and 4way handshake in its
> firmware/hypervisor. No interventions between them are allowed to the guest
> OSes.
> All frames which are sent/received from/to before the connection process
> completed seems to be dropped by the hardware. Only the static WEP is
> supported.
That sort of sucks; but I guess there's not too much you can do about
it. That probably means that using wpa_supplicant + WPA is completely
out of the picture, which unfortunately makes the PS3 wireless unlike
any other card, which would require special-casing the PS3 in userspace
tools.
Dan
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Masakazu Mokuno <mokuno-DfbDroY8Xu1L9jVzuh4AOg@public.gmane.org>
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
geoffrey.levand-mEdOJwZ7QcZBDgjK7y7TUQ@public.gmane.org,
Geert Uytterhoeven
<Geert.Uytterhoeven-osDt5Q4Chk1BDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] PS3: gelic: Add wireless support for PS3
Date: Fri, 14 Dec 2007 07:58:47 -0500 [thread overview]
Message-ID: <1197637127.16724.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20071214134918.275E.MOKUNO-DfbDroY8Xu1L9jVzuh4AOg@public.gmane.org>
On Fri, 2007-12-14 at 14:03 +0900, Masakazu Mokuno wrote:
> On Thu, 13 Dec 2007 16:13:38 -0500
> Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 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 those frames up unmodified so the driver would at least have a
> > _hope_ of 802.1x capability. Does the firmware handle Dynamic WEP at
> > all?
> >
> > Basically, what happens when the AP you've just associated with starts
> > sending you EAPOL traffic to start the 802.1x process?
>
> The PS3 wireless device does the association and 4way handshake in its
> firmware/hypervisor. No interventions between them are allowed to the guest
> OSes.
> All frames which are sent/received from/to before the connection process
> completed seems to be dropped by the hardware. Only the static WEP is
> supported.
That sort of sucks; but I guess there's not too much you can do about
it. That probably means that using wpa_supplicant + WPA is completely
out of the picture, which unfortunately makes the PS3 wireless unlike
any other card, which would require special-casing the PS3 in userspace
tools.
Dan
next prev parent reply other threads:[~2007-12-14 13:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 12:27 [PATCH] PS3: gelic: Add wireless support for PS3 Masakazu Mokuno
2007-12-13 15:33 ` Dan Williams
2007-12-13 15:33 ` Dan Williams
2007-12-14 5:07 ` Masakazu Mokuno
2007-12-14 5:07 ` Masakazu Mokuno
2007-12-13 21:13 ` Dan Williams
2007-12-13 21:13 ` Dan Williams
2007-12-14 5:03 ` Masakazu Mokuno
2007-12-14 5:03 ` Masakazu Mokuno
2007-12-14 12:58 ` Dan Williams [this message]
2007-12-14 12:58 ` Dan Williams
2007-12-15 1:42 ` Jouni Malinen
2007-12-15 1:42 ` Jouni Malinen
2007-12-16 17:49 ` Dan Williams
2007-12-16 18:11 ` Jouni Malinen
2007-12-16 23:10 ` Dan Williams
2007-12-16 23:10 ` Dan Williams
2007-12-16 23:42 ` Jouni Malinen
2007-12-16 23:42 ` Jouni Malinen
2007-12-21 6:17 ` Masakazu Mokuno
2007-12-21 6:17 ` Masakazu Mokuno
2007-12-14 6:48 ` David Woodhouse
2007-12-14 6:48 ` David Woodhouse
2007-12-21 9:26 ` Masakazu Mokuno
2007-12-21 9:26 ` Masakazu Mokuno
2008-01-24 5:51 ` [PATCH v2] " Masakazu Mokuno
2008-01-24 5:51 ` Masakazu Mokuno
2008-01-25 1:49 ` Dan Williams
2008-01-25 2:47 ` John W. Linville
2008-01-25 2:47 ` John W. Linville
2008-01-25 3:36 ` Masakazu Mokuno
2008-01-25 3:36 ` Masakazu Mokuno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1197637127.16724.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=geoffrey.levand@am.sony.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mokuno@sm.sony.co.jp \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.