From owner-freebsd-current@FreeBSD.ORG Mon Aug 29 00:42:20 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 F36B4106564A; Mon, 29 Aug 2011 00:42:19 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 9CB9D8FC0A; Mon, 29 Aug 2011 00:42:19 +0000 (UTC) Received: by qyk4 with SMTP id 4so1530319qyk.13 for ; Sun, 28 Aug 2011 17:42:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rQ92J2TmoCOzJ1KsYH9XKKF11tmJHTKV80AmkaKFtgk=; b=mRKb3Q4iELui4vv7q9vMZCTQtlk5XE7bVAx4l5QdpL4ZPHDIB+93JkXCdIt+9gfIK1 sK7IEncJ9zwn4xLf65H8iRzM69FirK+h9wc/LMdmis2xZ9+RTzRFsc+JS0bhdycXjZci 3/Ib7eL0wZMiZ+GeggjiJ5IejpKJC1jYK1hW8= MIME-Version: 1.0 Received: by 10.224.214.9 with SMTP id gy9mr885284qab.79.1314578538762; Sun, 28 Aug 2011 17:42:18 -0700 (PDT) Received: by 10.224.19.131 with HTTP; Sun, 28 Aug 2011 17:42:18 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Aug 2011 17:42:18 -0700 Message-ID: From: Garrett Cooper To: Adrian Chadd 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:42:20 -0000 On Sun, Aug 28, 2011 at 5:21 PM, Adrian Chadd wrote: > 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_m= ore >> =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? Just options ATH_DEBUG in my $KERNCONF and I built the ath and ath_pci modules. > Which NIC is this for again? AR9285? Yup: ath0@pci0:2:0:0: class=3D0x028000 card=3D0x10891a3b chip=3D0x002b168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR9285 Wireless Network Adapter (PCI-Express)' class =3D network Thanks! -Garrett