From owner-freebsd-drivers@FreeBSD.ORG Tue Feb 17 07:14:07 2009 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2355F1065673 for ; Tue, 17 Feb 2009 07:14:07 +0000 (UTC) (envelope-from gibblertron@gmail.com) Received: from mail-bw0-f170.google.com (mail-bw0-f170.google.com [209.85.218.170]) by mx1.freebsd.org (Postfix) with ESMTP id 7CE198FC18 for ; Tue, 17 Feb 2009 07:14:06 +0000 (UTC) (envelope-from gibblertron@gmail.com) Received: by bwz18 with SMTP id 18so4550775bwz.19 for ; Mon, 16 Feb 2009 23:14:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=esy3ZlTj9hdWAqEAbZWJouu4El4bLjbhnq8OY8P6at0=; b=rerLpeHEpt+X84P1zYBzFpwhnMFXTKQQBR9lurl4lGW0XuG3htZwrhUovj0JQKA4Wd Ug+aQVr4hppHF9/F+Y9HjKvCa3OH84mImw0PclHCFKQiQ8vbpClhsWS4yaVL9tZeFQNh SP8ijCFxLMxl8mxjQbvnfX9IAZATcWFkR4uiU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=hpO9jGusVHtG3MquPY7sfFpgvXYBJAiv5f2OVjfTTcd20gqpe87uXD1FYIut1Jck/t h9oz58wxeo+ADprRAqQzT95LJOQT0uxPEEE0Jh3/4ADw4hdigm0iB5+L9Gjq4m8B8wIO M59ilk+gEsvdBtspoABkfeDMs3NqR2zCRGvPQ= MIME-Version: 1.0 Received: by 10.181.154.16 with SMTP id g16mr330313bko.179.1234853031164; Mon, 16 Feb 2009 22:43:51 -0800 (PST) Date: Mon, 16 Feb 2009 22:43:51 -0800 Message-ID: From: patrick To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Porting a 5.3 USB WLAN driver to 7.1 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 07:14:07 -0000 I'm doing my best to port a driver (atuwi) for a Linksys WUSB11v2.8 driver that was written for FreeBSD 5.x to 7.1, but as I'm not a kernel hacker by any means, I'm having a few problems. I've managed to update Daan Vreeken's atuwi so that it compiles and loads, but I haven't yet got it to connect to my wireless network. When I load driver, I get a couple warnings: atuwi0: WARNING: using obsoleted if_watchdog interface atuwi0: WARNING: using obsoleted IFF_NEEDSGIANT flag I've Googled both messages, but haven't found any discussion on when these were obsoleted and what you're supposed to do instead. My ifconfig status shows up as: atuwi0: flags=108802 metric 0 mtu 1500 ether 00:0c:41:5a:48:5f inet 10.0.42.223 netmask 0xffffff00 broadcast 10.0.42.255 maclabel ?biba,?lomac,?mls,?sebsd media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier vlan: 0 parent interface: ifconfig: unable to get channel information ssid "Air Mousey" I notice that "status" shows up as "no carrier", and I'm not sure what exactly that means and why it's unable to get any "channel information". I also notice question marks in the "maclabel" line, and I suspect that might be indicative of a problem. My biggest problem is that I can't find any documentation on the "right" way to structure such a driver. I've looked at other if_xxxx drivers in the usb/ folder, but each does its thing in its own way. Both OpenBSD and NetBSD adopted Daan's atuwi driver and have had it running for a while, but unfortunately no one in the FreeBSD world took it on. If anyone has any insight or can point me in the right direction, I'd be greatly appreciative. Thanks, Patrick From owner-freebsd-drivers@FreeBSD.ORG Sat Feb 21 20:37:21 2009 Return-Path: Delivered-To: drivers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F7861065672 for ; Sat, 21 Feb 2009 20:37:21 +0000 (UTC) (envelope-from huntting@glarp.com) Received: from wotan.mcwest.org (wotan.mcwest.org [63.231.80.19]) by mx1.freebsd.org (Postfix) with ESMTP id D1A198FC18 for ; Sat, 21 Feb 2009 20:37:20 +0000 (UTC) (envelope-from huntting@glarp.com) Received: from antediluvian.glarp.com (71-212-209-203.hlrn.qwest.net [71.212.209.203]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by wotan.mcwest.org (Postfix) with ESMTPSA id 3584FD4C1C for ; Sat, 21 Feb 2009 13:18:00 -0700 (MST) Received: from lugubrious.glarp.com (lugubrious.glarp.com [10.0.0.245]) by antediluvian.glarp.com (8.14.3/8.14.3) with ESMTP id n1LKHKxQ024105; Sat, 21 Feb 2009 13:17:21 -0700 (MST) (envelope-from huntting@glarp.com) Received: from huntting (helo=lugubrious.glarp.com) by lugubrious.glarp.com with local-esmtp (Exim 4.69) (envelope-from ) id 1LayI1-0004d6-7m; Sat, 21 Feb 2009 13:17:33 -0700 To: drivers@FreeBSD.org From: Brad Huntting Date: Sat, 21 Feb 2009 13:17:33 -0700 Sender: huntting@glarp.com Message-Id: Cc: Subject: kernel gdb over Ethernet X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2009 20:37:21 -0000 I'm thinking about how to implement gdb over Ethernet (or UDP or TCP). I know this has been considered in the past by several different people, and it's even been implemented in Linux (which makes the gdb(1) end simpler). My idea was to create a netgraph node that can act as a gdb stub. Then poll the network interface(s) from the gdb_getc() loop to read data. But, before I go much further, has this already been implemented somewhere and I'm just not finding it? brad