From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 17 21:40:09 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 4A384AA0 for ; Sun, 17 Mar 2013 21:40:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by mx1.freebsd.org (Postfix) with ESMTP id CE9DC38B for ; Sun, 17 Mar 2013 21:40:08 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id e12so4207034wge.22 for ; Sun, 17 Mar 2013 14:40:02 -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=UQ1/fsIvLaEATTw6N4PP6rOSM6IRsFosCeCQmyv9uOw=; b=RCpxHx2Ye7DZSp1JFiLhep/UkNqLJ6rEkirSXjv/g7lHiAu3HeG1588SKuZdplbbdr cnH5fFBtcikkf5khGgU3VyCa3zxEa9hfXrp74fzSWCshACtQ6XSz2AxM04ETLylnWaBi 7CxGHk/xIaPYG5bmkz+UinRhfANmYbGktHEhjO34KVv1a+/o0zXATvHvT1SIKZOyh0WT IOgq0IJaog7pq+u4VaQ/k6zm7faOKpLu3RaxHVBbob7E2HuRzVhF5cvDO9EvD5kh2P1p OH6tnSLnov4mqhzfuOiTUXRRovkmPZnDxgL+b5S76qOXML6u9T50jO3RDqg+744i2v9f 3cig== MIME-Version: 1.0 X-Received: by 10.194.237.129 with SMTP id vc1mr20803053wjc.20.1363556402215; Sun, 17 Mar 2013 14:40:02 -0700 (PDT) Received: by 10.216.111.201 with HTTP; Sun, 17 Mar 2013 14:40:01 -0700 (PDT) In-Reply-To: <514633FF.6070108@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> <514633FF.6070108@gmail.com> Date: Sun, 17 Mar 2013 14:40:01 -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 21:40:09 -0000 Just go to my github - github.com/erikarn/ - then click on repositories, then the HAL fork, then just file an issue there. Adrian On 17 March 2013 14:22, Joshua Isom wrote: > 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 >> >