Re: [Madwifi-users] Fast channel switching

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

800 -- 1000 microseconds seems to be working (in ahdemo mode atleast),
though I have to test intensely. But why do u suggest 30 - 50ms, is it
harware limitation or it is an issue with madwifi driver??

On Wed, Feb 24, 2010 at 3:45 PM, IVAN KORSHUN <200...@ma...> wrote:

> 100 microsecond  too small ...
> need 30 ... 50 ms
>
>
> > Hi Ivan
> >
> > Thanks a lot for the help. The function seems to be working, although I
> had
> > to make few changes. If I used the addess, 0xb8510024 for AR_IER it was
> > giving segmentation fault. However it did work with address 0x0024
> (likewise
> > for other registers too). But although the frequency does get changed, it
> > does not get reflected in iwconfig command. For it I guess I will have to
> > set the member variable ic_curchan of variable ic (of type ieee80211com),
> > which Iam trying to figure out.
> >
> > However one of the other issues is that this function is taking about
> 30ms
> > for switching the channel (I have tested it on x86 based IBM laptop).
> > Whereas we need a channel switching functionality of the order of
> > microseconds (preferably around 500 microseconds if possible). On
> analyzing
> > your function I observed that following for loop
> >
> > for (ii=0; (ii< 0x3FFFE) && channelSelect ;ii++)channelSelect =*hard_reg
> &
> > 0x2;
> >
> > takes about 30ms. Although in place of this for loop I put a delay of
> about
> > 100 microsecond and it does seem to work (though I have to test
> thouroughly
> > as to whether any packets are getting lost). Also Iam trying to figure
> the
> > optimal values for the different delays that you have called in your
> > function.
> >
> > Could you please let me know as to on what basis have you come up with
> these
> > different values of delay (ie. 0x3E8, 0xA, 0x64, and the for loop), as it
> > would help me in optimizing these values for my hardware.
> >
> > Thanks
> > Vishal
> >
> > On Tue, Feb 23, 2010 at 1:27 PM, IVAN KORSHUN <200...@ma...> wrote:
> >
> > > sysUDelayFlash its ath_hal_delay(int n) /* Delay n microseconds */
> > > I use non Linux OS ...
> > >
> > > ar5212SetChannel5112work2192(2192); //set freq 2192 MHz
> > > ar5212SetChannel5112work2192(2195); //set freq 2195 MHz
> > > ...
> > > ar5212SetChannel5112work2192(2512); //set freq 2512 MHz
> > >
> > > and hard_reg ...
> > > 0xB8510024 its AR_IER                  0x0024  /* MAC Interrupt enable
> > > register */
> > > 0xb851981c its AR_PHY_ACTIVE           0x981C  /* activation register
> */
> > > 0xb8519860 its AR_PHY_AGC_CONTROL      0x9860  /* chip calibration and
> > > noise floor setting */
> > >
> > > 0xb851989C & 0xb85198D8  its regs for internal use ...
> > >
> > >
> > > -----Original Message-----
> > > From: Vishal Sevani <vis...@gm...>
> > > To: mad...@li...
> > > Date: Tue, 23 Feb 2010 12:05:05 +0530
> > > Subject: Re: [Madwifi-users] Fast channel switching
> > >
> > > > On Mon, Feb 22, 2010 at 10:19 PM, IVAN KORSHUN <200...@ma...>
> > > wrote:
> > > >
> > > > > void ar5212SetChannel5112work2192(UINT32 freq)
> > > > > {
> > > > > /* Step 5 MHz */
> > > > >           UINT32       ii,channelSelect;
> > > > > volatile   UINT32 *hard_reg;
> > > > >
> > > > >        channelSelect = ((freq - 672) * 2 - 3040)/10;
> > > > >            channelSelect = (channelSelect << 2) & 0xff;
> > > > >            channelSelect = ath_hal_reverseBits(channelSelect, 8);
> > > > >
> > > > >
> > > > >        channelSelect = (channelSelect << 4) | 0x1005;
> > > > >
> > > > >        hard_reg = (void*)0xB8510024; *hard_reg = 0x0;
> > > > >        sysUDelayFlash (0x3E8);
> > > > >        hard_reg = (void*)0xb851981c; *hard_reg = 0x0;
> > > > >        sysUDelayFlash (0xA);
> > > > >        hard_reg = (void*)0xb851989C; *hard_reg = (channelSelect &
> > > 0xff);
> > > > >
> > > > >        channelSelect = (channelSelect >> 8) & 0x7f;
> > > > >        hard_reg = (void*)0xb85198D8; *hard_reg = channelSelect;
> > > > >        sysUDelayFlash (0xA);
> > > > >        hard_reg = (void*)0xb851981c; *hard_reg = 0x1;
> > > > >        sysUDelayFlash (0x64);
> > > > >        hard_reg = (void*)0xb8519860;
> > > > >        *hard_reg = *hard_reg |0x2;
> > > > >        channelSelect = 0x2;
> > > > >        for (ii=0; (ii< 0x3FFFE) && channelSelect
> ;ii++)channelSelect =
> > > > > *hard_reg & 0x2;
> > > > >
> > > > >        hard_reg = (void*)0xB8510024; *hard_reg = 0x1;
> > > > >
> > > > > }
> > > > >
> > > >
> > > > Hi Ivan
> > > >
> > > > Do you intend to suggest that I can call this function directly for
> > > > switching the frequency?? If so could you please explain as to what
> the
> > > > function does. You are setting the values for the variable, hard_reg
> and
> > > > channelSelect, but dont you need to set these values in the register
> so
> > > that
> > > > the hardware actually changes the channel?
> > > >
> > > >  Also what is the definition for the function, sysUDelayFlash ()
> since it
> > > is
> > > > not available in the madwifi code.
> > > >
> > > > Thanks
> > > > Vishal
> > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Vishal Sevani <vis...@gm...>
> > > > > To: mad...@li...
> > > > > Date: Mon, 22 Feb 2010 14:10:04 +0530
> > > > > Subject: Re: [Madwifi-users] Fast channel switching
> > > > >
> > > > > > On Sat, Feb 20, 2010 at 5:00 AM, Pavel Roskin <pr...@gn...>
> > > wrote:
> > > > > >
> > > > > > > On Fri, 2010-02-19 at 15:17 +0530, Vishal Sevani wrote:
> > > > > > >
> > > > > > > >         > I did apply the following patch
> > > > > > > >         > https://madwifi-project.org/ticket/2322 , but to
> no
> > > avail.
> > > > > > > >         Could you
> > > > > > > >         > point out as to what the problem could be?? If you
> need
> > > me
> > > > > > > >         to provide
> > > > > > > >         > any other debug information please do let me know.
> > > > > > > >
> > > > > > > >
> > > > > > > >         I'll appreciate if you post your results to the
> ticket.
> > >  So
> > > > > > > >         far there
> > > > > > > >         have been no test results for that patch at all.
> > > > > > > >
> > > > > > > > Yeah I have posted my experience in the following ticket.
> > > > > > > > https://madwifi-project.org/ticket/2359
> > > > > > >
> > > > > > > I actually I meant that you would report a negative result with
> the
> > > > > > > patch in #2322.  But it looks like the problems are different.
> > > > > > >
> > > > > > > Yeah it seems more of a hardware issue with AR71xx borad, (or
> issue
> > > > > with
> > > > > > Openwrt) as pointed out by ne...@pa... in his comment
> > > following
> > > > > yours
> > > > > > in the ticket #2359. If Iam correct, it is happening because the
> > > value in
> > > > > > reg AR_ISR corresponding to flag AR_ISR_HIUERR is being set,
> which is
> > > for
> > > > > > unexpected bus error. As mentioned in the following post
> > > > > > http://n2.nabble.com/fatal-interrupt-td3225930.html, it is
> beacuse
> > > the
> > > > > > following bit, AR_ISR_S2_MCABT  (for master cycle abort) is being
> > > set.
> > > > > >
> > > > > > Iam clueless as to what could be causing this master cycle abort
> > > problem
> > > > > and
> > > > > > how should I go about debugging it. Could you please provide any
> > > pointers
> > > > > as
> > > > > > to how I can rectify this problem.
> > > > > >
> > > > > >
> > > > > > > > Yesterday again I tried with latest release of Openwrt
> Kamikaze
> > >  ie.
> > > > > > > > v8.09.2, but still I get the same problem. But the madwifi
> code
> > > works
> > > > > > > > properly on IBM latop running Ubuntu with Linux kernel
> 2.6.24-23.
> > > So
> > > > > I
> > > > > > > > guess it is the issue with Openwrt or the hardware ie. AR71xx
> > > boards.
> > > > > > > > Has the latest code been tested on Openwrt and Ar71xx
> boards??
> > > > > > >
> > > > > > > I'm not aware of it.
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Pavel Roskin
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > >
> ------------------------------------------------------------------------------
> > > > > > Download Intel  Parallel Studio Eval
> > > > > > Try the new software tools for yourself. Speed compiling, find
> bugs
> > > > > > proactively, and fine-tune applications for parallel performance.
> > > > > > See why Intel Parallel Studio got high marks during beta.
> > > > > > http://p.sf.net/sfu/intel-sw-dev
> > > > > > _______________________________________________
> > > > > > Madwifi-users mailing list
> > > > > > Mad...@li...
> > > > > > https://lists.sourceforge.net/lists/listinfo/madwifi-users
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > >
> ------------------------------------------------------------------------------
> > > > > Download Intel  Parallel Studio Eval
> > > > > Try the new software tools for yourself. Speed compiling, find bugs
> > > > > proactively, and fine-tune applications for parallel performance.
> > > > > See why Intel Parallel Studio got high marks during beta.
> > > > > http://p.sf.net/sfu/intel-sw-dev
> > > > > _______________________________________________
> > > > > Madwifi-users mailing list
> > > > > Mad...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/madwifi-users
> > > > >
> > > >
> > > >
> > >
> ------------------------------------------------------------------------------
> > > > Download Intel  Parallel Studio Eval
> > > > Try the new software tools for yourself. Speed compiling, find bugs
> > > > proactively, and fine-tune applications for parallel performance.
> > > > See why Intel Parallel Studio got high marks during beta.
> > > > http://p.sf.net/sfu/intel-sw-dev
> > > > _______________________________________________
> > > > Madwifi-users mailing list
> > > > Mad...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/madwifi-users
> > > >
> > > >
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > Download Intel  Parallel Studio Eval
> > > Try the new software tools for yourself. Speed compiling, find bugs
> > > proactively, and fine-tune applications for parallel performance.
> > > See why Intel Parallel Studio got high marks during beta.
> > > http://p.sf.net/sfu/intel-sw-dev
> > > _______________________________________________
> > > Madwifi-users mailing list
> > > Mad...@li...
> > > https://lists.sourceforge.net/lists/listinfo/madwifi-users
> > >
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel  Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Madwifi-users mailing list
> > Mad...@li...
> > https://lists.sourceforge.net/lists/listinfo/madwifi-users
> >
> >
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Madwifi-users mailing list
> Mad...@li...
> https://lists.sourceforge.net/lists/listinfo/madwifi-users
>