Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-24 Thread hopto
still does not work. by nids normally works as a client. -- View this message in context: http://freebsd.1045724.n5.nabble.com/CFT-Ralink-RT2860-RT2870-RT3060-RT3090-support-tp5683758p5711933.html Sent from the freebsd-current mailing list archive at Nabble.com. __

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-12 Thread Bernhard Schmidt
On Sat, May 12, 2012 at 4:40 PM, hopto wrote: > on first problem: > #ifconfig ral0 inet 192.168.0.1 netmask 0xfff0 ssid freebsdap channel 11 > mediaopt hostap > ifconfig: SIOCS80211: Invalid argument > > on second problem: > If the set is not as klinet otobrazhayutsya available networks at all

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-12 Thread hopto
on first problem: #ifconfig ral0 inet 192.168.0.1 netmask 0xfff0 ssid freebsdap channel 11 mediaopt hostap ifconfig: SIOCS80211: Invalid argument on second problem: If the set is not as klinet otobrazhayutsya available networks at all. Ate configured as an access point to the kind of okay (wla

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-12 Thread Bernhard Schmidt
On Sat, May 12, 2012 at 8:44 AM, hopto wrote: > does not work DWA-525 is not as an access point, not as a client > > May 12 01:57:23 bit-box kernel: ral0: mem > 0xfe51-0xfe51 irq 16 at device 0.0 on pci6 > May 12 01:58:52 bit-box kernel: ral0: unable to receive rt2860fw firmware > image

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-12 Thread hopto
does not work DWA-525 is not as an access point, not as a client May 12 01:57:23 bit-box kernel: ral0: mem 0xfe51-0xfe51 irq 16 at device 0.0 on pci6 May 12 01:58:52 bit-box kernel: ral0: unable to receive rt2860fw firmware image May 12 01:58:52 bit-box kernel: ral0: could not load 8051 m

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-11 Thread Bernhard Schmidt
On Friday 11 May 2012 17:57:03 hopto wrote: > FreeBSD 9 amd64 > > cc1: warnings being treated as errors > /usr/src/sys/modules/ral/../../dev/ral/rt2860.c: In function > 'rt2860_attach': > /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:349: warning: assignment > from incompatible pointer type > **

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-11 Thread hopto
FreeBSD 9 amd64 cc1: warnings being treated as errors /usr/src/sys/modules/ral/../../dev/ral/rt2860.c: In function 'rt2860_attach': /usr/src/sys/modules/ral/../../dev/ral/rt2860.c:349: warning: assignment from incompatible pointer type *** Error code 1 Stop in /usr/src/sys/modules/ral. what? --

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-08 Thread Bernhard Schmidt
On Sat, May 5, 2012 at 12:51 PM, Bernhard Schmidt wrote: > Please apply attached patch (also here [1]) on top of the first one, > it fixes channel switching for >= 3070 (called the wrong function, > doh..) as well as a bgscan issue. > > [1] http://techwires.net/~bschmidt/rt2860_1.diff And another

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-06 Thread Adrian Chadd
Hi, FWIW, "device timeout" may just be watchdog related race conditions, rather than an actual hardware device timeout. I have the same issues in ath(4). I need to fix a whole lot of locking constructs before I can fix 'that'. Adrian ___ freebsd-curr

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-06 Thread Sergey V. Dyatko
On Sat, 5 May 2012 14:50:52 +0200 Bernhard Schmidt wrote: > On Sat, May 5, 2012 at 2:27 PM, Sergey V. Dyatko > wrote: > > On Sat, 5 May 2012 12:51:10 +0200 > > Bernhard Schmidt wrote: > >> Please apply attached patch (also here [1]) on top of the first > >> one, it fixes channel switching for >

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-05 Thread Bernhard Schmidt
On Sat, May 5, 2012 at 2:27 PM, Sergey V. Dyatko wrote: > On Sat, 5 May 2012 12:51:10 +0200 > Bernhard Schmidt wrote: >> Please apply attached patch (also here [1]) on top of the first one, >> it fixes channel switching for >= 3070 (called the wrong function, >> doh..) as well as a bgscan issue.

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-05 Thread Sergey V. Dyatko
On Sat, 5 May 2012 12:51:10 +0200 Bernhard Schmidt wrote: > On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote: > > On Thu, 3 May 2012 18:53:52 +0200 > > Bernhard Schmidt wrote: > > > > > Hi folks, > > > > > > As some of you might know there has been some work going on > > > porting suppo

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-05 Thread Bernhard Schmidt
On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote: > On Thu, 3 May 2012 18:53:52 +0200 > Bernhard Schmidt wrote: > > > Hi folks, > > > > As some of you might know there has been some work going on porting > > support for new Ralink chipsets from OpenBSD. Several different > > drivers where

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-05 Thread Bernhard Schmidt
On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote: > On Thu, 3 May 2012 18:53:52 +0200 > Bernhard Schmidt wrote: > > > Hi folks, > > > > As some of you might know there has been some work going on porting > > support for new Ralink chipsets from OpenBSD. Several different > > drivers where

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-05 Thread Sergey V. Dyatko
On Thu, 3 May 2012 18:53:52 +0200 Bernhard Schmidt wrote: > Hi folks, > > As some of you might know there has been some work going on porting > support for new Ralink chipsets from OpenBSD. Several different > drivers where floating around but nothing seemed to be decent enough > to be committed

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-04 Thread matt
On 05/03/12 11:18, Adrian Chadd wrote: Hi, First off, let me say "thankyou" to you, ray@ and all the people who have chipped away at this little problem. I look very forward to having rt2xxx 802.11n support, as do many users on the forums. :) I haven't yet done a pass or two to see what the sta

Re: [CFT] Ralink RT2860, RT2870, RT3060, RT3090 support

2012-05-03 Thread Adrian Chadd
Hi, First off, let me say "thankyou" to you, ray@ and all the people who have chipped away at this little problem. I look very forward to having rt2xxx 802.11n support, as do many users on the forums. :) I haven't yet done a pass or two to see what the state of the locking/concurrency handling is