From owner-freebsd-current@FreeBSD.ORG Mon Aug 29 00:21:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 237C2106567C for ; Mon, 29 Aug 2011 00:21:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id D4B8C8FC13 for ; Mon, 29 Aug 2011 00:21:28 +0000 (UTC) Received: by yib19 with SMTP id 19so3701531yib.13 for ; Sun, 28 Aug 2011 17:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eikWUXS2Kr8sdJEq8ClC5nAYVqXIJZy1NTeClgg/wiM=; b=AioRvWtRciiS13sW82IMuwfenvb/2UgYjbi69aC1lC1elZfBZcQauZr+fjGOjR/oHg yd4Ngp0uZe9bdFbolI0cRd5iM6gIrit0HI41IfWhAP+ABashw3anuF6KdbAMx6240FER ExMqcZZjRtDU12+Q5AXYRsgugV/vCXJqeLbKI= MIME-Version: 1.0 Received: by 10.151.86.10 with SMTP id o10mr4690815ybl.87.1314577287857; Sun, 28 Aug 2011 17:21:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.145.21 with HTTP; Sun, 28 Aug 2011 17:21:27 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Aug 2011 08:21:27 +0800 X-Google-Sender-Auth: _FG4GVuqsAPOW5Lt4L2zff93EXQ Message-ID: From: Adrian Chadd To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: if_ath - should it be compiled without ath_hal support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 00:21:29 -0000 that looks a bit special. On 29 August 2011 07:38, Garrett Cooper wrote: >> I'd like to eventually split out the ath_hal again into a separate >> module and re-instate the separation between HAL and driver code >> (primarily to enforce cleaner code and more stable APIs.) > > Good to know. I was just a bit confused with the manpages that say > they're optional after I discovered looking at the driver that they're > hardwired in. I plan on fleshing out the driver documentation in the Wiki a little more. Like everything, all I need is time. :) >> If you're seeing issues like the above, chances are that you're seeing >> some corruption. Can you please print out the whole value of *rs (ie, >> all the fields of the ath_rx_status struct) so I can see how valid it >> is? > > Sure: > > (kgdb) p *rs > $1 =3D {rs_datalen =3D 244, rs_status =3D 0 '\0', rs_phyerr =3D 0 '\0', > rs_rssi =3D 0 '\0', rs_keyix =3D 127 '\177', rs_rate =3D 27 '\033', rs_mo= re > =3D 0 '\0', rs_tstamp =3D 2097280, rs_antenna =3D 8399232, rs_rssi_ctl = =3D > "0\200)", rs_rssi_ext =3D "\200\000\037", rs_isaggr =3D 1 '\001', > rs_moreaggr =3D 1 '\001', rs_num_delims =3D 0 '\0', rs_flags =3D 252 '=FC= ', > rs_evm0 =3D 0, rs_evm1 =3D 0, rs_evm2 =3D 0, rs_evm3 =3D 0, rs_evm4 =3D 0= } It doesn't look like garbage to begin with .. and then it does. How have you compiled it? Some of those fields are currently optional (ie, require the AR5416 (11n) support to be enabled) - have you somehow managed to compile part of the code with it, part of the code without it? Which NIC is this for again? AR9285? Adrian