On Monday 29 October 2007 23:56:02 Nick Kossifidis wrote:
> BTW can you add support for BB_GAIN and RF_GAIN tables and possibly
> RF_PHY (for all unknown phy registers) ?
sure, it's as easy as adding the right ranges to the wiki.
can you tell me the end addresses?
i'm guessing:
0x9a00-0x9aff ?
On Mon, Oct 29, 2007 at 04:28:02PM +0200, Nick Kossifidis wrote:
> Can you plz see if madwifi-old-openhal works for you and also plz make
> some more traces, especially for phy related functions and post them
> here.
I tried madwifi-old-openhal with 2.6.23 as well as the most recent
wireless-2.6 t
On Mon 29.10.07 19:00, Nick Kossifidis wrote:
> > I hacked into the tx function and managed to let the card send out the
> > contents of two descriptors in one frame. I didn't do any encapsulation,
> > I just copied the first packet(an ICMP echo request), fetched a second
> > buffer, called the fil
> I hacked into the tx function and managed to let the card send out the
> contents of two descriptors in one frame. I didn't do any encapsulation,
> I just copied the first packet(an ICMP echo request), fetched a second
> buffer, called the fill functions appropriately and finally it worked. I
> c
On Sat 27.10.07 03:12, Nick Kossifidis wrote:
[snip]
> About fast frames: actually it's more complicated, we have more
> descriptors for each buffer, we have to do encapsulation and
> decapsulation (check out madwifi code) by also tweaking the stack etc.
> Currently noone is working on fast frames
2007/10/29, Nick Kossifidis <[EMAIL PROTECTED]>:
> 2007/10/25, bruno randolf <[EMAIL PROTECTED]>:
> > On Wednesday 24 October 2007 23:11:41 you wrote:
> > > On 10/24/07, bruno randolf <[EMAIL PROTECTED]> wrote:
> > > > ok, i put up the register list on
> > > > http://madwifi.org/wiki/DevDocs/Athero
2007/10/25, bruno randolf <[EMAIL PROTECTED]>:
> On Wednesday 24 October 2007 23:11:41 you wrote:
> > On 10/24/07, bruno randolf <[EMAIL PROTECTED]> wrote:
> > > ok, i put up the register list on
> > > http://madwifi.org/wiki/DevDocs/AtherosRegisters.
> >
> > This is nice, however I was planning on
2007/10/29, Frank de Lange <[EMAIL PROTECTED]>:
> > O.K. lets start with this (line 639 after my patches):
> >
> > In ath5k_hw_reset we do this...
> >
> > /* PHY access enable */
> > ath5k_hw_reg_write(ah, AR5K_PHY_SHIFT_5GHZ, AR5K_PHY(0));
> >
> > try changing AR5K_PHY_SHIFT_5GHZ to AR5K_PHY_SHIFT
On Mon, 29 Oct 2007 15:08:36 +0200 Nick Kossifidis wrote:
> try changing AR5K_PHY_SHIFT_5GHZ to AR5K_PHY_SHIFT_2GHZ and see what
> happens
No change here :(
Still unable to reset hardware: -22
And the same errors in ip/ifconfig
___
ath5k-devel mailing
> O.K. lets start with this (line 639 after my patches):
>
> In ath5k_hw_reset we do this...
>
> /* PHY access enable */
> ath5k_hw_reg_write(ah, AR5K_PHY_SHIFT_5GHZ, AR5K_PHY(0));
>
> try changing AR5K_PHY_SHIFT_5GHZ to AR5K_PHY_SHIFT_2GHZ and see what
> happens (i haven't checked out regdumps
2007/10/29, Nick Kossifidis <[EMAIL PROTECTED]>:
> 2007/10/29, Frank de Lange <[EMAIL PROTECTED]>:
> > On Mon, Oct 29, 2007 at 01:05:23PM +0100, Frank de Lange wrote:
> > > To reply to my own question, yes -22 is -EINVAL and it seems to be
> > > generated when the driver tries to get the rate table
2007/10/29, Frank de Lange <[EMAIL PROTECTED]>:
> On Mon, Oct 29, 2007 at 01:05:23PM +0100, Frank de Lange wrote:
> > To reply to my own question, yes -22 is -EINVAL and it seems to be
> > generated when the driver tries to get the rate table for the device:
> >
> > [ 2027.007789] ath5k_hw_reset:54
On Mon, Oct 29, 2007 at 01:05:23PM +0100, Frank de Lange wrote:
> To reply to my own question, yes -22 is -EINVAL and it seems to be
> generated when the driver tries to get the rate table for the device:
>
> [ 2027.007789] ath5k_hw_reset:547
> [ 2027.007796] ath5k_hw_nic_wakeup:368
> [ 2027.00780
To reply to my own question, yes -22 is -EINVAL and it seems to be
generated when the driver tries to get the rate table for the device:
[ 2027.007789] ath5k_hw_reset:547
[ 2027.007796] ath5k_hw_nic_wakeup:368
[ 2027.007801] ath5k_hw_set_power:1085
[ 2027.007808] ath5k_hw_nic_reset:1038
[ 2027.009
Hi Frank,
On Mon 29.10.07 12:14, Frank de Lange wrote:
> On Sat, Oct 27, 2007 at 03:01:22PM +0200, Evgeni Golov wrote:
> > So I decided to test ath5k, got wireles-2.6 git, fetched "everything"
> > and compiled the kernel. After a reboot the ath5k module gets loaded
> > and says:
> > phy1: Selected
2007/10/29, Frank de Lange <[EMAIL PROTECTED]>:
> On Sat, Oct 27, 2007 at 03:01:22PM +0200, Evgeni Golov wrote:
> > So I decided to test ath5k, got wireles-2.6 git, fetched "everything"
> > and compiled the kernel. After a reboot the ath5k module gets loaded
> > and says:
> > phy1: Selected rate co
On Sat, Oct 27, 2007 at 03:01:22PM +0200, Evgeni Golov wrote:
> So I decided to test ath5k, got wireles-2.6 git, fetched "everything"
> and compiled the kernel. After a reboot the ath5k module gets loaded
> and says:
> phy1: Selected rate control algorithm 'simple'
> ath5k_pci :03:00.0: AR5212
17 matches
Mail list logo
