Re: run(4) firmware update; please test

2014-05-17 Thread Stefan Sperling
On Fri, May 16, 2014 at 02:38:49PM +, Alexey Suslikov wrote:
 Please take a look at my (unfinished) attempt to bring
 MediaTek/Ralink RT5370/RT5372 support to run(4).
 
 http://marc.info/?l=openbsd-techm=138903287819764w=2

I did take a look at this some time ago. After looking at FreeBSD's
run driver, it became apparent that they've done so much work they've
effectively become the new run(4) upstream. Instead of using your
diff as a base I deviced to go over the entire diff between OpenBSD's
and FreeBSD's run drivers and pluck all changes related to new hardware
support. The result effectively includes your diff and much more.

FreeBSD have done even more (IBSS and hostap support are particularly
interesting), so there's still more work to do if you'd like to help.

I've got run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R)
working now (by switching to the correct firmware image ;), and will
send my diff soon.



Re: run(4) firmware update; please test

2014-05-17 Thread Matthieu Herrb
On Sat, May 17, 2014 at 02:15:46PM +0200, Stefan Sperling wrote:
 On Fri, May 16, 2014 at 01:30:58PM +0200, Gerhard Roth wrote:
  He's using a model that requires a firmware-blob different from the one
  of all other testers (run-rt2870 vs. run-rt3071). That might explain,
  why he's the only one who got troubles with the new FW.
  
 Yes, and I just realized that in my previous diff, I accidentally
 used the rt2870 image as rt3071 image.
 
 $ md5 obj/run-rt*
 MD5 (obj/run-rt2870) = 039127f8c1acf7978a410ffcf563
 MD5 (obj/run-rt3071) = 039127f8c1acf7978a410ffcf563
 
 Here's a hopefully fixed version.

Works for me on :

run0 at uhub1 port 1 Ralink 11g Adapter rev 2.00/1.01 addr 3
run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), address 
1c:af:f7:11:9c:1b


MD5 (/etc/firmware/run-rt3071) = 0e877b1acde54b05bef0bc0ca08478e7

-- 
Matthieu Herrb



Re: run(4) firmware update; please test

2014-05-16 Thread Dinar Talypov
Hi,

I have tested with D-Link  DWA-140 rev B2G:

run0 at uhub0 port 1 Ralink 11n Adapter rev 1.10/1.01 addr 2
run0: MAC/BBP RT3071 (rev 0x021C), RF RT3022 (MIMO 2T2R), address
14:d6:4d:49:73:4e

with this diff nothing works. It doesn't find any access point.



2014-05-15 19:32 GMT+04:00 Fred open...@crowsons.com:

 On 05/15/14 10:35, Stefan Sperling wrote:

 This firmware update to version 0.33 is a prequisite for
 newer run(4) devices which are not yet supported.

 Can active users of run(4) devices please test this update
 to make sure no regressions are introduced for already working
 devices? I don't have a supported run(4) device to test with.

   cd /usr/src/sys/dev/microcode/rum  # yes, rum with m
   patch  this-patch
   make obj
   make depend
   sudo make install

 I've obtained permission from Mediatek/Ralink to distribute this
 firmware update under the terms in /etc/firmware/run-license.


 Hi,

 Tested with the at TP-Link TL-WN727N USB Wifi device:

 May 15 13:24:46 x41 /bsd: run0 at uhub0 port 4 Ralink 802.11 n WLAN rev
 2.00/1.01 addr 3
 May 15 13:24:46 x41 /bsd: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020
 (MIMO 1T1R), address 74:ea:3a:8a:b6:8f

 No regressions with this diff.

 Thanks

 Fred




Re: run(4) firmware update; please test

2014-05-16 Thread Stefan Sperling
On Fri, May 16, 2014 at 02:44:10PM +0400, Dinar Talypov wrote:
 Hi,
 
 I have tested with D-Link  DWA-140 rev B2G:
 
 run0 at uhub0 port 1 Ralink 11n Adapter rev 1.10/1.01 addr 2
 run0: MAC/BBP RT3071 (rev 0x021C), RF RT3022 (MIMO 2T2R), address
 14:d6:4d:49:73:4e
 
 with this diff nothing works. It doesn't find any access point.

