From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 17 00:25:32 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 7ECB9EA5 for ; Sun, 17 Mar 2013 00:25:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD1B9B6 for ; Sun, 17 Mar 2013 00:25:32 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id r11so501428pdi.20 for ; Sat, 16 Mar 2013 17:25:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ipOdG0H6pmqtUB+SvEeiim4goGEtKDAj7zZiRVN/MLg=; b=jOL/i3s40WF3AeqP6BFyUh2oY2VVeI9/jd26Jy2qv7JX1bY7DkJxBrZ1SIioSqS1/3 J3/eUmRKGL6L+92vi94Vt2zf5X9Ov26dOgwhg9iGs7QMFQDsuMmrRv+ZgKY3q7CsakBj h6heNwUoy3ISTIg4JB2DRRFB2VBAMWYY4tthnoqRAlPO9+FezYOFuL/7KQMqEXRuhU2C PvNermF6EwhQJH6zIQB2AS7isWU7Bg0i+GcbFz5weY9S06nBloR2R1QwFuke4gBv1Mi5 MSwm0RTlsbkctEHlEQkn6vBZLO1yW5wECw29swcqMYX1FOAaNw+gf0iwcVuCsEUcRvRD 98lQ== MIME-Version: 1.0 X-Received: by 10.68.143.106 with SMTP id sd10mr11562708pbb.50.1363479926046; Sat, 16 Mar 2013 17:25:26 -0700 (PDT) Received: by 10.70.39.69 with HTTP; Sat, 16 Mar 2013 17:25:25 -0700 (PDT) In-Reply-To: <5143A1C3.7010304@gmail.com> 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> Date: Sat, 16 Mar 2013 17:25:25 -0700 Message-ID: Subject: Re: Fine, OK, here's my initial AR9380/AR9485 support From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 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 00:25:32 -0000 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