From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 17 21:22:14 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 971176FA for ; Sun, 17 Mar 2013 21:22:14 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ia0-x22c.google.com (mail-ia0-x22c.google.com [IPv6:2607:f8b0:4001:c02::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 62E492DF for ; Sun, 17 Mar 2013 21:22:14 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id l29so4751154iag.31 for ; Sun, 17 Mar 2013 14:22:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+22OUyQnYnGi3JzHk0jG5LGyAao6QXe/hhO4d1jCqK4=; b=mH40tFCG2AWeuil1HcIB0G8pO9uIvyUGPyxsZmO5m9CDTmVGajjb7VW/su/IdafK0R bvW2+UuNZeX935VeQXIn09eTCKWR3uFjLEjR361l5DUI1nZGGfrp0PmRuC5RgL8KcXj+ SHf0zPpM43hdNU/tSTpd2vlltMW/NtuQdaxIqFqzsagdYAtrLzN0Ld2hNzT/xB6gn18j IsYSMxKmuA5jJxDsGK7DhTh+WHpzU7iA2Ux0BDbzdqpQTqmg3zLdV37OrTyWbRYmGEdm Xwc8j2AYcFA3oa85fk4KvqkBELg5j/Ow5IPdrG7PQuZJol5XlnPUyoqwEIgX/6OZ1swb KinA== X-Received: by 10.50.187.225 with SMTP id fv1mr5210186igc.74.1363555334160; Sun, 17 Mar 2013 14:22:14 -0700 (PDT) Received: from [192.168.1.14] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id ih1sm6917869igc.3.2013.03.17.14.22.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Mar 2013 14:22:13 -0700 (PDT) Message-ID: <514633FF.6070108@gmail.com> Date: Sun, 17 Mar 2013 16:22:07 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Fine, OK, here's my initial AR9380/AR9485 support References: <5142813d.83c2e00a.67a8.39d5@mx.google.com> <514284E5.9060303@gmail.com> <51428E10.1000801@gmail.com> <78975985-a190-4915-82b5-b1810d6115b2@email.android.com> <5143A1C3.7010304@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 21:22:14 -0000 How do you file a bug report against the fork? On 3/16/2013 7:25 PM, Adrian Chadd wrote: > On 15 March 2013 15:33, Joshua Isom wrote: > >>> ar9300_set_stub_functions: setting stub functions >>> ar9300_set_stub_functions: setting stub functions >>> ar9300_attach: calling ar9300_hw_attach >>> ar9300_hw_attach: calling ar9300_eeprom_attach >>> ar9300_flash_map: unimplemented for now >>> Restoring Cal data from DRAM >>> Restoring Cal data from EEPROM >>> ar9300_hw_attach: ar9300_eeprom_attach returned 0 >>> ath0: RX status length: 48 >>> ath0: RX buffer size: 4096 >>> ath0: TX descriptor length: 128 >>> ath0: TX status length: 36 >>> ath0: TX buffers per descriptor: 4 >>> ar9300_freebsd_setup_x_tx_desc: called, 0x0/0, 0x0/0, 0x0/0 > > .. I really should remove that, but. > >>> ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries >>> ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries >>> ath0: [HT] enabling HT modes >>> ath0: [HT] enabling short-GI in 20MHz mode >>> ath0: [HT] 1 stream STBC receive enabled >>> ath0: [HT] 1 stream STBC transmit enabled >>> ath0: [HT] 3 RX streams; 3 TX streams >>> ath0: AR9380 mac 448.3 RF5110 phy 0.0 > > Cool, normal AR9380. Nothing fancy. > >>> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 > >>> ar9300_Stub_GetSlotTime: called >>> ar9300_Stub_GetSlotTime: called >>> ar9300_Stub_GetCTSTimeout: called >>> ar9300_Stub_GetCTSTimeout: called >>> ar9300_Stub_GetAntennaSwitch: called >>> ar9300_Stub_GetAntennaSwitch: called > > Ok. I should implement those stub routines in the driver. Can you file > a bug report (against my fork, not the qca tree) with the above stubs? > That way I don't forget. > > I wonder why you see them and I don't. Or do I just never check dmesg. > >>> wlan0: Ethernet address: 64:70:02:18:6d:95 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 > > This is well known. For some odd reason I get a RXEOL interrupt when I > initialise the RX FIFO. I don't know why yet. It's harmless but I'd > like to figure out why. > >>> ar9300_reset[4254]: ar9300_stop_dma_receive failed > > Likely another channel scan, maybe? Or maybe it finally associated? > >>> ath0: ath_edma_recv_proc_queue: handled npkts 0 ngood 0 > > Thanks for being patient so far! > > > > Adrian >