Are you able to help me debug this by providing more details?

Are you really sure it's the firmware update that's causing the problem?

Are you able to try your run(4) device with FreeBSD-current (10 isn't
new enough)? They claim to support your device and use the updated firmware.



Re: run(4) firmware update; please test

2014-05-16 Thread Raphael Graf
On Thu, May 15, 2014 11:35 am, Stefan Sperling wrote:
 This firmware update to version 0.33 is a prequisite for
 newer run(4) devices which are not yet supported.

 Can active users of run(4) devices please test this update
 to make sure no regressions are introduced for already working
 devices? I don't have a supported run(4) device to test with.


This one keeps working as expected:

run0 at uhub13 port 1 Belkin Belkin Enhanced Wireless USB Adapter rev 
2.00/1.01 addr 2
run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 
00:22:75:f5:df:b8




Re: run(4) firmware update; please test

2014-05-16 Thread Gerhard Roth
On Fri, 16 May 2014 13:07:24 +0200 Stefan Sperling s...@openbsd.org wrote:
 On Fri, May 16, 2014 at 02:44:10PM +0400, Dinar Talypov wrote:
  Hi,
  
  I have tested with D-Link  DWA-140 rev B2G:
  
  run0 at uhub0 port 1 Ralink 11n Adapter rev 1.10/1.01 addr 2
  run0: MAC/BBP RT3071 (rev 0x021C), RF RT3022 (MIMO 2T2R), address
  14:d6:4d:49:73:4e
  
  with this diff nothing works. It doesn't find any access point.
 
 Are you able to help me debug this by providing more details?
 
 Are you really sure it's the firmware update that's causing the problem?
 
 Are you able to try your run(4) device with FreeBSD-current (10 isn't
 new enough)? They claim to support your device and use the updated firmware.
 


He's using a model that requires a firmware-blob different from the one
of all other testers (run-rt2870 vs. run-rt3071). That might explain,
why he's the only one who got troubles with the new FW.

On topic: new FW works fine on a SparkLAN WPER-150GN:

   run0 at uhub1 port 3 Ralink 802.11 n WLAN rev 2.00/1.01 addr 3
   run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 
00:0e:8e:xx:xx:xx



Re: run(4) firmware update; please test

2014-05-16 Thread Alexey Suslikov
Stefan Sperling stsp at openbsd.org writes:

 Are you able to try your run(4) device with FreeBSD-current (10 isn't
 new enough)? They claim to support your device and use the updated 
firmware.

Please take a look at my (unfinished) attempt to bring
MediaTek/Ralink RT5370/RT5372 support to run(4).

http://marc.info/?l=openbsd-techm=138903287819764w=2






Re: run(4) firmware update; please test

2014-05-15 Thread Stefan Sperling
On Thu, May 15, 2014 at 11:35:32AM +0200, Stefan Sperling wrote:
  cd /usr/src/sys/dev/microcode/rum  # yes, rum with m
  patch  this-patch
  make obj
  make depend
  sudo make install

This should have said 'make' instead of 'make depend'.



Re: run(4) firmware update; please test

2014-05-15 Thread Fred

On 05/15/14 10:35, Stefan Sperling wrote:

This firmware update to version 0.33 is a prequisite for
newer run(4) devices which are not yet supported.

Can active users of run(4) devices please test this update
to make sure no regressions are introduced for already working
devices? I don't have a supported run(4) device to test with.

  cd /usr/src/sys/dev/microcode/rum  # yes, rum with m
  patch  this-patch
  make obj
  make depend
  sudo make install

I've obtained permission from Mediatek/Ralink to distribute this
firmware update under the terms in /etc/firmware/run-license.



Hi,

Tested with the at TP-Link TL-WN727N USB Wifi device:

May 15 13:24:46 x41 /bsd: run0 at uhub0 port 4 Ralink 802.11 n WLAN 
rev 2.00/1.01 addr 3
May 15 13:24:46 x41 /bsd: run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 
(MIMO 1T1R), address 74:ea:3a:8a:b6:8f


No regressions with this diff.

Thanks

Fred