Hi.
>> Nope but i believe that regdumps from them should give us something...
> Yes, but its easier if we get you an BG card for testing purposes.
> Anyone know where we can reliably purchase them from?
I have to check first, but I think that we have received a b/g-only card
from Compex as part o
On 11/1/07, Luis R. Rodriguez <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 01, 2007 at 12:31:57AM -0400, Luis R. Rodriguez wrote:
> > Here are a few patches which start fixing G mode settings.
>
> Forgot to mention these depend on Nick's 1-7 series patches plus,
>
> [PATCH] ath5k: Remove fill_tx_desc
>
On Wed, 2007-10-31 at 14:39 -0700, Daniel Wu wrote:
> > >
> > > The /proc/sys/dev/ath/debug and others are fine.
> >
> > Just yesterday, I committed a fix for sysctl for Linux 2.6.24-rc1. Are
> > you running Linux 2.6.24-rc1 by any chance? Perhaps my sysctl patches
> > should be propagated to oth
> >
> > The /proc/sys/dev/ath/debug and others are fine.
>
> Just yesterday, I committed a fix for sysctl for Linux 2.6.24-rc1. Are
> you running Linux 2.6.24-rc1 by any chance? Perhaps my sysctl patches
> should be propagated to other branches.
I'm running:
[EMAIL PROTECTED] madwifi-trace]# una
Hello!
On Wed, 2007-10-31 at 14:20 -0700, Daniel Wu wrote:
> Hey, not sure if i should ask here, but here goes:
>
> i tried using the madwifi-trace and the madwifi-trace.sh, but I'm
> getting errors:
>
> I can't seem to write into the /proc/sys/dev/ath/hal/ directory,
> The error:
> [EMAIL PROTE
Hey, not sure if i should ask here, but here goes:
i tried using the madwifi-trace and the madwifi-trace.sh, but I'm
getting errors:
I can't seem to write into the /proc/sys/dev/ath/hal/ directory,
The error:
[EMAIL PROTECTED] ~]# echo 1 > /proc/sys/dev/ath/hal/alq
bash: echo: write error: Cannot
On 10/31/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> 2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> > On 10/31/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> > > 2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> > > > On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> > > >
>
2007/10/31, Ulrich Meis <[EMAIL PROTECTED]>:
> On Mon 29.10.07 17:12, Ulrich Meis wrote:
> [snip]
> > There's just one problem...I can't send more than 2312 bytes, which also
> > happens to be the limit defined in the 802.11 spec. Or maybe I can, but
> > the receiver(also running ath5k) doesn't acc
2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> On 10/31/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> > 2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> > > On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> > >
> > > > * Give more infos about mac/phy/radio revision during attac
On 10/31/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> 2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> > On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> >
> > > * Give more infos about mac/phy/radio revision during attach.
> >
> > > @@ -535,10 +568,24 @@ ath5k_pci_probe(struct pci
2007/10/31, Luis R. Rodriguez <[EMAIL PROTECTED]>:
> On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
>
> > * Give more infos about mac/phy/radio revision during attach.
>
> > @@ -535,10 +568,24 @@ ath5k_pci_probe(struct pci_dev *pdev,
> > if (ret)
> > goto err_ah;
>
On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> * Give more infos about mac/phy/radio revision during attach.
> @@ -535,10 +568,24 @@ ath5k_pci_probe(struct pci_dev *pdev,
> if (ret)
> goto err_ah;
>
> - dev_info(&pdev->dev, "%s chip found: mac %d.%d phy %d
On 10/31/07, Luis R. Rodriguez <[EMAIL PROTECTED]> wrote:
> On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
>
> > Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
>
> This if for your patches 1-7 and the new descriptor rework. I've
> tested this on x86 and big-endian. Big-endian works wel
On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> Signed-Off-by: Nick Kossifidis <[EMAIL PROTECTED]>
This if for your patches 1-7 and the new descriptor rework. I've
tested this on x86 and big-endian. Big-endian works well except if you
use dhclient you won't get an IP address, please use
On Sun, 28 Oct 2007 02:15:31 +0200 Evgeni Golov wrote:
> Hope this helps you :)
Any updates on this? Or any suggestions how I could help?
___
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
On 10/30/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> 2007/10/30, Ulrich Meis <[EMAIL PROTECTED]>:
> > On Tue 30.10.07 12:45, Luis R. Rodriguez wrote:
> > > On 10/27/07, Nick Kossifidis <[EMAIL PROTECTED]> wrote:
> > > > fill_tx_desc is used for fast frames operation, since
> > > > we don't sup
On Mon 29.10.07 17:12, Ulrich Meis wrote:
[snip]
> There's just one problem...I can't send more than 2312 bytes, which also
> happens to be the limit defined in the 802.11 spec. Or maybe I can, but
> the receiver(also running ath5k) doesn't accept it...on that side I
> hacked into the rx tasklet an
Just noticed that you have 5111 phy so plz ignore previous mail...
BUFFER_CONTROL_5 is right and we do the same for > 5112
2007/10/31, Nick Kossifidis <[EMAIL PROTECTED]>:
> ACK nevermind your script does enough magic already ;-)
>
> Here is an interesting find comparing your dumps of 5414 and 52
ACK nevermind your script does enough magic already ;-)
Here is an interesting find comparing your dumps of 5414 and 5213...
while on 5213 we change channel by setting RF_BUFFER and then
RF_BUFFER_CONTROL_3 on 5414 RF_BUFFER_CONTROL_5 is used, also there is
some difference between them (we can po
19 matches
Mail list logo
