Date: Tue, 14 Sep 2004 21:24:36 -0700 From: Sam Leffler <sam@errno.com> To: Rob Deker <deker@slackdot.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Parameters passed to ath_hal_setuptxdesc() from ath(4) Message-ID: <26CB460B-06CF-11D9-A154-000A95AD0668@errno.com> In-Reply-To: <1095207831.16006.10.camel@localhost> References: <41475335.5020507@slackdot.org> <200409141621.52897.sam@errno.com> <1095207831.16006.10.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 14, 2004, at 5:23 PM, Rob Deker wrote: > On Tue, 2004-09-14 at 19:21, Sam Leffler wrote: > >>> ~ - Is this a function of the HAL? >> >> hardware (but only 5210 parts need it). >> >>> ~ - If so, does the header length parameter to ath_hal_setuptxdesc() >>> tell the HAL how many bytes it needs to send at a slower rate? >>> ~ - If the answers to the first two questions were "yes", and I >>> wanted >>> to provide a mechanism for the application programmer to specify >>> his/her header length, what (if any) are the limits imposed on this >>> parameter by the HAL? >> >> hdrLen <= pktLen probably; though I'm not sure a 5210 would care what >> you >> supplied. >> > So if it were to have an "incorrect" value would listening STAs still > properly recieve the packet? I have no idea, try it. > Also, on a related note, is the txpower parameter actually honored? I > noted that it's hardcoded to '60' and wondered. per-packet TPC is not working right now. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26CB460B-06CF-11D9-A154-000A95AD0668>