From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 18 05:02:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDB28C12 for ; Sun, 18 Nov 2012 05:02:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 97DDA8FC08 for ; Sun, 18 Nov 2012 05:02:53 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1808061dad.13 for ; Sat, 17 Nov 2012 21:02:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CiDmjZtAF0ZIyNqbVC2I47jEyD2u3KeqmdfWO/KL/Bo=; b=TOh8F3uHIwWzcYUlQJIkAB11KfTdRNlhQRPwGV5F1iaEmcnEU0io6Y99kI+m/O6or7 AEmu6WMSfuYQuZguZM93A7OGvQkJNjGjF/v5dT9Jf/237ija/bbjj5IPY17gcCXRZ4Bp yKklO05DyeM92p+xswjbgja4yP6rA8aSdUOstrdEs/fHO1eWVNYM9KMS+2SFS+UEsZSu ZvHtEnRkGgPXzQmu3YCR7CgD6E0/QjFdZhpfSYMEE8SNYV8ihHN56QKxnkKIcro4hMec aXdqIYS7UAbCF2+Jsb0xZBUca0nV7nhzqsqLjLuFd2s3n0TZHvLTJcInPYPnUEJ1Pyxs Vi/Q== MIME-Version: 1.0 Received: by 10.69.0.8 with SMTP id au8mr29393685pbd.58.1353214973050; Sat, 17 Nov 2012 21:02:53 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sat, 17 Nov 2012 21:02:53 -0800 (PST) In-Reply-To: <50A86AB6.3050502@gmail.com> References: <50A49138.3080700@gmail.com> <50A52547.6030402@gmail.com> <50A86AB6.3050502@gmail.com> Date: Sat, 17 Nov 2012 21:02:53 -0800 X-Google-Sender-Auth: zqrXhriMAK5QNHo0yQn4dqfky4c Message-ID: Subject: Re: Today's wireless update - TL;DR - please test -HEAD 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, 18 Nov 2012 05:02:53 -0000 Yup, there's no AR9300 HAL support yet in the tree, sorry. If I could commit it right now I would. :) Adrian On 17 November 2012 20:57, Joshua Isom wrote: > On 11/15/2012 11:41 AM, Adrian Chadd wrote: >> >> On 15 November 2012 09:24, Joshua Isom wrote: >> >> >>> So I'm taking it that currently it will not work without the glue that's >>> not >>> yet available? >>> >>> I'm trying to get ndis working, but it's failing to find the device. I >>> can >>> run pciconf -lv and it shows that it's connected. >> >> >> The glue is available. The HAL isn't available. That's the missing piece. >> >> As for NDIS, I haven't ever played with that. Sorry. I'm trying to >> make the drivers support everything so we don't need NDIS. >> >> What's the PCI ID of the chip you're using, and which driver are you >> trying to use with NDIS? >> >> >> Adrian >> > > I tried doing a mix of ath from -current and the rest from -stable but it > wouldn't compile because of iwn and other issues. I tried doing a -current > generic kernel. It would kernel panic shortly after getty was started but I > think that's another issue. After I got it to not panic, the ath driver > still wouldn't attach. Here's the relevant output of pciconf. > > none3@pci0:2:0:0: class=0x028000 card=0x3112168c chip=0x0030168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR9300 Wireless LAN adaptor' > class = network > > I was trying drivers off the CD I was given by the vendor. The card is a > TP-LINK TL-WDN4800. I tried the XP and Vista drivers, athwx.sys and > athrx.sys, but neither had any effect. > >