From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 15 00:24:07 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C58AC16A4CE for ; Wed, 15 Sep 2004 00:24:07 +0000 (GMT) Received: from newmail.slackdot.org (mail2.slackdot.org [66.92.146.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4762243D1F for ; Wed, 15 Sep 2004 00:24:07 +0000 (GMT) (envelope-from deker@slackdot.org) Received: from localhost (localhost [127.0.0.1]) by newmail.slackdot.org (Postfix) with ESMTP id 2D44914AF6; Tue, 14 Sep 2004 20:22:08 -0400 (EDT) Received: from newmail.slackdot.org ([127.0.0.1]) by localhost (newmail.slackdot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11525-09; Tue, 14 Sep 2004 20:22:05 -0400 (EDT) Received: from [192.168.0.157] (unknown [192.168.0.157]) by newmail.slackdot.org (Postfix) with ESMTP id 4A97C141BF; Tue, 14 Sep 2004 20:22:05 -0400 (EDT) From: Rob Deker To: Sam Leffler In-Reply-To: <200409141621.52897.sam@errno.com> References: <41475335.5020507@slackdot.org> <200409141621.52897.sam@errno.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-bmz/ZYRuL99KHqH1s1bo" Message-Id: <1095207831.16006.10.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 14 Sep 2004 20:23:51 -0400 X-Virus-Scanned: by amavisd-new at slackdot.org cc: freebsd-hackers@freebsd.org Subject: Re: Parameters passed to ath_hal_setuptxdesc() from ath(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2004 00:24:07 -0000 --=-bmz/ZYRuL99KHqH1s1bo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-09-14 at 19:21, Sam Leffler wrote: > > ~ - Is this a function of the HAL? >=20 > hardware (but only 5210 parts need it). >=20 > > ~ - 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? >=20 > hdrLen <=3D pktLen probably; though I'm not sure a 5210 would care what y= ou=20 > supplied. >=20 So if it were to have an "incorrect" value would listening STAs still properly recieve the packet? Also, on a related note, is the txpower parameter actually honored? I noted that it's hardcoded to '60' and wondered. thanks, -d --=-bmz/ZYRuL99KHqH1s1bo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBR4uXiIu2X5vnl3ERAvteAKDJmLpTWmUsyVbvP/P1wo/sVTgzBACg8YxF uULF0WRedEujbAkMUAuSRS4= =GiaF -----END PGP SIGNATURE----- --=-bmz/ZYRuL99KHqH1s1bo--