[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DB6E584.9040504@lwfinger.net>
Date: Tue, 26 Apr 2011 10:32:20 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: Jeff Chua <jeff.chua.linux@...il.com>
CC: lkml <linux-kernel@...r.kernel.org>, wlanfae@...ltek.com
Subject: Re: r8712u cannot set essid
On 04/25/2011 10:26 PM, Jeff Chua wrote:
> On Tue, Apr 26, 2011 at 8:48 AM, Larry Finger<Larry.Finger@...inger.net> wrote:
>> On 04/25/2011 07:21 PM, Jeff Chua wrote:
>>> A little bit of good news is that I got adhoc to work 2 out of 100
>>> tries (with wpa_supplicant on another sreen, and the above iwconfig
>>> command). So, it's working "partially". Once it has an SSID, I could
>>> change it and it'll still work.
>>
>> Please try the attached patch.
>
> Tried, but didn't make any difference.
>
> Now I can make adhoc work 100% if I first put the device in wpa2
> infrastructure and associates it with an AP. Then kill the
> wpa_supplicant process, and start a new wpa_supplicant with adhoc
> config.
>
> If I just start with the wpa_supplicant adhoc config, it'll never set the ssid.
>
> So, something is not right in the r8712u module or may be the firmware?
I must have something wrong in my setup, thus my testing did not work. There is
another place in the code where the setting of parameters requires the interface
to be connected. Please try the attached patch.
Larry
View attachment "r8712u_set_essid" of type "text/plain" (846 bytes)
Powered by blists - more mailing lists