Whoops, I replied to the first message wrong, so I'll bring it back
to the list...
I don't have access at the moment to a FreeBSD box to point to
specifics, but I'd recommend looking at ifconfig sources (/usr/src/
sbin/ifconfig/ifieee80211.c?) to see which ioctl is being called for
the txpower argument. Then, follow that down into /usr/src/sys/
net80211/ieee80211_ioctl.c and see what's happening from the net80211
layer to the driver.
-d
On Aug 10, 2005, at 2:50 PM, Sam Pierson wrote:
I'm not sure, exactly. What happened was, I brought a laptop
far away and then sent some UDP packets to it from an ath
card. It receives all of them correctly. When I turn the global
power down (ifconfig ath0 txpower 1), it cannot receive the
packets. There is a little variation, when I set it to 9, only
some of the packets are received, and when I set it to 19
or greater, most of the packets are received.
-Sam
On 8/10/05, Deker <[EMAIL PROTECTED]> wrote:
I wasn't aware that the HAL supported variable TX power yet. Has
there been some update to allow the txpower argument to
ath_hal_tx_start to be honored?
-d
On Aug 10, 2005, at 1:53 PM, Sam Pierson wrote:
I noticed that when I control the signal strength through
ifconfig, I can effectively reduce the signal when I set it
as something like: ifconfig ath0 txpower 1. I have read
that this input is device driver dependent and I couldn't
find anything in the interface that handles txcontrol. Are
these values taken in exactly or are they rounded to some
less fine-grained control number? Thanks,
Sam
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-
[EMAIL PROTECTED]"
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
