2008/7/29 Michael Renzmann <[EMAIL PROTECTED]>:
> Hi.
>
> Geoffrey McRae wrote:
>> iwconfig is reporting that my TX power is 27dBm,
>
> This is reported for all cards, no matter if they actually support this
> much or not. TX power settings are not yet touched by the driver.
>
> Bye, Mike
I'll soo
Hi.
Geoffrey McRae wrote:
> iwconfig is reporting that my TX power is 27dBm,
This is reported for all cards, no matter if they actually support this
much or not. TX power settings are not yet touched by the driver.
Bye, Mike
___
ath5k-devel mailing lis
Hey All,
I am using nick's patched driver with ar2425 support. iwconfig is
reporting that my TX power is 27dBm, thats about 500mw, is this correct,
can this device actually transmit at those levels? In Australia the max
legal limit is 100mw as far as I know.
Can anyone clear this up? I mean, it w
Thank you for great news and thank you all for your hard work.
Cheers,
Valent.
On Mon, Jul 28, 2008 at 4:48 PM, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> 2008/7/28 Pavel Roskin <[EMAIL PROTECTED]>:
>> Quoting Jaco Kroon <[EMAIL PROTECTED]>:
>>
>>> Does somebody need to actually sit down and do
2008/7/28 Pavel Roskin <[EMAIL PROTECTED]>:
> Quoting Jaco Kroon <[EMAIL PROTECTED]>:
>
>> Does somebody need to actually sit down and do that or is there an
>> automated process for this? The drivers there works for me (same
>> chipset as Valent) and I'd be willing to sit down and generate diffs
2008/7/28 Pavel Roskin <[EMAIL PROTECTED]>:
> On Mon, 2008-07-28 at 16:04 +0300, Nick Kossifidis wrote:
>
>> > Please amend this to the patch 1 to not break bisectability.
>>
>> I see your point but this series is meant to be applied as a whole, i
>> didn't notice this bug until i tested the code w
Pavel Roskin wrote:
> Quoting Jaco Kroon <[EMAIL PROTECTED]>:
>
>> Does somebody need to actually sit down and do that or is there an
>> automated process for this? The drivers there works for me (same
>> chipset as Valent) and I'd be willing to sit down and generate diffs
>> over the coming week
Quoting Jaco Kroon <[EMAIL PROTECTED]>:
> Does somebody need to actually sit down and do that or is there an
> automated process for this? The drivers there works for me (same
> chipset as Valent) and I'd be willing to sit down and generate diffs
> over the coming weekend, permitting somebody can
Pavel Roskin wrote:
> On Mon, 2008-07-28 at 14:23 +0200, Valent Turkovic wrote:
>> Hi,
>> I'm would like to help test and troubleshoot ath5k when you guys (and
>> gals?) add support for AR2425 (AR5007EG) chipset.
>>
>> I own Asus eee PC 701 which comes with AR2425 (AR5007EG) wireless
>> chipset. It
On Mon, 2008-07-28 at 16:04 +0300, Nick Kossifidis wrote:
> > Please amend this to the patch 1 to not break bisectability.
>
> I see your point but this series is meant to be applied as a whole, i
> didn't notice this bug until i tested the code with debugging enabled
> (which is off by default),
2008/7/22 Jiri Slaby <[EMAIL PROTECTED]>:
> On 07/20/2008 05:52 AM, Nick Kossifidis wrote:
>> Last minute fix...
>>
>> AR5K_CPCORN is changed to AR5K_CPCOVF in reg list update so we have to
>> update debug.c in order to compile
>>
>> Changes-licensed-under: ISC
>> Signed-off-by: Nick Kossifidi
2008/7/22 Jiri Slaby <[EMAIL PROTECTED]>:
> On 07/20/2008 05:41 AM, Nick Kossifidis wrote:
>>
>> * Update ath5k_hw_reset and add some more documentation about PHY
>> calibration
>> * Fix ath5k_hw_set_power to use AR5K_SLEEP_CTL_SLE_ALLOW for Network
>> sleep
>> * Preserve sleep duration field wh
On Mon, 2008-07-28 at 14:23 +0200, Valent Turkovic wrote:
> Hi,
> I'm would like to help test and troubleshoot ath5k when you guys (and
> gals?) add support for AR2425 (AR5007EG) chipset.
>
> I own Asus eee PC 701 which comes with AR2425 (AR5007EG) wireless
> chipset. It is a very popular device s
Hi,
I'm would like to help test and troubleshoot ath5k when you guys (and
gals?) add support for AR2425 (AR5007EG) chipset.
I own Asus eee PC 701 which comes with AR2425 (AR5007EG) wireless
chipset. It is a very popular device so I can't wait to test ath5k
when it adds support for 5007.
I'm not a
> I've been looking at this too. After the "revamp beacon configuration"
> patch, mesh no longer send beacons. If I revert it, beacons reappear and
> my two stations are found. I'm using both a b43 & zd1211rw.
>
> I believe the problem is in mac80211. It appears that the call to
> ieee80211_if
Dear Louay, Benoit, Nick and Chr,
first of all I thank you all to have spent some of your time repliing
to me, then I go to explain better and to reply to you all about your
cumulative questions.
1) Our radio cards is "physically" capable (RF + BB) to operate from 2.26 to
2.52 GHz and
On Fri, Jul 18, 2008 at 4:12 AM, Andrey Yurovsky <[EMAIL PROTECTED]> wrote:
> This enables draft-802.11s Mesh Point operation. For that we need mesh
> beaconing. Tested with AR5212/AR5213 PCI card against Zydas and b43 mesh
> nodes.
>
> Signed-off-by: Andrey Yurovsky <[EMAIL PROTECTED]>
> ---
> d
17 matches
Mail list logo
