From owner-freebsd-drivers@FreeBSD.ORG Mon Dec 10 20:13:14 2007 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 97D4416A421 for ; Mon, 10 Dec 2007 20:13:14 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 643A813C45D for ; Mon, 10 Dec 2007 20:13:13 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: (qmail invoked by alias); 10 Dec 2007 19:46:29 -0000 Received: from p54ADA9C0.dip0.t-ipconnect.de (EHLO apog-desktop.local) [84.173.169.192] by mail.gmx.net (mp043) with SMTP; 10 Dec 2007 20:46:29 +0100 X-Authenticated: #14602519 X-Provags-ID: V01U2FsdGVkX19C43IUOMBCW071nH/JOh+Ng0M+S2Viv2KnkX2EHq FRoi0ZkePfBzfZ From: Alexander Pohoyda To: freebsd-drivers@freebsd.org Date: Mon, 10 Dec 2007 20:46:27 +0100 User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_TeZXHiZGIa5ibMK" Message-Id: <200712102046.27504.alexander.pohoyda@gmx.net> X-Y-GMX-Trusted: 0 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: SiS 190 NIC driver 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: Mon, 10 Dec 2007 20:13:14 -0000 --Boundary-00=_TeZXHiZGIa5ibMK Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello! Attached is a driver for the SiS 190 NIC found in some Shuttle XPS boxes. I have developed it based on the code of SiS 900 BSD driver using hints and enums from Linux and Solaris drivers. It is developed and tested to be working on FreeBSD 5.4 amd64. Please bear in mind that this is my first driver ever. The driver surely needs some corrections and more work (collision handling, polling mode, etc) but I'm not able to do this right now becasue of the missing documentation. Please review the code and add it into the source with any corrections you dimi necessary. Thank you! With best regards, Alexander Pohoyda --Boundary-00=_TeZXHiZGIa5ibMK-- From owner-freebsd-drivers@FreeBSD.ORG Mon Dec 10 20:55:02 2007 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 10EA416A41B for ; Mon, 10 Dec 2007 20:55:02 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 9F74F13C459 for ; Mon, 10 Dec 2007 20:55:01 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: (qmail 6895 invoked by uid 0); 10 Dec 2007 20:55:00 -0000 Received: from 84.173.169.192 by www097.gmx.net with HTTP; Mon, 10 Dec 2007 21:55:00 +0100 (CET) Content-Type: text/plain; charset="us-ascii" Date: Mon, 10 Dec 2007 21:55:00 +0100 From: "Alexander Pohoyda" Message-ID: <20071210205500.161240@gmx.net> MIME-Version: 1.0 To: freebsd-drivers@freebsd.org X-Authenticated: #14602519 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19smscM0x5svq5xhT0yolbLeOxVN/o1jKoI3TVjyh c1nrFcyfDjrMoeOcTXZpVdjNKIzZVVigqx6Q== Content-Transfer-Encoding: 7bit X-GMX-UID: lp5uf8kKMmA6cXy9tWFn8hU5MjQ1N13v Subject: Re: SiS 190 NIC driver 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: Mon, 10 Dec 2007 20:55:02 -0000 Sorry guys, the attachment didn't come thru. Here it is once again: -- Alexander Pohoyda PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44 From owner-freebsd-drivers@FreeBSD.ORG Tue Dec 11 01:56:35 2007 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 2AAFE16A420 for ; Tue, 11 Dec 2007 01:56:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.freebsd.org (Postfix) with ESMTP id AC20813C448 for ; Tue, 11 Dec 2007 01:56:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so701121pyb for ; Mon, 10 Dec 2007 17:56:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=NhwIwMfMGMM8yvggpRrjC5O4lUmqiBUAhqHfchwL/tA=; b=C/zhtA96+X1uSL/N6z8oHWByuEW+0XuQbFKyB0RIRapfRdIbnjw0x6TldZMqrLoXnZfeB+Gt7uCanl0ihMyXRIfnRmZR5c4WMrsrvHJBdf4hDTfLh/airjojBBoJ8SdThczPLD1oiatrno+Vkn+9xe0vKOOXbXuipRJyiOCn32E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=nDEiAQW3EmA56bq6CcF0IV78+04UUOQxcR3qa55HEWAcATrGQg8+42O1CCbhovl/3tfniRqq/tNSUyyrOus8/PRVsz7nTM31u+zIO2qN1tk1F8ig+bwjBE1aWHNlTqE8jBC7YDLXlBCt5XMKV+acx/cpsbWKZdZbL3qT5JKtotE= Received: by 10.65.40.16 with SMTP id s16mr15491182qbj.1197336647850; Mon, 10 Dec 2007 17:30:47 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id 7sm1121267nzn.2007.12.10.17.30.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 10 Dec 2007 17:30:46 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lBB1RCnN064672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Dec 2007 10:27:12 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lBB1RBAn064671; Tue, 11 Dec 2007 10:27:11 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 11 Dec 2007 10:27:11 +0900 From: Pyun YongHyeon To: Alexander Pohoyda Message-ID: <20071211012711.GB64299@cdnetworks.co.kr> References: <200712102046.27504.alexander.pohoyda@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200712102046.27504.alexander.pohoyda@gmx.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-drivers@freebsd.org Subject: Re: SiS 190 NIC driver X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2007 01:56:35 -0000 On Mon, Dec 10, 2007 at 08:46:27PM +0100, Alexander Pohoyda wrote: > Hello! > > Attached is a driver for the SiS 190 NIC found in some Shuttle XPS boxes. I > have developed it based on the code of SiS 900 BSD driver using hints and > enums from Linux and Solaris drivers. > > It is developed and tested to be working on FreeBSD 5.4 amd64. Please bear in > mind that this is my first driver ever. The driver surely needs some > corrections and more work (collision handling, polling mode, etc) but I'm not > able to do this right now becasue of the missing documentation. > > Please review the code and add it into the source with any corrections you > dimi necessary. > > Thank you! > Great work! I've looked over the driver code and I guess the driver is not for RELENG_6/RELENG_7/CURRENT. Would you make it work for CURRENT? Some conmments: - I guess SiS 190 is a gigabit controller but the probe message just shows 10/100TX message. Does this driver supports 1Gbps? - The usage of bus_dma(9) KPI seems to be incorrect. For example there should be no reason to set BUS_DMA_ALLOCNOW flag in bus_dma_tag_create. You can also use bus_dmamap_load_mbuf_sg(9) for newer FreeBSD which make it possible to remove book-keepings needed to pass/get to/from callback. Please check other network drivers for correct usage of bus_dma(9). - It seems that Tx/Rx ring have alignment restrictions, probably 16 bytes or larger. Would you please check it? - Descriptor counter 64 seems to be small for gigabit controllers. I guess 256 or higher would be more reasonable one. - I'm not sure SiS 190 can't handle DMA gathering in Tx path but it seems that Linux doesn't use multiple Tx descriptors at all in Tx path(NETIF_F_SG flag is absent in Linux) So I guess you can simplify sis_encap() function. - It seems the driver name sis19x looks odd. How about sge(SiS Gigabit Ethernet)? - Missing Makefile and man page. - style(9) cleanup. I don't have SiS 190 hardware to test the driver. So it's hard for me to make it work on CURRENT. Feel free to contact to me if you have any questions. -- Regards, Pyun YongHyeon From owner-freebsd-drivers@FreeBSD.ORG Tue Dec 11 07:45:11 2007 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 AAACF16A418 for ; Tue, 11 Dec 2007 07:45:11 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 1BC4613C4F3 for ; Tue, 11 Dec 2007 07:45:10 +0000 (UTC) (envelope-from alexander.pohoyda@gmx.net) Received: (qmail 1332 invoked by uid 0); 11 Dec 2007 07:45:09 -0000 Received: from 155.56.68.221 by www119.gmx.net with HTTP; Tue, 11 Dec 2007 08:45:09 +0100 (CET) Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Dec 2007 08:45:09 +0100 From: "Alexander Pohoyda" In-Reply-To: <20071211012711.GB64299@cdnetworks.co.kr> Message-ID: <20071211074509.281710@gmx.net> MIME-Version: 1.0 References: <200712102046.27504.alexander.pohoyda@gmx.net> <20071211012711.GB64299@cdnetworks.co.kr> To: freebsd-drivers@freebsd.org X-Authenticated: #14602519 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX18cxgQ4aBccFqn4HBktdOvr6wc35JDXi4YjRnb6Pf FdhT5hFy1GSM0qu41jIBJN54EoHbrVsWdbuQ== Content-Transfer-Encoding: 7bit X-GMX-UID: PXdtc0kcf2IsDUC4smxo2DB4dWxlcxYQ Subject: Re: SiS 190 NIC driver 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, 11 Dec 2007 07:45:11 -0000 > > Attached is a driver for the SiS 190 NIC found in some Shuttle XPS > I've looked over the driver code and I guess the driver is not > for RELENG_6/RELENG_7/CURRENT. Would you make it work for CURRENT? I would like to, but neither RELENG_6, nor RELENG_7 boots on my Shuttle box. I have reported this in -current mailing list some time ago, but got no usable suggestion. Maybe I should try a recent CURRENT, but I don't have much time to play around with it. > - I guess SiS 190 is a gigabit controller but the probe message just > shows 10/100TX message. Does this driver supports 1Gbps? I don't know for sure, but SiS website mentions: SiS191 Gigabit LAN & SiS190 LAN Driver(v2.03) Other websites have it wrong, I guess, e.g.: SiS 190 Gigabit LAN & SiS 191 LAN Driver v 1.03b However, I will have a look at this. > - The usage of bus_dma(9) KPI seems to be incorrect. For example > there should be no reason to set BUS_DMA_ALLOCNOW flag in > bus_dma_tag_create. This code is left from the original sis driver and it works. Moreover, the Architecture Handbook does not mention bus_dmamap_load_mbuf_sg(9) and once again, newer FreeBSD releases do not start on this box at all, so if this new bus_dma API is not available in RELENG_5, I cannot use it. > needed to pass/get to/from callback. Please check other network > drivers for correct usage of bus_dma(9). The existing sis driver does no use bus_dmamap_load_mbuf_sg either. > - It seems that Tx/Rx ring have alignment restrictions, probably > 16 bytes or larger. Would you please check it? I do not understand, please elaborate. > - Descriptor counter 64 seems to be small for gigabit controllers. > I guess 256 or higher would be more reasonable one. Do you mean that: int sis_tx_cnt; should rather be: u_int256_t sis_tx_cnt; If not, please elaborate. > - I'm not sure SiS 190 can't handle DMA gathering in Tx path but > it seems that Linux doesn't use multiple Tx descriptors at all > in Tx path(NETIF_F_SG flag is absent in Linux) So I guess you can > simplify sis_encap() function. Please offer your version of a function and I will test it. Or explain how you mean to simplify it. Is there an existing driver with a simplified variant? > - It seems the driver name sis19x looks odd. How about sge(SiS > Gigabit Ethernet)? Yes, I would like sge better, but see above. > - Missing Makefile and man page. Sorry, cannot provide a man page other than a standard sis(4), but a Makefile is not a problem, will do. > - style(9) cleanup. I tried to stick to style(9), do you have any specific complaints? > I don't have SiS 190 hardware to test the driver. So it's hard for me > to make it work on CURRENT. Feel free to contact to me if you have > any questions. Thank you very much for useful comments! Please send me code snippets and I will test them! -- Alexander Pohoyda PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44 From owner-freebsd-drivers@FreeBSD.ORG Wed Dec 12 03:45:10 2007 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 253CE16A47C for ; Wed, 12 Dec 2007 03:45:10 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id E73C413C45D for ; Wed, 12 Dec 2007 03:45:09 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so129157waf.3 for ; Tue, 11 Dec 2007 19:45:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=NXWJgODyFaSxZo4esmoZIltJ+juOJROHYxi8kI+enxs=; b=g5j4v20TcsTQfR+X6RkxCcrulTQEte8FDROfxDMYc5vKp9fT5Pual9s1kZiqpbPGG+KukjXcvD9tclYepBTHpAs86yMMmwGtQbTyx5uIYcwUPnNv2aPmM76+OfseucPGqrfJq00wv+IAN9+9kdRgysDfJOh8YP4Ul/Jb19P3TtA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=B1WvsXqk15v4ua0AI8qQhl5ySaZY1pW5UfDKF+yplUu693z283mdmJaNTDyvuwDpdMAP2zRLTbaT5Wcr7qvSe/9cls3j8g7yDu6miPPD54R5cQPIKsLujqWDsbOX98F0qByhI6IyJ6xMiGsLJVL4kKNtsGzntW3+sgOUbxrxToc= Received: by 10.115.33.1 with SMTP id l1mr243307waj.17.1197431108555; Tue, 11 Dec 2007 19:45:08 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id j6sm1705273wah.2007.12.11.19.45.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Dec 2007 19:45:07 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lBC3fGTk069076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Dec 2007 12:41:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lBC3fElX069075; Wed, 12 Dec 2007 12:41:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 12 Dec 2007 12:41:14 +0900 From: Pyun YongHyeon To: Alexander Pohoyda Message-ID: <20071212034114.GB68410@cdnetworks.co.kr> References: <200712102046.27504.alexander.pohoyda@gmx.net> <20071211012711.GB64299@cdnetworks.co.kr> <20071211074509.281710@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071211074509.281710@gmx.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-drivers@freebsd.org Subject: Re: SiS 190 NIC driver X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2007 03:45:10 -0000 On Tue, Dec 11, 2007 at 08:45:09AM +0100, Alexander Pohoyda wrote: > > > Attached is a driver for the SiS 190 NIC found in some Shuttle XPS > > > I've looked over the driver code and I guess the driver is not > > for RELENG_6/RELENG_7/CURRENT. Would you make it work for CURRENT? > > I would like to, but neither RELENG_6, nor RELENG_7 boots on my Shuttle box. I have reported this in -current mailing list some time ago, but got no usable suggestion. Maybe I should try a recent CURRENT, but I don't have much time to play around with it. Maybe sumbit a PR for this? > > > > - I guess SiS 190 is a gigabit controller but the probe message just > > shows 10/100TX message. Does this driver supports 1Gbps? > > I don't know for sure, but SiS website mentions: SiS191 Gigabit LAN & SiS190 LAN Driver(v2.03) > > Other websites have it wrong, I guess, e.g.: SiS 190 Gigabit LAN & SiS 191 LAN Driver v 1.03b > > However, I will have a look at this. Thanks. > > > > - The usage of bus_dma(9) KPI seems to be incorrect. For example > > there should be no reason to set BUS_DMA_ALLOCNOW flag in > > bus_dma_tag_create. > > This code is left from the original sis driver and it works. Moreover, the Architecture Handbook does not mention bus_dmamap_load_mbuf_sg(9) and once again, newer FreeBSD releases do not start on this box at all, so if this new bus_dma API is not available in RELENG_5, I cannot use it. I don't think sis(4) is the best example for bus_dma(9) usage. If it was it would have worked on sparc64. Check otherdrivers that runs without problems on !i386 architecture. And yes, the Handbook needs updating. See bus_dma(9) man page. > > > > needed to pass/get to/from callback. Please check other network > > drivers for correct usage of bus_dma(9). > > The existing sis driver does no use bus_dmamap_load_mbuf_sg either. > > > > - It seems that Tx/Rx ring have alignment restrictions, probably > > 16 bytes or larger. Would you please check it? > > I do not understand, please elaborate. > For example, you seem to use alignemnet 1 in dma tags for Tx ring. 796 /* TX */ 797 error = bus_dma_tag_create(sc->sis_parent_tag, /* parent */ 798 1, 0, /* alignment, boundary */ ^^^ 799 BUS_SPACE_MAXADDR, /* lowaddr */ 800 BUS_SPACE_MAXADDR, /* highaddr */ 801 NULL, NULL, /* filter, filterarg */ 802 SIS_TX_RING_SZ, 1, /* maxsize,nsegments */ 803 BUS_SPACE_MAXSIZE_32BIT, /* maxsegsize */ 804 0, /* flags */ 805 busdma_lock_mutex, /* lockfunc */ 806 &Giant, /* lockarg */ 807 &ld->sis_tx_tag); I guess the the alignment would be sizeof(struct sis19x_desc) at least, i.e. 16 bytes. Normally ethernet controllers may have more larger alignment limitation than its single descriptor size(e.g. 256 bytes). You seems to use m_devget(9) for !386 to align recevied frames in sis_rxeof(). This clearly indicates it needs Rx buffer alignment limitation. In addition, you seem to use the same dma tag for Tx/Rx dma maps. Becasue most hardwares supports multi-fragmented frames in Tx side, total Tx DMA segment size would be larger than Rx DMA segment size. For Rx side, most hardwares just support 1 DMA segment, so it's maximum DMA segment size would be MCLBYTES. > > > - Descriptor counter 64 seems to be small for gigabit controllers. > > I guess 256 or higher would be more reasonable one. > > Do you mean that: > int sis_tx_cnt; > should rather be: > u_int256_t sis_tx_cnt; > > If not, please elaborate. > Sorry, I meant the following descriptor counters for Rx/Tx ring. 77 #define SIS_RX_RING_CNT 64 ^^^ 78 #define SIS_TX_RING_CNT 64 ^^^ > > > - I'm not sure SiS 190 can't handle DMA gathering in Tx path but > > it seems that Linux doesn't use multiple Tx descriptors at all > > in Tx path(NETIF_F_SG flag is absent in Linux) So I guess you can > > simplify sis_encap() function. > > Please offer your version of a function and I will test it. Or explain how you mean to simplify it. Is there an existing driver with a simplified variant? > Check vr(4)'s vr_encap, it simply calls m_defrag(9) as Rhine I hardware doesn't support multi-segment dma. > > > - It seems the driver name sis19x looks odd. How about sge(SiS > > Gigabit Ethernet)? > > Yes, I would like sge better, but see above. > > > > - Missing Makefile and man page. > > Sorry, cannot provide a man page other than a standard sis(4), but a Makefile is not a problem, will do. > > > > - style(9) cleanup. > > I tried to stick to style(9), do you have any specific complaints? > 198 Reserved0 = 0x08, // unused ^^^ 199 /* 2007-04-25, Alexander Pohoyda: this register is ^^^^ 200 * automatically set by NIC to the value of TxDescStartAddr 201 * register plus 8 (which, I suppose, is the offset of the 202 * sis_ptr field in sis19x_desc structure). */ ^^^ 203 TxNextDescAddr = 0x0c, // unused // comment, multi-line comment, missing () in return statement etc. > > > I don't have SiS 190 hardware to test the driver. So it's hard for me > > to make it work on CURRENT. Feel free to contact to me if you have > > any questions. > > Thank you very much for useful comments! Please send me code snippets and I will test them! I'm somewhat overloaded for other work so I'm afraid I can't write a code for not-having hardwares. It would be even better if you can check other drivers(bge, em, fxp, gem, msk, nfe, sk, stge etc) in CURRENT. -- Regards, Pyun YongHyeon From owner-freebsd-drivers@FreeBSD.ORG Wed Dec 12 05:41:21 2007 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 3E10E16A417 for ; Wed, 12 Dec 2007 05:41:21 +0000 (UTC) (envelope-from zoup@zoup.org) Received: from elimiz.elimizonline.net (52.19.354a.static.theplanet.com [74.53.25.82]) by mx1.freebsd.org (Postfix) with ESMTP id 1BECB13C468 for ; Wed, 12 Dec 2007 05:41:21 +0000 (UTC) (envelope-from zoup@zoup.org) Received: from [91.184.76.207] (helo=Desktop.DES) by elimiz.elimizonline.net with esmtpa (Exim 4.68) (envelope-from ) id 1J2Jyg-0000a5-Sp for freebsd-drivers@freebsd.org; Wed, 12 Dec 2007 09:17:51 +0400 Date: Wed, 12 Dec 2007 08:47:31 +0330 From: Armin ranjbar To: freebsd-drivers@freebsd.org Message-Id: <20071212084731.90ac80ad.zoup@zoup.org> Organization: Zoup.org X-Mailer: Sylpheed version 2.3.0beta5 (GTK+ 2.8.20; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - elimiz.elimizonline.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - zoup.org X-Source: X-Source-Args: X-Source-Dir: Subject: Broadcom BCM5906M 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: Wed, 12 Dec 2007 05:41:21 -0000 Dear all , anyone get broadcom 5906M ethernet device working under freebsd ? its appear its not supported under if_bge.c . any idea how we can get it working ? -- He was part of my dream, of course -- but then I was part of his dream too. -- Lewis Carroll From owner-freebsd-drivers@FreeBSD.ORG Wed Dec 12 06:32:10 2007 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 EA33316A417 for ; Wed, 12 Dec 2007 06:32:10 +0000 (UTC) (envelope-from rock_on_the_web@hotmail.com) Received: from bay0-omc3-s30.bay0.hotmail.com (bay0-omc3-s30.bay0.hotmail.com [65.54.246.230]) by mx1.freebsd.org (Postfix) with ESMTP id 93C5513C447 for ; Wed, 12 Dec 2007 06:32:10 +0000 (UTC) (envelope-from rock_on_the_web@hotmail.com) Received: from BAY143-W38 ([65.55.154.73]) by bay0-omc3-s30.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Dec 2007 22:20:09 -0800 Message-ID: X-Originating-IP: [202.172.126.254] From: Da Rock To: Date: Wed, 12 Dec 2007 06:20:09 +0000 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 12 Dec 2007 06:20:09.0700 (UTC) FILETIME=[0BD7C240:01C83C87] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: linux cx2388 drivers 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: Wed, 12 Dec 2007 06:32:11 -0000 I think I've bugged the multimedia guys enough with this subject. I have a = tv tuner which I've been trying for over a year to work on FreeBSD, with no= success. I have found out a bundle of info though. =20 Apparently there are manufacturer drivers for the card on Fedora 4, which i= s seriously outdated now, and there is only "experimental" drivers for some= of the latest linux derivatives. =20 The card uses a new conexant cx2388x chipset, a phillips saa7134 chipset, a= nd a zarlink mt352 chipset onboard- mainly because this is a hybrid card. M= any of the new tv tuner cards are using these chipsets, so if it can be wor= ked out then it may resolve the headaches for many users. It would seem tha= t currently none of the new tv tuners are working at all on freebsd. =20 The drivers in all cases use a module and create udev devices. =20 So my question is- how can we adapt these or whatever so that BSD devices a= re made? Where can I find a crash course in making devices? So far what I'v= e read hasn't been making sense, so some clarity would be appreciated. =20 Second, where can I find info to use the linux compat api to port the linux= drivers to bsd? Apparently the reason why newer drivers were not made (fed= ora 3-4 had drivers available) appears to be due to a threading issue (mult= i-thread changes?), so they should work on freebsd if we could adapt the dr= ivers (as far as I understand). =20 I am very new to this- I've been driven to this due to this stupid card iss= ue- so please be gentle :) Any advice and information would be appreciated. =20 Cheers _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=3Dclick&clientID=3D832&r= eferral=3DhotmailtaglineOct07&URL=3Dhttp://music.ninemsn.com.au/roguetrader= s= From owner-freebsd-drivers@FreeBSD.ORG Wed Dec 12 22:22:36 2007 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 E4D2F16A418 for ; Wed, 12 Dec 2007 22:22:36 +0000 (UTC) (envelope-from netslists@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id A081013C465 for ; Wed, 12 Dec 2007 22:22:36 +0000 (UTC) (envelope-from netslists@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so131063anc.13 for ; Wed, 12 Dec 2007 14:22:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=FG1PcRSsLh1EaZSs0tbwRShGxU/HETXgkzJQ+i8VFV0=; b=sJXQuGZ9rJeqYMFf5hUfAYa7f0N/bQSZGR/eVyZuhnFzVyD5sg/AHoLPmSZ36sZ1D4zVENcUG9H67OIXbRCO2M+UZ3G/VxupqXHpU9bhf18ebDIKqDK+H28cIopFsTujOquOMTmEyA8+ftsvQ2M1JvbpxjxvP+3Oq5vzAVALKWU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=fU24hPSTKdBQxETAxLWMRin2NJdNFsoDEcF+oQMcX6xntKXbfiVV24X1WI7tb1xUCp6XsfcfvWcloOq+H7uTkGf1Q4ob2XQ2IfN2+GF1sp8Eg/SAt0evfqad5NBdrg7jGLK9uZ/+TdoK9CQO7lgiulOnc9WrmQwVOYo07tusIn8= Received: by 10.100.215.5 with SMTP id n5mr2568479ang.3.1197496642141; Wed, 12 Dec 2007 13:57:22 -0800 (PST) Received: from ?192.168.12.8? ( [97.101.40.241]) by mx.google.com with ESMTPS id q26sm3493082ele.2007.12.12.13.57.20 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Dec 2007 13:57:21 -0800 (PST) Message-ID: <4760593D.7070203@gmail.com> Date: Wed, 12 Dec 2007 16:57:17 -0500 From: Sten Daniel Soersdal User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Igor Soumenkov <2igosha@gmail.com> References: <472A6708.9030109@clearchain.com> <20071102004248.GA5253@e.0x20.net> <200711020152.53535.max@love2party.net> <472A7ADD.3010002@clearchain.com> <20071104102803.GD5253@e.0x20.net> <20071104105147.GE5253@e.0x20.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) 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: Wed, 12 Dec 2007 22:22:37 -0000 Igor Soumenkov wrote: > But - strange enough - it changes the connection speed frequently > while being 2 meters away from the access point (which is 802.11g). > Right now it is 36 Mbps only. The signal might be too strong. Have seen poor performance and poor TX rate selection under such conditions with other cards. Try sitting between the computer and the AP and investigate power readings. Just my $0.2 -- Sten Daniel Soersdal From owner-freebsd-drivers@FreeBSD.ORG Thu Dec 13 02:53:17 2007 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 2107516A504; Thu, 13 Dec 2007 02:53:17 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net [203.16.214.145]) by mx1.freebsd.org (Postfix) with ESMTP id 6D1F513C448; Thu, 13 Dec 2007 02:53:15 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4HANItYEd5LSgsWmdsb2JhbACBWo4JASA X-IronPort-AV: E=Sophos;i="4.24,160,1196602200"; d="scan'208";a="16344959" Received: from ppp121-45-40-44.lns10.adl2.internode.on.net (HELO mail.clearchain.com) ([121.45.40.44]) by ipmail05.adl2.internode.on.net with ESMTP; 13 Dec 2007 13:23:08 +1030 Received: from benjamin-closes-powerbook-g4-12.local (wcl.ml.unisa.edu.au [130.220.166.5]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lBD2r03p068234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Dec 2007 13:23:08 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <47609F4F.2000109@clearchain.com> Date: Thu, 13 Dec 2007 13:26:15 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Sten Daniel Soersdal References: <472A6708.9030109@clearchain.com> <20071102004248.GA5253@e.0x20.net> <200711020152.53535.max@love2party.net> <472A7ADD.3010002@clearchain.com> <20071104102803.GD5253@e.0x20.net> <20071104105147.GE5253@e.0x20.net> <4760593D.7070203@gmail.com> In-Reply-To: <4760593D.7070203@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Thu, 13 Dec 2007 13:23:08 +1030 (CST) Cc: freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) 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: Thu, 13 Dec 2007 02:53:17 -0000 Sten Daniel Soersdal wrote: > Igor Soumenkov wrote: >> But - strange enough - it changes the connection speed frequently >> while being 2 meters away from the access point (which is 802.11g). >> Right now it is 36 Mbps only. > > The signal might be too strong. Have seen poor performance and poor TX > rate selection under such conditions with other cards. Try sitting > between the computer and the AP and investigate power readings. > Just my $0.2 > Kevin Lo has provided a patch which should fix this issue. I'll apply it shortly. Cheers, Benjamin From owner-freebsd-drivers@FreeBSD.ORG Thu Dec 13 15:43:02 2007 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 A788916A46C; Thu, 13 Dec 2007 15:43:02 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:1f1::2]) by mx1.freebsd.org (Postfix) with ESMTP id E789413C47E; Thu, 13 Dec 2007 15:43:01 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from prawn.unsane.co.uk (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id lBDFgRse023302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Dec 2007 15:42:28 GMT (envelope-from jhary@unsane.co.uk) Message-ID: <476152E9.3090707@unsane.co.uk> Date: Thu, 13 Dec 2007 15:42:33 +0000 From: Vince User-Agent: Thunderbird 2.0.0.9 (X11/20071116) MIME-Version: 1.0 To: Benjamin Close References: <472A6708.9030109@clearchain.com> In-Reply-To: <472A6708.9030109@clearchain.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) 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: Thu, 13 Dec 2007 15:43:02 -0000 Benjamin Close wrote: > Howdy All, I'm pleased to announce the first 'official' > experimental version of the wpi wireless driver and hence require your > help in making it become stable. > Expect a few things not to work (ie bg scanning, setting txpower) but in > general the driver should be usable in station mode (hostap is not yet > supported). > > If you've got an Intel 3945abg wireless card, grab the tarball at: > > > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz > > Untar and follow the instructions in the README. > If you want more info about the driver, or to checkout the FAQ checkout: > > http://www.clearchain.com/wiki/Wpi > > I'm interested in all reports related to panics, things not working as > expected, etc. > The driver still has debug enabled so expect a few messages to be dumped > to the screen whilst in use. > > Finally, many thanks to all those that have been helping debug the > driver along the way. > Thanks for getting this driver going, I'm now using the version in 7.0, Its working very well for me other than one (reasonably minor) thing, which is that "ifconfig wpi0 scan" just sits there until I kill it. the driver works in every other way, associates, works with WEP (havent tried with WPA.) It will find and associate with a network if I just put in "ifconfig wpi0 up" or if i use wpa_supplicant. (jhary@prawn)$uname -a FreeBSD prawn.unsane.co.uk 7.0-BETA4 FreeBSD 7.0-BETA4 #39: Tue Dec 11 12:51:33 GMT 2007 toor@prawn.unsane.co.uk:/usr/local/obj/usr/src/sys/PRAWN7ULE i386 Vince > Cheers, > Benjamin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-drivers@FreeBSD.ORG Thu Dec 13 22:02:01 2007 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 F318316A417 for ; Thu, 13 Dec 2007 22:02:00 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 93FC213C46A for ; Thu, 13 Dec 2007 22:02:00 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 89459 invoked from network); 13 Dec 2007 21:31:38 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@128.238.66.5) by acm.poly.edu with AES256-SHA encrypted SMTP; 13 Dec 2007 21:31:38 -0000 Message-ID: <4761A58F.3070605@acm.poly.edu> Date: Thu, 13 Dec 2007 16:35:11 -0500 From: Boris Kochergin User-Agent: Thunderbird 2.0.0.0 (X11/20070609) MIME-Version: 1.0 To: Benjamin Close References: <472A6708.9030109@clearchain.com> In-Reply-To: <472A6708.9030109@clearchain.com> Content-Type: multipart/mixed; boundary="------------080401030803020405030909" Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) 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: Thu, 13 Dec 2007 22:02:01 -0000 This is a multi-part message in MIME format. --------------080401030803020405030909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Benjamin Close wrote: > Howdy All, I'm pleased to announce the first 'official' > experimental version of the wpi wireless driver and hence require your > help in making it become stable. > Expect a few things not to work (ie bg scanning, setting txpower) but > in general the driver should be usable in station mode (hostap is not > yet supported). > > If you've got an Intel 3945abg wireless card, grab the tarball at: > > > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz > > > Untar and follow the instructions in the README. > If you want more info about the driver, or to checkout the FAQ checkout: > > http://www.clearchain.com/wiki/Wpi > > I'm interested in all reports related to panics, things not working as > expected, etc. > The driver still has debug enabled so expect a few messages to be > dumped to the screen whilst in use. > > Finally, many thanks to all those that have been helping debug the > driver along the way. > > Cheers, > Benjamin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" First, thanks a lot for working on this. I installed 7.0-BETA4/amd64 onto my friend's Dell Inspiron E1505, which has one of these (pciconf says it's a "10418086 Intel 3945ABG Wireless LAN Controller"). With the module built from RELENG_7 sources from a few hours ago, "ifconfig wpi0 up" panics the kernel with (copied by hand): Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff806f6bd2 stack pointer = 0x10:0xffffffffae6ba970 frame pointer = 0x10:0xffffffae6babc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, press 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1108 (wpi taskq) trap number = 12 panic: page fault cpuid = 1 The 20071102-freebsd-wpi.tar.gz tarball behaves the same way, and it also happens on FreeBSD/i386. If it's not a known problem, shall I provide a backtrace? -Boris --------------080401030803020405030909 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz (1828.76-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 2133782528 (2034 MB) avail memory = 2059112448 (1963 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi0: reservation of 0, 9fc00 (3) failed acpi0: reservation of 100000, 7fdd3400 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6130b2406000b24 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6130b2406000b24 device_attach: est1 attach returned 6 p4tcc1: on cpu1 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xee00-0xeeff mem 0xd0000000-0xdfffffff,0xefdf0000-0xefdfffff irq 16 at device 0.0 on pci1 pci0: at device 27.0 (no driver attached) pcib2: at device 28.0 on pci0 pci11: on pcib2 pci11: at device 0.0 (no driver attached) pcib3: at device 28.3 on pci0 pci12: on pcib3 uhci0: port 0xbf80-0xbf9f irq 20 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xbf60-0xbf7f irq 21 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xbf40-0xbf5f irq 22 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xbf20-0xbf3f irq 23 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xffa80000-0xffa803ff irq 20 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci3: on pcib4 bfe0: mem 0xef9fe000-0xef9fffff irq 17 at device 0.0 on pci3 miibus0: on bfe0 bmtphy0: PHY 1 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: using obsoleted if_watchdog interface bfe0: Ethernet address: 00:15:c5:c8:10:70 bfe0: [ITHREAD] fwohci0: <1394 Open Host Controller Interface> mem 0xef9fd800-0xef9fdfff irq 19 at device 1.0 on pci3 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 47:4f:c0:00:1f:15:95:61 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x27ec000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 46:4f:c0:15:95:61 fwe0: Ethernet address: 46:4f:c0:15:95:61 fwip0: on firewire0 fwip0: Firewire address: 47:4f:c0:00:1f:15:95:61 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode pci3: at device 1.1 (no driver attached) pci3: at device 1.2 (no driver attached) pci3: at device 1.3 (no driver attached) pci3: at device 1.4 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64,0x62,0x66 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xc0000-0xcffff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 76319MB at ata0-master SATA150 acd0: DVDR at ata1-master UDMA33 GEOM_LABEL: Label for provider ad0s1 is ntfs/Windows. SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad0s3a --------------080401030803020405030909-- From owner-freebsd-drivers@FreeBSD.ORG Thu Dec 13 22:05:44 2007 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 5CF7516A469 for ; Thu, 13 Dec 2007 22:05:44 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 9F94E13C465 for ; Thu, 13 Dec 2007 22:05:43 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2007 21:39:02 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO homeKamikaze.norad) [129.13.72.169] by mail.gmx.net (mp043) with SMTP; 13 Dec 2007 22:39:02 +0100 X-Authenticated: #5465401 X-Provags-ID: V01U2FsdGVkX1/r4A4pTYHrHGJv+UMP4XhQscEhU6JUcaKqFsTo0i ovFdLQXrPVlFfJ Message-ID: <4761A673.7040009@gmx.de> Date: Thu, 13 Dec 2007 22:38:59 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20071203) MIME-Version: 1.0 To: Vince References: <472A6708.9030109@clearchain.com> <476152E9.3090707@unsane.co.uk> In-Reply-To: <476152E9.3090707@unsane.co.uk> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) 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: Thu, 13 Dec 2007 22:05:44 -0000 Vince wrote: > Benjamin Close wrote: > Thanks for getting this driver going, I'm now using the version in 7.0, > Its working very well for me other than one (reasonably minor) thing, > which is that "ifconfig wpi0 scan" just sits there until I kill it. the > driver works in every other way, associates, works with WEP (havent > tried with WPA.) It will find and associate with a network if I just put > in "ifconfig wpi0 up" or if i use wpa_supplicant. I've had the same problem with ipw0 until my thinkpad burst into flames. A workaround is something like this: # ifconfig wpi0 up && sleep 3 && ifconfig wpi0 list scan On a sidenote, with RELENG_7 WPA finally started working for ipw on my system (which so shortly after the transition burst into flames). From owner-freebsd-drivers@FreeBSD.ORG Sat Dec 15 18:42:15 2007 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 4878E16A469 for ; Sat, 15 Dec 2007 18:42:15 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 24F0013C43E for ; Sat, 15 Dec 2007 18:42:15 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id CC20B61B10A for ; Sat, 15 Dec 2007 10:42:14 -0800 (PST) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13727-05 for ; Sat, 15 Dec 2007 10:42:12 -0800 (PST) Received: from [10.47.1.118] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id D98D761B0DE for ; Sat, 15 Dec 2007 10:42:11 -0800 (PST) Message-ID: <47642003.3080202@miralink.com> Date: Sat, 15 Dec 2007 10:42:11 -0800 From: Sean Bruno User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: freebsd-drivers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Sat Dec 15 10:42:12 2007 X-DSPAM-Confidence: 0.7856 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 47642004177681214584237 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Subject: FreeBSD Kernel "Newbies" 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, 15 Dec 2007 18:42:15 -0000 I noticed that the Linux folks have started up a "newbies" project recently that allows mentoring and growth of new kernel programmers as well as a conduit for manufacturers to get drivers written and bugs fixed. http://kernelnewbies.org/ Is there any interest in starting up such an endeavor in the FreeBSD community? I think I could spend ~10 hours a week on such a project, but my kernel programming skills are mediocre at best. Sean