Re: [Madwifi-users] System hanging in ad hoc mode operation..

[Amit K. <aku...@me...>]

On Thu, 2004-01-22 at 17:42, Sam Leffler wrote:

> the network.  I believe this is caused by misprogramming of the beacon=20
> timer(s) but have had no time to work on it (and adhoc is so low on my=20
> priority list that I can't even see it).  If this is your problem then if=
 you=20

That is bad news indeed for all of us that need ad hoc mode support. I
have written some code to merge two IBSS' when they have a common essid.
But the beacons are being a problem: Beacon generation seems to stop
arbitrarily.

> dump the h/w registers with
>=20
> echo hal > /proc/sys/dev/ath/dump
>=20
> you'll see the BEAC_CNT register does not increment.
>=20
> I don't know if this can be fixed in the driver or if the fix must happen=
 in=20
> the HAL.  Regardless it's a problem someone (other than me) can work on.
>=20
> 	Sam

Who is this someone else? Maybe I could co-ordinate my efforts with
him/her. Without that, I can only seem to trace down to
ath_beacon_config() where the timers are supposedly initialized.

--=20
     .| Amit Kucheria                       |.
   ...| Wireless Systems Engineer           |...
 .....| Metric Systems Corp., San Diego, CA |.....
......| www.metricsystems.com               |......