* Re: any controller working in AP mode ?
From: Pavel Roskin @ 2009-07-22 15:48 UTC (permalink / raw)
To: Ram kumar; +Cc: Javier Cardona, andrey, linux-wireless
In-Reply-To: <1247843954.25608.62.camel@mj>
On Fri, 2009-07-17 at 11:19 -0400, Pavel Roskin wrote:
> > It would be very helpful if anyone can guide me,how to get the
> > hardware for MARVELL 8388.
>
> 5 minute search finds that Zonet ZEW2502 is what you need. There is
> only one driver for that device on the Zonet site, and it's clearly for
> Marvell.
Just for the record, it turns out the device is not supported, even
though it's Marvell:
Bus 001 Device 005: ID 1286:1fab Marvell Semiconductor, Inc.
Both libertas drivers support only 1286:2001 and 05a3:8388.
Web search for 1286:1fab doesn't find anything useful other than
recommendations to use ndiswrapper.
I should have checked the ID in the *.inf files against the kernel
sources.
--
Regards,
Pavel Roskin
^ permalink raw reply
* Re: [PATCH] ath9k: Add init values for AR9287 based chipsets.
From: John W. Linville @ 2009-07-22 15:22 UTC (permalink / raw)
To: Vivek Natarajan; +Cc: linux-wireless
In-Reply-To: <20090715031731.GC4613@myhost>
On Wed, Jul 15, 2009 at 08:47:31AM +0530, Vivek Natarajan wrote:
> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
> ---
> drivers/net/wireless/ath/ath9k/initvals.h | 1544 +++++++++++++++++++++++++++++
> 1 files changed, 1544 insertions(+), 0 deletions(-)
This didn't apply after all the rebased patches from Luis. It looked
deceptively simple to move it, but my "Spidey sense" told me I should
ask you to rebase and resend. "ath9k: Add support for AR9287 based
chipsets." didn't apply without this, so could you rebase/resend that
one as well?
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Re: wireless-testing regression: iwl3945 scan fails
From: Kalle Valo @ 2009-07-22 14:44 UTC (permalink / raw)
To: linux-wireless; +Cc: reinette.chatre, Johannes Berg
In-Reply-To: <87k521s2wa.fsf@litku.valot.fi>
Kalle Valo <kalle.valo@iki.fi> writes:
> Good morning,
>
> I just upgraded to rc3-wl (commit 225b6807) and my iwl3945 doesn't work
> anymore, even scan fails. I don't have time to investigate this right
> now, but I'll try to find some time during the evening.
I have looked at this now a bit and I don't think this is an iwl3945
problem. Scanning seems to stall in some situations and iwl3945 doesn't
even receive the scan command.
Here's an example what's happening with wpa_supplicant from debian
unstable:
$ sudo ifup wlan0
[ 104.468073] iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
[ 104.533234] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
[ 104.612049] phy0: device now idle
[ 104.613091] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 106.968392] phy0: device no longer idle - scanning
[ 109.561397] phy0: device now idle
[ 109.563737] wlan0: deauthenticating by local choice (reason=3)
[ 109.563743] phy0: device no longer idle - in use
[waited a while]
$ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Device or resource busy
$ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Device or resource busy
$ sudo wpa_action wlan0 stop
[ 191.649653] wlan0: deauthenticating by local choice (reason=3)
[ 191.697619] phy0: device now idle
Also I have been able to reproduce the problem once with iw. For some
strange reason I have had to reboot my laptop to reproduce this,
unloading all wireless related modules (expect rfkill which I can't
unload due to dependencies) is not enough.
--
Kalle Valo
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: John W. Linville @ 2009-07-22 14:24 UTC (permalink / raw)
To: Kamil Dzida; +Cc: linux-wireless
In-Reply-To: <loom.20090722T140518-0@post.gmane.org>
On Wed, Jul 22, 2009 at 02:15:15PM +0000, Kamil Dzida wrote:
> John W. Linville <linville@...> writes:
>
> >
> > On Wed, Jul 22, 2009 at 08:00:28AM +0000, Kamil Dzida wrote:
> >
> > > It seems that OpenBSD has driver for AR5523 (AR5005UG and AR5005UX) upstream.
> > > I doubt that they would like to share their code with Linux -
> like dual licensing
> > > GPL/BSD.
> >
> > At the risk of starting another flame war with insane people, I'll
> > point-out that dual licensing is not necessary. The BSD licensed
> > code is completely available to us.
> >
> > John
>
>
> I am not here to start a flame war of any sort,
> yet if it sounded like that then I am terribly sorry.
> I came here to aid with a link to man page which includes a good list of
> AR5005UG and AR5005UX based hardware which could be useful for the
> developers.
>
> Anyway thank you for the clarification.
Whether or not you are insane remains to be seen. :-) Nevertheless,
you were _not_ the "insane people" I was alluding to above...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Kamil Dzida @ 2009-07-22 14:15 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <20090722123727.GB3927@tuxdriver.com>
John W. Linville <linville@...> writes:
>
> On Wed, Jul 22, 2009 at 08:00:28AM +0000, Kamil Dzida wrote:
>
> > It seems that OpenBSD has driver for AR5523 (AR5005UG and AR5005UX) upstream.
> > I doubt that they would like to share their code with Linux -
like dual licensing
> > GPL/BSD.
>
> At the risk of starting another flame war with insane people, I'll
> point-out that dual licensing is not necessary. The BSD licensed
> code is completely available to us.
>
> John
I am not here to start a flame war of any sort,
yet if it sounded like that then I am terribly sorry.
I came here to aid with a link to man page which includes a good list of
AR5005UG and AR5005UX based hardware which could be useful for the
developers.
Anyway thank you for the clarification.
Kamil Dzida
^ permalink raw reply
* Re: Update for regulatory database on 5GHz band for Thailand (TH)
From: Phattanon Duangdara @ 2009-07-22 14:04 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <20090722131957.GA5276@tuxdriver.com>
On Wed, Jul 22, 2009 at 8:19 PM, John W. Linville<linville@tuxdriver.com> wrote:
> On Wed, Jul 22, 2009 at 08:07:21PM +0700, Phattanon Duangdara wrote:
>> National Telecommunication Commisions of Thailand has announce new
>> regulatory about 5GHz for RLAN last year.
>>
>> But I found that Linux Wireless Regulatory Database not get updated.
>>
>> Reference in Thai Language:
>> http://www.ratchakitcha.soc.go.th/DATA/PDF/2551/E/042/64.PDF
>> (Partly in english and reference to ITU/FCC documents, I think it
>> quite easy to understand)
>>
>> How can this get update on Regulatory Database ?
>
> What a beautiful font! :-)
>
> While there is enough English/numbers there that I can probably judge
> what it means, I'd feel a lot better if someone else (perhaps you)
> submitted a patch against the tree here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
>
> Thanks!
>
> John
> --
> John W. Linville Someday the world will need a hero, and you
> linville@tuxdriver.com might be all we have. Be ready.
> –iva Honduras Libre!
>
Actually, NTC provide english translated documents, but for thism, it
missing from their website. I already contact NTC to get those
document in english for reference and clarification. Later models of
some Laptops sell in Thailand already has 5GHz enabled radio.
For now I will try to update db against tree from my knowledge.
Phattanon
^ permalink raw reply
* Re: Update for regulatory database on 5GHz band for Thailand (TH)
From: Holger Schurig @ 2009-07-22 13:33 UTC (permalink / raw)
To: Phattanon Duangdara; +Cc: linux-wireless
In-Reply-To: <f7de31c0907220607v3266710co5640389fc0ccbc22@mail.gmail.com>
> Reference in Thai Language:
> http://www.ratchakitcha.soc.go.th/DATA/PDF/2551/E/042/64.PDF
> (Partly in english and reference to ITU/FCC documents, I think
> it quite easy to understand)
While I find your writing aesthetically pleasing, I'd not dare to
extract regulatory data out of a document where I can only read
here and there something. I'm not sure if others are more brave
than me :-)
Could you describe what exactly changed?
--
M&N Solutions GmbH Ein Unternehmen der Datagroup AG
Holger Schurig
Raiffeisenstr. 10
61191 Rosbach
Tel: 06003/9141-15 Fax 06003/9141-49
http://www.mn-solutions.de/
Handelsregister Friedberg, HRB 5903
Geschäftsführer: P.Schrittenlocher
^ permalink raw reply
* Re: Update for regulatory database on 5GHz band for Thailand (TH)
From: John W. Linville @ 2009-07-22 13:19 UTC (permalink / raw)
To: Phattanon Duangdara; +Cc: linux-wireless
In-Reply-To: <f7de31c0907220607v3266710co5640389fc0ccbc22@mail.gmail.com>
On Wed, Jul 22, 2009 at 08:07:21PM +0700, Phattanon Duangdara wrote:
> National Telecommunication Commisions of Thailand has announce new
> regulatory about 5GHz for RLAN last year.
>
> But I found that Linux Wireless Regulatory Database not get updated.
>
> Reference in Thai Language:
> http://www.ratchakitcha.soc.go.th/DATA/PDF/2551/E/042/64.PDF
> (Partly in english and reference to ITU/FCC documents, I think it
> quite easy to understand)
>
> How can this get update on Regulatory Database ?
What a beautiful font! :-)
While there is enough English/numbers there that I can probably judge
what it means, I'd feel a lot better if someone else (perhaps you)
submitted a patch against the tree here:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Update for regulatory database on 5GHz band for Thailand (TH)
From: Phattanon Duangdara @ 2009-07-22 13:07 UTC (permalink / raw)
To: linux-wireless
National Telecommunication Commisions of Thailand has announce new
regulatory about 5GHz for RLAN last year.
But I found that Linux Wireless Regulatory Database not get updated.
Reference in Thai Language:
http://www.ratchakitcha.soc.go.th/DATA/PDF/2551/E/042/64.PDF
(Partly in english and reference to ITU/FCC documents, I think it
quite easy to understand)
How can this get update on Regulatory Database ?
^ permalink raw reply
* Re: wireless-testing regression: iwl3945 scan fails
From: John W. Linville @ 2009-07-22 12:34 UTC (permalink / raw)
To: Kalle Valo; +Cc: linux-wireless, reinette.chatre
In-Reply-To: <87k521s2wa.fsf@litku.valot.fi>
On Wed, Jul 22, 2009 at 08:27:49AM +0300, Kalle Valo wrote:
> I just upgraded to rc3-wl (commit 225b6807) and my iwl3945 doesn't work
> anymore, even scan fails. I don't have time to investigate this right
> now, but I'll try to find some time during the evening.
Marcel had similar complaints yesterday evening. I dunno which device
he has. FWIW, the iwl5300 I have here seems to be working fine.
Maybe the Intel folks have some insight? There was a big batch of
patches from them in yesterday's update.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: John W. Linville @ 2009-07-22 12:38 UTC (permalink / raw)
To: Kamil Dzida; +Cc: linux-wireless
In-Reply-To: <loom.20090722T115236-65@post.gmane.org>
On Wed, Jul 22, 2009 at 12:12:07PM +0000, Kamil Dzida wrote:
> I hope that it is O.K. to have ISC licensed driver in GPL licensed kernel.
It is.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: John W. Linville @ 2009-07-22 12:37 UTC (permalink / raw)
To: Kamil Dzida; +Cc: linux-wireless
In-Reply-To: <loom.20090722T074629-659@post.gmane.org>
On Wed, Jul 22, 2009 at 08:00:28AM +0000, Kamil Dzida wrote:
> It seems that OpenBSD has driver for AR5523 (AR5005UG and AR5005UX) upstream. I
> doubt that they would like to share their code with Linux - like dual licensing
> GPL/BSD.
At the risk of starting another flame war with insane people, I'll
point-out that dual licensing is not necessary. The BSD licensed
code is completely available to us.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Kamil Dzida @ 2009-07-22 12:12 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <3ace41890907220348i367a2b02had02f05af3ab3d4f@mail.gmail.com>
Hin-Tak Leung <hintak.leung@...> writes:
> I like to see the spec, even though I don't have a device (yet).
>
> Hin-Tak
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
If you are asking me then sorry but I am not connected in any way with OpenBSD
and I do not have any hardware specifications :(
You should ask Atheros through Luis and also Damien Bergamini of OpenBSD.
Anyway I just realized that the partial Linux driver is actually a port of
OpenBSD driver with firmware extracted from Windows driver!
I hope that it is O.K. to have ISC licensed driver in GPL licensed kernel.
Kamil
^ permalink raw reply
* Re: lockdep complaint on tip + some pending patches
From: Johannes Berg @ 2009-07-22 10:52 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
In-Reply-To: <43e72e890907211750s69420e47ma98b4c3214dfd1f1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]
On Tue, 2009-07-21 at 17:50 -0700, Luis R. Rodriguez wrote:
> While running on wireless-testing + netns pending patches + wow patches:
>
> wpa_supplicant -D wext -i wlan1 -c mosca.conf
>
> [ 233.096916] phy0: device now idle
> [ 233.114625] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 234.116189] phy0: device no longer idle - scanning
> [ 234.233767]
> [ 234.233772] =======================================================
> [ 234.233797] [ INFO: possible circular locking dependency detected ]
> [ 234.233807] 2.6.31-rc3-wl #16
> [ 234.233814] -------------------------------------------------------
> [ 234.233824] wpa_supplicant/3089 is trying to acquire lock:
> [ 234.233835] (cfg80211_mutex){+.+.+.}, at: [<f83eb185>]
> cfg80211_get_dev_from_ifindex+0x15/0x80 [cfg80211]
> [ 234.233887]
> [ 234.233889] but task is already holding lock:
> [ 234.233901] (rtnl_mutex){+.+.+.}, at: [<c049de2f>] rtnl_lock+0xf/0x20
> [ 234.233932]
> [ 234.233934] which lock already depends on the new lock.
> [ 234.233936]
> [ 234.233957]
> [ 234.233958] the existing dependency chain (in reverse order) is:
> [ 234.233970]
> [ 234.233972] -> #1 (rtnl_mutex){+.+.+.}:
> [ 234.233996] [<c0169b35>] __lock_acquire+0xba5/0x1020
> [ 234.234014] [<c016a06b>] lock_acquire+0xbb/0xe0
> [ 234.234029] [<c05838f4>] mutex_lock_nested+0x54/0x300
> [ 234.234045] [<c049de2f>] rtnl_lock+0xf/0x20
> [ 234.234061] [<f83f734a>] nl80211_send_reg_change_event+0x1aa/0x250 [cfg80211]
I think you're using the wrong genetlink netns patch.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Hin-Tak Leung @ 2009-07-22 10:48 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <loom.20090722T074629-659@post.gmane.org>
On Wed, Jul 22, 2009 at 9:00 AM, Kamil Dzida<kamil.dzida@gmail.com> wrote:
> Pat Erley <pat-lkml@...> writes:
>
>>
>> Luis R. Rodriguez wrote:
>> > On Tue, Jul 21, 2009 at 6:03 PM, Purushotham
>> > Nayak<nayak_purushotham@...> wrote:
>> >> Hi,
>> >>
>> >> I'm interested in working on this. I just posted to the Linux driver
> project a few days ago if I could work on
>> the atheros USB devices. Please let me also know the USB device that uses the
> AR5523.
>> >
>> > Dan recently purchased one of these devices. Dan any pointers?
>>
>> I have a few WPN111 Refurbed devices that are AR5523 based. Apparently
>> there is a WPN111v2 that may or may not be otus supported, I can't confirm
>> that. Based on pictures from google and the devices I own, the AR5523 ones
>> are silver, and the Otus ones are white. I'd be more than happy to test and
>> do what I can to try to help, but my time is limited, so I'm not up for
>> taking the task onto my shoulders right now.
>>
>> Pat
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@...
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>
> It seems that OpenBSD has driver for AR5523 (AR5005UG and AR5005UX) upstream. I
> doubt that they would like to share their code with Linux - like dual licensing
> GPL/BSD. Fortunately their documentation mentions which hardware includes those
> chipsets, look here:
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=uath&sektion=4&apropos=0&manpath=OpenBSD+Current&arch=i386
>
>
> Note that Atheros AR5007UG (alternatively known as AR2524/AR5524) is supported
> by Linux zd1211rw driver.
>
> Kamil
I like to see the spec, even though I don't have a device (yet).
Hin-Tak
^ permalink raw reply
* Re: Slow roaming in mac80211 (2.6.30).
From: Holger Schurig @ 2009-07-22 8:55 UTC (permalink / raw)
To: Lars Ericsson; +Cc: 'Johannes Berg', linux-wireless, hostap
In-Reply-To: <1B3FCF72EBBC44A39F5A80B8FFBF6402@gotws1589>
> For .26 I have made a few patches to fix minor issues related
> to roaming.
It might be worthwile for you to publish this code, even it it's
for an ancient kernel. You can post that to the mailing list and
mark them as "RFC" instead of "PATCH" in the subject line.
Some people are currently working on roaming support, e.g.
Helmut. Your patches/findings might give some input or ideas.
^ permalink raw reply
* Re: Slow roaming in mac80211 (2.6.30).
From: Lam Yoke Khei @ 2009-07-22 8:18 UTC (permalink / raw)
To: Lars Ericsson; +Cc: linux-wireless, hostap
In-Reply-To: <1B3FCF72EBBC44A39F5A80B8FFBF6402@gotws1589>
Hi Lars,
Would you mind to share your idea or patches on 2.6.26 kernel to improve
roaming? As I am investigating the solution for short handoff/reassociation
time (~50ms) via linux wireless stack. Thanks in advance.
Best regards,
Lam
----- Original Message -----
From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>; <hostap@shmoo.com>
Sent: Wednesday, July 22, 2009 5:21 AM
Subject: Slow roaming in mac80211 (2.6.30).
>
> Johannes,
>
> I'm currently using the 2.6.26 kernel and have started evaluating the
> 2.6.30.
>
> For .26 I have made a few patches to fix minor issues related to
> roaming.
>
> The trace below shows a typical roaming:
> 87.632965 AP 1 drops STA
> 87.733979 wpa_supplicant trigs a scan
> 88.629931 mac80211 probes for the old AP
> 90.670305 SCAN result to wpa_supplicant
> 90.702325 wpa_supplicant ready with new AP
> 92.158037 mac80211 executes the wpa_supplicant decisions
> 92.164776 we are on line again
>
> Total roaming time is 4,5 seconds, where mac80211 had added 2*2
> seconds delay.
>
> A first analysis gives that the two delays are the ieee80211_sta_work()
> timeout. There are many events trigging ieee80211_sta_work(), but
> since only the timer sets IEEE80211_STA_REQ_RUN, nothing will happen.
>
> Questions;
> - Why does mac80211 tells the wpa_supplicant that the AP
> is gone (87.632965), and then blocks/delays the actions taken by the
> wpa_supplicant?
> - Why are some wpa_supplicant actions (90.702325)
> not event driven?
>
> It looks to me as if we have to decision makers here. For me the
> wpa_supplicant is the one that make the decision. Once the mac80211
> gives up and feedback that the AP is gone, it should just sit
> and wait for next decision from the wpa_supplicant.
>
> I had a few patches for this for .26, but since the code is changed
> they do not apply. Before I create new patches I would like to get
> your opinion on this.
>
> Regards
> /Lars
>
> -----
> [ 87.632965] wlan0: deauthenticated (Reason: 1)
> [ 87.733979] [B] LaE: SCANRQUEST: SSID=AGV
> [ 88.629931] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 1
> [ 88.829932] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 2
> [ 89.029944] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 3
> [ 89.230016] wlan0: direct probe to AP 00:40:96:a0:e7:e7 timed out
> [ 90.670305] [B] LaE: SCANRESULT: BSSID=00:40:96:a0:e7:e7, SSID=
> , ch= 1, , q= 0, l= 0(-30dBm), n= 0
> [ 90.670384] [B] LaE: SCANRESULT: BSSID=00:08:21:31:53:87, SSID=
> , ch=11, , q= 0, l= 0(-62dBm), n= 0
> [ 90.670455] [B] LaE: SCANRESULT: BSSID=00:08:21:31:53:87, SSID=AGV
> , ch=11, , q= 0, l= 0(-60dBm), n= 0
> [ 90.670705] ieee80211_ioctl_siwauth: enter
> [ 90.670777] ieee80211_ioctl_siwencodeext: enter
> [ 90.670807] ieee80211_set_encryption: enter
> [ 90.671128] ieee80211_ioctl_siwencodeext: enter
> [ 90.671165] ieee80211_set_encryption: enter
> [ 90.671219] ieee80211_ioctl_siwencodeext: enter
> [ 90.671247] ieee80211_set_encryption: enter
> [ 90.671297] ieee80211_ioctl_siwencodeext: enter
> [ 90.671325] ieee80211_set_encryption: enter
> [ 90.671375] ieee80211_ioctl_siwencodeext: enter
> [ 90.671404] ieee80211_set_encryption: enter
> [ 90.671623] ieee80211_ioctl_siwencodeext: enter
> [ 90.671659] ieee80211_set_encryption: enter
> [ 90.672062] ieee80211_ioctl_siwauth: enter
> [ 90.672295] ieee80211_ioctl_siwgenie: enter
> [ 90.672332] ieee80211_sta_req_auth: queue auth
> [ 90.672380] ieee80211_ioctl_siwauth: enter
> [ 90.672420] ieee80211_ioctl_siwauth: enter
> [ 90.672458] ieee80211_ioctl_siwauth: enter
> [ 90.672495] ieee80211_ioctl_siwauth: enter
> [ 90.672532] ieee80211_ioctl_siwauth: enter
> [ 90.672569] ieee80211_ioctl_siwauth: enter
> [ 90.672612] ieee80211_ioctl_siwfreq: enter freq=246200000
> [ 90.702175] ieee80211_ioctl_siwessid: enter ssid=AGV
> [ 90.702217] ieee80211_sta_req_auth: queue auth
> [ 90.702325] ieee80211_ioctl_siwap: enter AP=00:08:21:31:53:87
> [ 90.702372] ieee80211_sta_req_auth: queue auth
> [ 92.158037] wlan0: authenticate with AP 00:08:21:31:53:87
> [ 92.159965] wlan0: authenticated
> [ 92.160002] wlan0: associate with AP 00:08:21:31:53:87
> [ 92.164733] wlan0: RX ReassocResp from 00:08:21:31:53:87 (capab=0x431
> status=0 aid=140)
> [ 92.164776] wlan0: associated
> [ 92.166984] ieee80211_ioctl_giwap: enter
>
> -----
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Kamil Dzida @ 2009-07-22 8:00 UTC (permalink / raw)
To: linux-wireless
In-Reply-To: <4A66A482.6050401@erley.org>
Pat Erley <pat-lkml@...> writes:
>
> Luis R. Rodriguez wrote:
> > On Tue, Jul 21, 2009 at 6:03 PM, Purushotham
> > Nayak<nayak_purushotham@...> wrote:
> >> Hi,
> >>
> >> I'm interested in working on this. I just posted to the Linux driver
project a few days ago if I could work on
> the atheros USB devices. Please let me also know the USB device that uses the
AR5523.
> >
> > Dan recently purchased one of these devices. Dan any pointers?
>
> I have a few WPN111 Refurbed devices that are AR5523 based. Apparently
> there is a WPN111v2 that may or may not be otus supported, I can't confirm
> that. Based on pictures from google and the devices I own, the AR5523 ones
> are silver, and the Otus ones are white. I'd be more than happy to test and
> do what I can to try to help, but my time is limited, so I'm not up for
> taking the task onto my shoulders right now.
>
> Pat
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@...
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
It seems that OpenBSD has driver for AR5523 (AR5005UG and AR5005UX) upstream. I
doubt that they would like to share their code with Linux - like dual licensing
GPL/BSD. Fortunately their documentation mentions which hardware includes those
chipsets, look here:
http://www.openbsd.org/cgi-bin/man.cgi?query=uath&sektion=4&apropos=0&manpath=OpenBSD+Current&arch=i386
Note that Atheros AR5007UG (alternatively known as AR2524/AR5524) is supported
by Linux zd1211rw driver.
Kamil
^ permalink raw reply
* rt2x00 : big-endianess broken for rt73usb (master mode) for e.g. xscale and powerpc
From: Gert Boddaert @ 2009-07-22 7:34 UTC (permalink / raw)
To: linux-wireless
I was able to do some testing on the rt73usb driver.
As mentioned in an earlier post, the latest driver breaks the master mode.
Although a linux client (x86 laptop) can connect to the rt73usb AP,
a windows XP client (x86 laptop) cannot.
I fails to obtain a DHCP address.
In order to reproduce the bug, you need a big-endian system with a rt73usb
stick, and hostapd.
I did not test client mode for big-endian systems.
Breaking down the different patches that were applied since 8 april 2009, I was
able to identify the culprit.
No solution yet, but I thought I should flag this
as a bug.
It is the following patch that breaks big-endian compatibility:
***
Some hardware require L2 padding between header and payload
because both must be aligned to a 4-byte boundary. This hardware
also is easier during the RX path since we no longer need to
move the entire payload but rather only the header to remove
the padding (mac80211 only wants the payload to be 4-byte aligned).
Signed-off-by: Ivo van Doorn <IvDoorn@...>
---
drivers/net/wireless/rt2x00/rt2x00.h | 10 ++++
drivers/net/wireless/rt2x00/rt2x00crypto.c | 68 +++++++++++++++++-----------
drivers/net/wireless/rt2x00/rt2x00dev.c | 33 +++++++------
drivers/net/wireless/rt2x00/rt2x00lib.h | 27 +++++++++--
drivers/net/wireless/rt2x00/rt2x00queue.c | 39 ++++++++++++++++
drivers/net/wireless/rt2x00/rt2x00queue.h | 14 +++++-
6 files changed, 143 insertions(+), 48 deletions(-)
(...)
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Pat Erley @ 2009-07-22 5:32 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: Purushotham Nayak, Christoph Hellwig, linux-wireless,
Dan Williams
In-Reply-To: <43e72e890907211804i1e1fa166y810caa95563bc695@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Tue, Jul 21, 2009 at 6:03 PM, Purushotham
> Nayak<nayak_purushotham@yahoo.com> wrote:
>> Hi,
>>
>> I'm interested in working on this. I just posted to the Linux driver project a few days ago if I could work on the atheros USB devices. Please let me also know the USB device that uses the AR5523.
>
> Dan recently purchased one of these devices. Dan any pointers?
I have a few WPN111 Refurbed devices that are AR5523 based. Apparently
there is a WPN111v2 that may or may not be otus supported, I can't confirm
that. Based on pictures from google and the devices I own, the AR5523 ones
are silver, and the Otus ones are white. I'd be more than happy to test and
do what I can to try to help, but my time is limited, so I'm not up for
taking the task onto my shoulders right now.
Pat
^ permalink raw reply
* wireless-testing regression: iwl3945 scan fails
From: Kalle Valo @ 2009-07-22 5:27 UTC (permalink / raw)
To: linux-wireless; +Cc: reinette.chatre
Good morning,
I just upgraded to rc3-wl (commit 225b6807) and my iwl3945 doesn't work
anymore, even scan fails. I don't have time to investigate this right
now, but I'll try to find some time during the evening.
--
Kalle Valo
^ permalink raw reply
* Re: Using compat-wireless w/ 2.6.27.26
From: Bob Copeland @ 2009-07-22 3:28 UTC (permalink / raw)
To: Philip A. Prindeville; +Cc: Luis R. Rodriguez, linux-wireless
In-Reply-To: <4A6620B9.4@redfish-solutions.com>
On Tue, Jul 21, 2009 at 01:10:33PM -0700, Philip A. Prindeville wrote:
> A little progress: I build 2009-07-10 with 2.6.27.26, and I can get the
> Vista box to associate, but not an iPhone running 3.0...
Yeah there's a bug, I can replicate it and am trying to track it
down right now.
--
Bob Copeland %% www.bobcopeland.com
^ permalink raw reply
* WoW patches - if anyone is up for following up with them
From: Luis R. Rodriguez @ 2009-07-22 1:49 UTC (permalink / raw)
To: linux-wireless; +Cc: ath9k-devel
I won't have time to finish testing this series and getting it merged
as I need to focus on another driver, I ran into some last issues
where I was seeing the nullfunc frames only be issued if I send a WOL
packet first, not sure what's up with that. Some other issues are the
ath9k: timeout (100000 us) on reg 0x806c: 0xdeadbeef & 0x01f00000 != 0x00000000
ath9k: RX failed to go idle in 10 ms RXSM=0xdeadbeef
after resume (not sure if this was caused by the WoW patches or what)
and the mac80211 WARN on the workqueue running local->suspended is
already true.
I probably won't get to these for a long long while (until I need WoW
for another driver), so in case someone is interesting in this, please
feel free to take them on and work on them.
You'll need two things:
* wireless-testing patches:
http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/wow-07-21.patch
This has johannes's netns patches since his nl80211 cmd is going in
first and then the WoW patches. I've stuffed some documentation on the
patch file itself to help anyone wishing to push that further,
including examples on how to get the pattern stuff initially done.
* http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/iw-add-wow.patch
You'll need this to enable WoW. Keep in mind based on feedback you
*need* to be associated to an AP to enable WoW.
Luis
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Purushotham Nayak @ 2009-07-22 1:03 UTC (permalink / raw)
To: Luis R. Rodriguez, Christoph Hellwig, linux-wireless; +Cc: Dan Williams
In-Reply-To: <43e72e890907211703y72ffe8cdv88ba9e3c59d1b76@mail.gmail.com>
Hi,
I'm interested in working on this. I just posted to the Linux driver project a few days ago if I could work on the atheros USB devices. Please let me also know the USB device that uses the AR5523.
Thanks,
Purush
----- Original Message ----
From: Luis R. Rodriguez <mcgrof@gmail.com>
To: Christoph Hellwig <hch@lst.de>; linux-wireless <linux-wireless@vger.kernel.org>; linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org; Dan Williams <dcbw@redhat.com>; ath5k-devel@lists.ath5k.org; madwifi-devel <madwifi-devel@lists.sourceforge.net>; Jouni Malinen <j@w1.fi>; ath9k-devel@lists.ath9k.org
Sent: Tuesday, July 21, 2009 8:03:36 PM
Subject: Re: AR5523 driver - old Atheros USB
On Tue, Jul 21, 2009 at 2:42 PM, Christoph Hellwig<hch@lst.de> wrote:
> On Tue, Jul 21, 2009 at 02:24:36PM -0700, Luis R. Rodriguez wrote:
>> >> Hey Chris, was curious if you still had lying around the driver you
>> >> had worked on for the old Atheros 802.11 USB device. Dan asked about
>> >> it, seems he bought one. We at least now have specs for it and can
>> >> provide them to interested developers. Since Dan brought this device
>> >> up figured I'd check to see if you still had it to see if you still
>> >> had the code and might be willing to let someone try to give a shot at
>> >> finishing it up for inclusion. Perhaps staging?
>> >
>> > The code has been at http://verein.lst.de/~hch/ar5523.tgz.
>>
>> Sweet. How functional is this? Does it TX/RX?
>
> It's been quite some time. IIRC it does TX, but can't actually see
> any packets on RX (filter issue or something).
Sorry for the large cross post, just seeing if someone is interested
in working on a wireless driver. The task would be to try to get
AR5523 USB driver up to speed with mac80211 from wireless-testing and
giving it a shot to fix remaining issues?
It seems to have compiled last for 2.6.23.
If you're interested please remove all lists and only leave
linux-wireless on the reply.
Luis
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
^ permalink raw reply
* Re: AR5523 driver - old Atheros USB
From: Luis R. Rodriguez @ 2009-07-22 1:04 UTC (permalink / raw)
To: Purushotham Nayak; +Cc: Christoph Hellwig, linux-wireless, Dan Williams
In-Reply-To: <928354.18240.qm@web56107.mail.re3.yahoo.com>
On Tue, Jul 21, 2009 at 6:03 PM, Purushotham
Nayak<nayak_purushotham@yahoo.com> wrote:
>
> Hi,
>
> I'm interested in working on this. I just posted to the Linux driver project a few days ago if I could work on the atheros USB devices. Please let me also know the USB device that uses the AR5523.
Dan recently purchased one of these devices. Dan any pointers?
Luis
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox