Re: [PATCH 0/2] ar9170-fw: Roll-your-own toolchain

[Jan Kiszka <jan.kiszka@web.de>]

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

Johannes Berg wrote:
> On Sat, 2009-06-06 at 19:37 +0200, Jan Kiszka wrote:
> 
>>> Yes. With the AP firmware, that is. I don't care about that firmware at
>>> all.
>> I do as it shall upgrade my soft-AP from an oldish rt2500 to this
>> dwa-160 stick.
> 
> No, you don't actually need AP software for that. The STA software
> supports most of AP already.

The last statement I read was: "haven't found a way to properly transmit
multicast frames after DTIM". Does this still apply on the new STA
firmware? What is the state of AP mode in the driver source? Just
disabled, some bits missing - or even ready to work?

> 
>> Are you at least interested in porting the missing AP bits into the STA
>> version (likely the best long-term approach anyway)? And do you have a
>> rough idea which bits are missing / where to look at?
> 
> Yes, that would be the plan. No, I have no idea what's missing. There
> are tools like diff though :)

Yeah:
# diff -up nice-code-1.c nice-code-2.c | manual-filter
...
-rxBBReg = reg_read_PHY(0x1c5960); //*(volatile u32_t*)(0x1c5960); /* 0x1c8960 write only */
+rxBBReg = *(volatile u32_t*)(0x1c5960); /* 0x1c8960 write only */
...

That will be a "nice" job... :)


Another silly question: You wrote that 802.11n works with the firmware,
and I blindly assumed that this of course includes a/b/g. I was right?
My current AP works in g-mode when association with the ar9170 fails...

Thanks so far,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]