From owner-freebsd-arch@FreeBSD.ORG Sun Mar 12 12:02:48 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19F8916A400 for ; Sun, 12 Mar 2006 12:02:48 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from vsmtp2.tin.it (vsmtp2.tin.it [212.216.176.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFD5043D55 for ; Sun, 12 Mar 2006 12:02:47 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp2.tin.it (7.2.072.1) id 44057FFC0093018F for freebsd-arch@freebsd.org; Sun, 12 Mar 2006 13:03:34 +0100 Message-ID: <44140E09.3000203@aruba.it> Date: Sun, 12 Mar 2006 13:03:21 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-arch@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 12:02:48 -0000 Hello! I'm tring to have my Neteasy DRP-32TXD PCMCIA ethernet working on my Omnibook 900 laptop: the card seems to be recognized and prompt: TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: d11302ab Functions: Network Adaptor, Memory Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Product version: 5.0 Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 | | TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00 cardbus0: Opening BAR: type=IO, bar=10, len=0100 cardbus0: Opening BAR: type=MEM, bar=14, len=0400 CIS reading done cardbus0: Non-prefetchable memory at 88000000-880003ff cardbus0: IO port at 1000-10ff found-> vendor=0x1186, dev=0x1561, revid=0x11 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 cardbus0: at device 0.0 (no driver attached) but no driver attached and it's not displayed with ifconfig -a: plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 I'm using i386/GENERIC kernel, so de driver (tulip) should be present. This card is listed in /usr/share/misc/pci_vendors under D-Link 1186 D-Link System Inc ... 1561 DRP-32TXD CardBus PC Card Any idea on how I can have this card working? all I can add is this card has driver attached (and is apparentely activated)each time I kldload snd_emu10k1 ... but I think this is a pure coincidence. Thanks in advance Lila From owner-freebsd-arch@FreeBSD.ORG Mon Mar 13 17:09:09 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC88A16A430; Mon, 13 Mar 2006 17:09:07 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AFF443D5E; Mon, 13 Mar 2006 17:09:00 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:Pjc4oGZGxqH4hVGdTGl8Rt3lpxTfxpgaHxEsVkuRhOvfqqgXYNNzc3mljIWjjKy+@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id k2DH8o46037313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 02:08:54 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 14 Mar 2006 02:08:50 +0900 Message-ID: From: Hajimu UMEMOTO To: arch@FreeBSD.org, current@FreeBSD.org User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Tue, 14 Mar 2006 02:08:55 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: Hajimu UMEMOTO Subject: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 17:09:09 -0000 Hi, I wish to upgrade the base version of our resolver in libc to BIND9's one. Since, our resolver is already thread-safe, it doesn't bring in major benefit for us. However, it makes chasing updating of BIND9 bit easier. Further, new res_n*() functions are used in some applications these days. Since, our resolver has many local changes, we cannot simply use contrib/bind9/lib/bind. So, I'll import it into lib/libc, then merge our local changes into it. I'll separate isc, nameser and resolv directories from net, as NetBSD did. Since, res_sendsigned(3) and the friends use MD5 functions, it is hard to include them without having MD5 functions in libc. So, I'll not merge them into libc. Since, res_update(3) in BIND9 is not binary compatible with our res_update(3), I'll leave our res_update(3) as is, except some necessary modifications. The res_update(3) and the friends are not essential part of the resolver. They are not defined in resolv.h but defined in res_update.h separately in BIND9. Further, they are not called from our tree. So, I'll hide them from our resolv.h, but leave them only for binary backward compatibility (perhaps, no one calls them). Since, struct __res_state_ext is not exposed in BIND9, I'll hide it from our resolv.h. And, I'll remove global variable _res_ext. It breaks binary backward compatibility. But, since it is not used from outside of our libc, I think it is safe. The patches are: http://www.imasy.or.jp/~ume/FreeBSD/libc-bind9-7c-20060313.diff.gz (for HEAD as of today) http://www.imasy.or.jp/~ume/FreeBSD/libc-bind9-6s-20060313.diff.gz (for RELENG_6 as of today) You need to remove some obsolete files. Please refer the instruction written in the head of the patch. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-arch@FreeBSD.ORG Mon Mar 13 19:27:59 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21EC716A400; Mon, 13 Mar 2006 19:27:59 +0000 (UTC) (envelope-from peter@wemm.org) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7A3F43D53; Mon, 13 Mar 2006 19:27:58 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id CF4AD197AF; Mon, 13 Mar 2006 11:27:58 -0800 (PST) From: Peter Wemm To: freebsd-arch@freebsd.org Date: Mon, 13 Mar 2006 11:27:57 -0800 User-Agent: KMail/1.8.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603131127.58239.peter@wemm.org> Cc: arch@freebsd.org, current@freebsd.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 19:27:59 -0000 =46rom the patch: =2D#define h_errno (*__h_error()) +#define h_errno (*__h_errno()) =2E... /* DO NOT USE THESE, THEY ARE SUBJECT TO CHANGE AND ARE NOT PORTABLE!!!=20 */ =2Dint * __h_error(void); +int * __h_errno(void); This is a significant ABI change. Anything that references the public=20 "h_errno" definition will no longer link against the new libc. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-arch@FreeBSD.ORG Mon Mar 13 19:27:59 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21EC716A400; Mon, 13 Mar 2006 19:27:59 +0000 (UTC) (envelope-from peter@wemm.org) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7A3F43D53; Mon, 13 Mar 2006 19:27:58 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id CF4AD197AF; Mon, 13 Mar 2006 11:27:58 -0800 (PST) From: Peter Wemm To: freebsd-arch@freebsd.org Date: Mon, 13 Mar 2006 11:27:57 -0800 User-Agent: KMail/1.8.3 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603131127.58239.peter@wemm.org> Cc: arch@freebsd.org, current@freebsd.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 19:27:59 -0000 =46rom the patch: =2D#define h_errno (*__h_error()) +#define h_errno (*__h_errno()) =2E... /* DO NOT USE THESE, THEY ARE SUBJECT TO CHANGE AND ARE NOT PORTABLE!!!=20 */ =2Dint * __h_error(void); +int * __h_errno(void); This is a significant ABI change. Anything that references the public=20 "h_errno" definition will no longer link against the new libc. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-arch@FreeBSD.ORG Mon Mar 13 20:47:43 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDEB16A424 for ; Mon, 13 Mar 2006 20:47:43 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC1F43D99 for ; Mon, 13 Mar 2006 20:47:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2DKip8j079187; Mon, 13 Mar 2006 13:45:07 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 13 Mar 2006 13:45:09 -0700 (MST) Message-Id: <20060313.134509.25161363.imp@bsdimp.com> To: liladude@aruba.it From: "M. Warner Losh" In-Reply-To: <44140E09.3000203@aruba.it> References: <44140E09.3000203@aruba.it> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 13 Mar 2006 13:45:07 -0700 (MST) Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 20:47:43 -0000 In message: <44140E09.3000203@aruba.it> Lila writes: : Hello! : I'm tring to have my Neteasy DRP-32TXD PCMCIA ethernet working on my : Omnibook 900 laptop: the card seems to be recognized and prompt: : : TUPLE: LINKTARGET [3]: 43 49 53 : Manufacturer ID: d11302ab : Functions: Network Adaptor, Memory : Function Extension: 0102 : Function Extension: 0280969800 : Function Extension: 0200e1f505 : Function Extension: 0301 : Product version: 5.0 : Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 | | : TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00 : cardbus0: Opening BAR: type=IO, bar=10, len=0100 : cardbus0: Opening BAR: type=MEM, bar=14, len=0400 : CIS reading done : cardbus0: Non-prefetchable memory at 88000000-880003ff : cardbus0: IO port at 1000-10ff : found-> vendor=0x1186, dev=0x1561, revid=0x11 : bus=2, slot=0, func=0 : class=02-00-00, hdrtype=0x00, mfdev=0 : cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) : lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) : intpin=a, irq=10 : powerspec 2 supports D0 D1 D2 D3 current D0 : cardbus0: at device 0.0 (no driver attached) : : but no driver attached and it's not displayed with ifconfig -a: : : plip0: flags=108810 mtu 1500 : lo0: flags=8049 mtu 16384 : inet6 ::1 prefixlen 128 : inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 : inet 127.0.0.1 netmask 0xff000000 : : I'm using i386/GENERIC kernel, so de driver (tulip) should be present. : This card is listed in /usr/share/misc/pci_vendors under D-Link : : 1186 D-Link System Inc : ... : 1561 DRP-32TXD CardBus PC Card : : Any idea on how I can have this card working? : all I can add is this card has driver attached (and is apparentely : activated)each time I kldload snd_emu10k1 ... but I think this is a pure : coincidence. It is. Each time you load a device driver, all unprobed devices are presented to the newly loaded device driver.... I'd try the following drivers: dc, rl, re, fxp to see if any of them work. One should. It is hard to know which one, but I'm guessing rl. Warner From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 00:31:04 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7632016A422; Tue, 14 Mar 2006 00:31:04 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC9F43D58; Tue, 14 Mar 2006 00:30:59 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:fs5oqDl4v0COe5rGNUDT19n34W2y9F94ST+JP+OHRX5jvmp/TO4Y3mYfiMCkc8Y3@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id k2E0Urk2011653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 09:30:54 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 14 Mar 2006 09:30:53 +0900 Message-ID: From: Hajimu UMEMOTO To: Peter Wemm In-Reply-To: <200603131127.58239.peter@wemm.org> References: <200603131127.58239.peter@wemm.org> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Tue, 14 Mar 2006 09:30:55 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: arch@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 00:31:04 -0000 Hi, >>>>> On Mon, 13 Mar 2006 11:27:57 -0800 >>>>> Peter Wemm said: peter> From the patch: peter> -#define h_errno (*__h_error()) peter> +#define h_errno (*__h_errno()) peter> .... peter> /* DO NOT USE THESE, THEY ARE SUBJECT TO CHANGE AND ARE NOT PORTABLE!!! peter> */ peter> -int * __h_error(void); peter> +int * __h_errno(void); peter> This is a significant ABI change. Anything that references the public peter> "h_errno" definition will no longer link against the new libc. No, I added an alias for __h_error for binary backward compatibility. +/* binary backward compatibility for FreeBSD 5.x and 6.x */ +__weak_reference(__h_errno, __h_error); Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 00:31:04 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7632016A422; Tue, 14 Mar 2006 00:31:04 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC9F43D58; Tue, 14 Mar 2006 00:30:59 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:fs5oqDl4v0COe5rGNUDT19n34W2y9F94ST+JP+OHRX5jvmp/TO4Y3mYfiMCkc8Y3@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id k2E0Urk2011653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 09:30:54 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 14 Mar 2006 09:30:53 +0900 Message-ID: From: Hajimu UMEMOTO To: Peter Wemm In-Reply-To: <200603131127.58239.peter@wemm.org> References: <200603131127.58239.peter@wemm.org> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Tue, 14 Mar 2006 09:30:55 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: arch@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 00:31:04 -0000 Hi, >>>>> On Mon, 13 Mar 2006 11:27:57 -0800 >>>>> Peter Wemm said: peter> From the patch: peter> -#define h_errno (*__h_error()) peter> +#define h_errno (*__h_errno()) peter> .... peter> /* DO NOT USE THESE, THEY ARE SUBJECT TO CHANGE AND ARE NOT PORTABLE!!! peter> */ peter> -int * __h_error(void); peter> +int * __h_errno(void); peter> This is a significant ABI change. Anything that references the public peter> "h_errno" definition will no longer link against the new libc. No, I added an alias for __h_error for binary backward compatibility. +/* binary backward compatibility for FreeBSD 5.x and 6.x */ +__weak_reference(__h_errno, __h_error); Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 11:10:12 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D933116A425 for ; Tue, 14 Mar 2006 11:10:12 +0000 (UTC) (envelope-from liladude@aruba.it) Received: from vsmtp21.tin.it (vsmtp21.tin.it [212.216.176.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D4643D53 for ; Tue, 14 Mar 2006 11:10:12 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp21.tin.it (7.2.072.1) id 4405C90700A2AE88; Tue, 14 Mar 2006 12:09:42 +0100 Message-ID: <4416A49A.6070206@aruba.it> Date: Tue, 14 Mar 2006 12:10:18 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "M. Warner Losh" References: <44140E09.3000203@aruba.it> <20060313.134509.25161363.imp@bsdimp.com> In-Reply-To: <20060313.134509.25161363.imp@bsdimp.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 11:10:13 -0000 Thanks for your answer. I tried to kldload some if_ drivers, but all of them already exist, because I am using the GENERIC kernel where all of them are already setted. I was waiting to find the good one before actually recompiling kernel. I thought good one should be if_de, since my card is setted under the tulip driver on linux... Maybe I just need to find a way to tell kernel what driver my card need... but I don't know where I should start. I wonder if having this card stated as D-Link insted of NetEasy in pci_vendors list can be the problem. If I could find a way to tell kernel they are the same thing I may be able to solve this problem. Any idea? Lila M. Warner Losh ha scritto: > In message: <44140E09.3000203@aruba.it> > Lila writes: > : Hello! > : I'm tring to have my Neteasy DRP-32TXD PCMCIA ethernet working on my > : Omnibook 900 laptop: the card seems to be recognized and prompt: > : > : TUPLE: LINKTARGET [3]: 43 49 53 > : Manufacturer ID: d11302ab > : Functions: Network Adaptor, Memory > : Function Extension: 0102 > : Function Extension: 0280969800 > : Function Extension: 0200e1f505 > : Function Extension: 0301 > : Product version: 5.0 > : Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 | | > : TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00 > : cardbus0: Opening BAR: type=IO, bar=10, len=0100 > : cardbus0: Opening BAR: type=MEM, bar=14, len=0400 > : CIS reading done > : cardbus0: Non-prefetchable memory at 88000000-880003ff > : cardbus0: IO port at 1000-10ff > : found-> vendor=0x1186, dev=0x1561, revid=0x11 > : bus=2, slot=0, func=0 > : class=02-00-00, hdrtype=0x00, mfdev=0 > : cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) > : lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) > : intpin=a, irq=10 > : powerspec 2 supports D0 D1 D2 D3 current D0 > : cardbus0: at device 0.0 (no driver attached) > : > : but no driver attached and it's not displayed with ifconfig -a: > : > : plip0: flags=108810 mtu 1500 > : lo0: flags=8049 mtu 16384 > : inet6 ::1 prefixlen 128 > : inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > : inet 127.0.0.1 netmask 0xff000000 > : > : I'm using i386/GENERIC kernel, so de driver (tulip) should be present. > : This card is listed in /usr/share/misc/pci_vendors under D-Link > : > : 1186 D-Link System Inc > : ... > : 1561 DRP-32TXD CardBus PC Card > : > : Any idea on how I can have this card working? > : all I can add is this card has driver attached (and is apparentely > : activated)each time I kldload snd_emu10k1 ... but I think this is a pure > : coincidence. > > It is. Each time you load a device driver, all unprobed devices are > presented to the newly loaded device driver.... > > I'd try the following drivers: dc, rl, re, fxp to see if any of them > work. One should. It is hard to know which one, but I'm guessing rl. > > Warner > From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 12:33:07 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46FC416A401; Tue, 14 Mar 2006 12:33:07 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 782CE43D45; Tue, 14 Mar 2006 12:33:06 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k2ECX33o020885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 15:33:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k2ECX3Au020884; Tue, 14 Mar 2006 15:33:03 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 14 Mar 2006 15:33:03 +0300 From: Gleb Smirnoff To: Hajimu UMEMOTO Message-ID: <20060314123303.GG1102@FreeBSD.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 12:33:07 -0000 On Tue, Mar 14, 2006 at 02:08:50AM +0900, Hajimu UMEMOTO wrote: H> Since, res_sendsigned(3) and the friends use MD5 functions, it is hard H> to include them without having MD5 functions in libc. So, I'll not H> merge them into libc. Why not add MD5 functions to our libc? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 12:36:06 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F4DA16A427; Tue, 14 Mar 2006 12:36:06 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC89343D46; Tue, 14 Mar 2006 12:36:05 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k2ECYjvZ020942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 15:34:45 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k2ECYiNB020941; Tue, 14 Mar 2006 15:34:44 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 14 Mar 2006 15:34:44 +0300 From: Gleb Smirnoff To: Florent Thoumie Message-ID: <20060314123444.GH1102@FreeBSD.org> References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1142004490.17473.16.camel@mayday.esat.net> User-Agent: Mutt/1.5.6i Cc: Dag-Erling Sm?rgrav , Andre Oppermann , freebsd-arch@FreeBSD.org Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 12:36:06 -0000 On Fri, Mar 10, 2006 at 03:28:10PM +0000, Florent Thoumie wrote: F> > > > FYI (if you're not reading -ports or -net), I just sent a prototype for F> > > > the openospfd port. F> > > Cool, thanks! I'm happy if you maintain the port as I've never done a port F> > > before. F> > F> > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. F> F> I'd be more than happy to see them in src/contrib. Me too. Question to Andre: what do we need to merge/add to our kernel to run OpenBGPd+OpenOSPFd with all their features? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 12:42:59 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDB1B16A400 for ; Tue, 14 Mar 2006 12:42:59 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A32143D78 for ; Tue, 14 Mar 2006 12:42:52 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 69669 invoked from network); 14 Mar 2006 12:40:19 -0000 Received: from c00l3r.networx.ch (HELO freebsd.org) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 14 Mar 2006 12:40:19 -0000 Message-ID: <4416BA4E.FFDA8134@freebsd.org> Date: Tue, 14 Mar 2006 13:42:54 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> <20060314123444.GH1102@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Dag-Erling Sm?rgrav , freebsd-arch@FreeBSD.org, Florent Thoumie Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 12:42:59 -0000 Gleb Smirnoff wrote: > > On Fri, Mar 10, 2006 at 03:28:10PM +0000, Florent Thoumie wrote: > F> > > > FYI (if you're not reading -ports or -net), I just sent a prototype for > F> > > > the openospfd port. > F> > > Cool, thanks! I'm happy if you maintain the port as I've never done a port > F> > > before. > F> > > F> > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. > F> > F> I'd be more than happy to see them in src/contrib. > > Me too. > > Question to Andre: what do we need to merge/add to our kernel to > run OpenBGPd+OpenOSPFd with all their features? Two more things I want to commit later today. One is the addition of strtonum() to libc and the other is a small change to the routing socket to make it possible to change just the flags on a route instead of replacing the entire route. That's it to get all standard functionality running. Beyond that we have to fix our IPSEC API (I'm not sure whose fault it is, but Open- and FreeBSD are not fully compatible) and we have to finish the TCPMD5 support in the kernel. -- Andre From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 12:46:20 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA92E16A41F; Tue, 14 Mar 2006 12:46:20 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24BD043D45; Tue, 14 Mar 2006 12:46:20 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id 9934011493; Tue, 14 Mar 2006 13:46:18 +0100 (CET) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81374-03; Tue, 14 Mar 2006 13:46:12 +0100 (CET) Received: from mayday.esat.net (mayday.esat.net [193.95.134.156]) by smtp.xbsd.org (Postfix) with ESMTP id 46D0E11443; Tue, 14 Mar 2006 13:46:12 +0100 (CET) From: Florent Thoumie To: Gleb Smirnoff In-Reply-To: <20060314123444.GH1102@FreeBSD.org> References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> <20060314123444.GH1102@FreeBSD.org> Content-Type: text/plain Date: Tue, 14 Mar 2006 12:46:04 +0000 Message-Id: <1142340364.823.16.camel@mayday.esat.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at xbsd.org Cc: Dag-Erling Sm?rgrav , Andre Oppermann , freebsd-arch@FreeBSD.org Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 12:46:20 -0000 On Tue, 2006-03-14 at 15:34 +0300, Gleb Smirnoff wrote: > On Fri, Mar 10, 2006 at 03:28:10PM +0000, Florent Thoumie wrote: > F> > > > FYI (if you're not reading -ports or -net), I just sent a prototype for > F> > > > the openospfd port. > F> > > Cool, thanks! I'm happy if you maintain the port as I've never done a port > F> > > before. > F> > > F> > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. > F> > F> I'd be more than happy to see them in src/contrib. > > Me too. > > Question to Andre: what do we need to merge/add to our kernel to > run OpenBGPd+OpenOSPFd with all their features? I'm not sure OpenOSPFD lacks something, but I think OpenBGPD still needs PF_KEY support for MD5. At least that's the current state of affairs for ports. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 12:50:39 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EB9F16A41F; Tue, 14 Mar 2006 12:50:39 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5669C43D70; Tue, 14 Mar 2006 12:50:24 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k2ECn6Jm021160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Mar 2006 15:49:07 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k2ECn6mc021159; Tue, 14 Mar 2006 15:49:06 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Tue, 14 Mar 2006 15:49:06 +0300 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20060314124906.GI1102@cell.sick.ru> References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> <20060314123444.GH1102@FreeBSD.org> <4416BA4E.FFDA8134@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4416BA4E.FFDA8134@freebsd.org> User-Agent: Mutt/1.5.6i Cc: Dag-Erling Sm?rgrav , freebsd-arch@FreeBSD.org, Florent Thoumie Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 12:50:39 -0000 On Tue, Mar 14, 2006 at 01:42:54PM +0100, Andre Oppermann wrote: A> > On Fri, Mar 10, 2006 at 03:28:10PM +0000, Florent Thoumie wrote: A> > F> > > > FYI (if you're not reading -ports or -net), I just sent a prototype for A> > F> > > > the openospfd port. A> > F> > > Cool, thanks! I'm happy if you maintain the port as I've never done a port A> > F> > > before. A> > F> > A> > F> > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. A> > F> A> > F> I'd be more than happy to see them in src/contrib. A> > A> > Me too. A> > A> > Question to Andre: what do we need to merge/add to our kernel to A> > run OpenBGPd+OpenOSPFd with all their features? A> A> Two more things I want to commit later today. One is the addition of A> strtonum() to libc and the other is a small change to the routing socket to A> make it possible to change just the flags on a route instead of replacing A> the entire route. That's it to get all standard functionality running. Good! A> Beyond that we have to fix our IPSEC API (I'm not sure whose fault it is, A> but Open- and FreeBSD are not fully compatible) and we have to finish the A> TCPMD5 support in the kernel. Yes, I remember about TCP MD5. What about choosing route using administrative distance of the protocol? Does this feature exist in Open(BSD+BGPdOSPFd)? Is it possible OSPF and BGP to inject same route into kernel, and kernel prefers the OSPF one until it is present, and then switches to BGP? This is what we have in zebra, where the zebra daemon performs this task - choosing between routes originated from different protocols. Since OpenBSD doesn't have this intermediate daemon, I guess they do the choosing process in kernel. Is this correct or I mistake? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 13:04:02 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4062A16A423 for ; Tue, 14 Mar 2006 13:04:02 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A81243D49 for ; Tue, 14 Mar 2006 13:04:01 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 69874 invoked from network); 14 Mar 2006 13:01:27 -0000 Received: from c00l3r.networx.ch (HELO freebsd.org) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 14 Mar 2006 13:01:27 -0000 Message-ID: <4416BF43.F1BE4E24@freebsd.org> Date: Tue, 14 Mar 2006 14:04:03 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> <20060314123444.GH1102@FreeBSD.org> <4416BA4E.FFDA8134@freebsd.org> <20060314124906.GI1102@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Dag-Erling Sm?rgrav , freebsd-arch@FreeBSD.org, Florent Thoumie Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 13:04:02 -0000 Gleb Smirnoff wrote: > > On Tue, Mar 14, 2006 at 01:42:54PM +0100, Andre Oppermann wrote: > A> > On Fri, Mar 10, 2006 at 03:28:10PM +0000, Florent Thoumie wrote: > A> > F> > > > FYI (if you're not reading -ports or -net), I just sent a prototype for > A> > F> > > > the openospfd port. > A> > F> > > Cool, thanks! I'm happy if you maintain the port as I've never done a port > A> > F> > > before. > A> > F> > > A> > F> > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. > A> > F> > A> > F> I'd be more than happy to see them in src/contrib. > A> > > A> > Me too. > A> > > A> > Question to Andre: what do we need to merge/add to our kernel to > A> > run OpenBGPd+OpenOSPFd with all their features? > A> > A> Two more things I want to commit later today. One is the addition of > A> strtonum() to libc and the other is a small change to the routing socket to > A> make it possible to change just the flags on a route instead of replacing > A> the entire route. That's it to get all standard functionality running. > > Good! > > A> Beyond that we have to fix our IPSEC API (I'm not sure whose fault it is, > A> but Open- and FreeBSD are not fully compatible) and we have to finish the > A> TCPMD5 support in the kernel. > > Yes, I remember about TCP MD5. > > What about choosing route using administrative distance of the protocol? Does > this feature exist in Open(BSD+BGPdOSPFd)? Is it possible OSPF and BGP to > inject same route into kernel, and kernel prefers the OSPF one until it > is present, and then switches to BGP? This is what we have in zebra, where > the zebra daemon performs this task - choosing between routes originated > from different protocols. Since OpenBSD doesn't have this intermediate > daemon, I guess they do the choosing process in kernel. Is this correct or > I mistake? They tag (PROTO[1|2]) their routes and OSPF may overwrite BGP routes. When OSPF removes a route BGP will insert its own again. Claudio and I want to make this more formal and more in the way you describe it above. That then needs approriate kernel functionality. We are currently debating the semantics to find a good solution for both the routing daemon and kernel hackers. ;) We'll float a proposal in the near future. -- Andre From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 13:18:31 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DC1216A432 for ; Tue, 14 Mar 2006 13:18:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0525143D53 for ; Tue, 14 Mar 2006 13:18:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2EDIBe1007037; Tue, 14 Mar 2006 08:18:11 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-arch@freebsd.org Date: Tue, 14 Mar 2006 08:18:08 -0500 User-Agent: KMail/1.8.3 References: <44140E09.3000203@aruba.it> <20060313.134509.25161363.imp@bsdimp.com> <4416A49A.6070206@aruba.it> In-Reply-To: <4416A49A.6070206@aruba.it> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603140818.09838.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1329/Mon Mar 13 19:22:03 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Lila Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 13:18:31 -0000 On Tuesday 14 March 2006 06:10 am, Lila wrote: > Thanks for your answer. > I tried to kldload some if_ drivers, but all of them already exist, > because I am using the GENERIC kernel where all of them are already > setted. I was waiting to find the good one before actually recompiling > kernel. > I thought good one should be if_de, since my card is setted under the > tulip driver on linux... Maybe I just need to find a way to tell kernel > what driver my card need... but I don't know where I should start. > I wonder if having this card stated as D-Link insted of NetEasy in > pci_vendors list can be the problem. If I could find a way to tell > kernel they are the same thing I may be able to solve this problem. > Any idea? dc(4) is a better candidate for most tulip cards than de(4). de(4) only supports rather ancient tulip cards. dc(4) supports most of the non-ancient cards. Try the patch at http://www.FreeBSD.org/~jhb/patches/drp-32txd.patch =2D-=20 John Baldwin =C2=A0<>< =C2=A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =C2=A0=3D =C2=A0http://www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 15:09:46 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2C3516A422; Tue, 14 Mar 2006 15:09:46 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19A9E43DCE; Tue, 14 Mar 2006 15:09:13 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:3HVm7doYOQoMbGtVtrF5byUcAiv8aERi36bz3tym11mZa2HYGchk9qPRhcM6g8tu@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id k2EF8xtm095052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Mar 2006 00:09:02 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 15 Mar 2006 00:08:58 +0900 Message-ID: From: Hajimu UMEMOTO To: Gleb Smirnoff In-Reply-To: <20060314123303.GG1102@FreeBSD.org> References: <20060314123303.GG1102@FreeBSD.org> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Wed, 15 Mar 2006 00:09:03 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 15:09:46 -0000 Hi, >>>>> On Tue, 14 Mar 2006 15:33:03 +0300 >>>>> Gleb Smirnoff said: glebius> On Tue, Mar 14, 2006 at 02:08:50AM +0900, Hajimu UMEMOTO wrote: H> Since, res_sendsigned(3) and the friends use MD5 functions, it is hard H> to include them without having MD5 functions in libc. So, I'll not H> merge them into libc. glebius> Why not add MD5 functions to our libc? Yup, we have libmd separately. Since, we are not using res_sendsigned(3), we don't need to add it in libc, for now. If it is required, we can add it later. Adding functions is easy, but removing functions is painful. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 15:40:12 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1E0E16A423 for ; Tue, 14 Mar 2006 15:40:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8207B43D45 for ; Tue, 14 Mar 2006 15:40:11 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 292EA2000BB for ; Tue, 14 Mar 2006 16:40:09 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 688162000C2; Tue, 14 Mar 2006 16:40:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 441BC44487E for ; Tue, 14 Mar 2006 15:38:02 +0000 (UTC) Date: Tue, 14 Mar 2006 15:38:01 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: freebsd-arch@FreeBSD.org In-Reply-To: <4416BA4E.FFDA8134@freebsd.org> Message-ID: <20060314152635.D73618@maildrop.int.zabbadoz.net> References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> <1142004490.17473.16.camel@mayday.esat.net> <20060314123444.GH1102@FreeBSD.org> <4416BA4E.FFDA8134@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 15:40:12 -0000 On Tue, 14 Mar 2006, Andre Oppermann wrote: > Beyond that we have to fix our IPSEC API (I'm not sure whose fault it is, > but Open- and FreeBSD are not fully compatible) I think you mean PF_KEY and you should talk to gnn about that. He was working on this in p4. > and we have to finish the TCPMD5 support in the kernel. bms once wrote about that (back in 2004). You can find the link to the posting in xorp archive on: http://sources.zabbadoz.net/freebsd/tcp-md5.html -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 17:46:02 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD60916A41F; Tue, 14 Mar 2006 17:46:02 +0000 (UTC) (envelope-from ck-lists@cksoft.de) Received: from mx11.cksoft.de (mx11.cksoft.de [62.111.66.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id A585D43D48; Tue, 14 Mar 2006 17:46:01 +0000 (GMT) (envelope-from ck-lists@cksoft.de) Received: from vesihiisi.cksoft.de (unknown [192.168.64.10]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mx12.cksoft.de (Postfix) with ESMTP id 50E51B9AC; Tue, 14 Mar 2006 18:46:01 +0100 (CET) Received: from vesihiisi.cksoft.de (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 694B51EA3; Tue, 14 Mar 2006 18:45:58 +0100 (CET) Received: by vesihiisi.cksoft.de (Postfix, from userid 1000) id 9B9931E9C; Tue, 14 Mar 2006 18:45:54 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 93F4C1E86; Tue, 14 Mar 2006 18:45:54 +0100 (CET) Date: Tue, 14 Mar 2006 18:45:54 +0100 (CET) From: Christian Kratzer X-X-Sender: ck@vesihiisi.cksoft.de To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= In-Reply-To: <86d5gu30qx.fsf@xps.des.no> Message-ID: <20060314184157.V10576@vesihiisi.cksoft.de> References: <1141834577.17213.15.camel@mayday.esat.net> <440F0893.5B17D61E@freebsd.org> <1141836428.17213.24.camel@mayday.esat.net> <440F0F5F.32400100@freebsd.org> <86d5gu30qx.fsf@xps.des.no> X-Spammer-Kill-Ratio: 75% MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-863743141-1142358354=:10576" X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on vesihiisi.cksoft.de Cc: Florent Thoumie , Andre Oppermann , freebsd-arch@freebsd.org Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Christian Kratzer List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 17:46:02 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-863743141-1142358354=:10576 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hi, On Fri, 10 Mar 2006, Dag-Erling Sm=F8rgrav wrote: > Andre Oppermann writes: >> Florent Thoumie writes: >>> FYI (if you're not reading -ports or -net), I just sent a prototype for >>> the openospfd port. >> Cool, thanks! I'm happy if you maintain the port as I've never done a p= ort >> before. > > IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. please don't bloat the base system with something that can run equally well from ports. Else other people will for example want a full blown openldap in the base just so that we can run nsswitch-ldap. Ports are far better at tracking and keeping up to date with fast moving complex third party packages than base. Greetings Christian --=20 Christian Kratzer ck@cksoft.de CK Software GmbH http://www.cksoft.de/ Phone: +49 7452 889 135 Fax: +49 7452 889 136 --0-863743141-1142358354=:10576-- From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 17:48:38 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 157FA16A401; Tue, 14 Mar 2006 17:48:38 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DD5643D69; Tue, 14 Mar 2006 17:48:37 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id 82C181EC322; Tue, 14 Mar 2006 18:48:36 +0100 (CET) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.4/8.13.4) with ESMTP id k2EHmP0H022177; Tue, 14 Mar 2006 18:48:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Christian Kratzer From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 14 Mar 2006 18:45:54 +0100." <20060314184157.V10576@vesihiisi.cksoft.de> Date: Tue, 14 Mar 2006 18:48:25 +0100 Message-ID: <22176.1142358505@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-arch@freebsd.org, Andre Oppermann , Florent Thoumie Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 17:48:38 -0000 In message <20060314184157.V10576@vesihiisi.cksoft.de>, Christian Kratzer writes: >> IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. > >please don't bloat the base system with something that can run >equally well from ports. I would tend to agree. 90% or more of all FreeBSD systems will not run either of these routing daemons, so their rightful place is in ports. Also, considering the general hazzleness of src/contrib I think ports offer a far more flexible infrastructure for dealing with the software (such as openospfd-stable vs openospfd-cvs versions etc.) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 01:00:09 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2038316A401 for ; Wed, 15 Mar 2006 01:00:08 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 815F743D48 for ; Wed, 15 Mar 2006 01:00:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3879346B14 for ; Tue, 14 Mar 2006 19:59:43 -0500 (EST) Date: Wed, 15 Mar 2006 01:00:57 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Message-ID: <20060315004530.B5861@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 01:00:09 -0000 For some time now, the FreeBSD Project has been carrying around at least three ATM stacks: - netatm - HARP, the Host ATM Research Platform - netnatm - A fairly minimal socket<->virtual circuit ATM wrapper for ATM device drivers - ngatm - NetGraph ATM framework For a variety of reasons, it would be desirable to do a bit of pruning of ATM stacks. In my previous conversations with Harti and Bruce, the conclusion has generally been that ngatm and netnatm provide almost all functionality provided by netatm and more, but in modern, and actively maintained, frameworks. The main motivator for pruning has to do with the SMP network stack work: we're reaching the point, discussed on a number of occasions previously on this mailing list, where jettisoning unmaintained network stack components that are unable to run MPSAFE, is highly desirable. This would allow us to remove compatibility shims that are increasingly burdonsome in terms of performance and complexity. Another aspect of this has to do with upcoming changes to the socket and pcb code, which will require maintainers of protocols to do a small but non-trivial amount of work to update protocols to fit the new socket behavior. Right now, almost all other sections of the network stack have active maintainers who are able to do this work, both development and testing, except for the netatm code. We've reached the point where continuing to carry around a third ATM stack is a significant impediment to continued work on network stack performance and reliability work. This should not be a surprise to anyone who reads this mailing list regularly, since I sent out e-mail on this very topic on July 18, 2005, warning that netatm (and several other components) were at risk as unmaintained but substantial network stack components. The proposal is as follows: In order to begin to merge revised socket/pcb code, required to fix a number of current races manifesting in the TCP code under load, and required for breaking out the tcbinfo lock which is a significant bottleneck in high performance TCP and multi-processor TCP scalability, I will disconnect netatm and dependent components from the build on April 1, 2006. At that point, I will merge updated socket and pcb reference counting. If a maintainer has not been found who can update and adequately test the netatm code for the new socket/pcb interfaces by June 30, 2006, the netatm code will be deleted from CVS HEAD (although remain available in Attic should someone turn up later). I'm happy to provide some first cut patches for any maintainer that arrives that do implement the changes, but I am unable to test them, and suspect they will be significant deficient for this reason, so will not commit them myself. This will leave us with at least two quite functional ATM implementations. Please let me know if netatm is critical to your work and you will be able to work with me to get netatm into shape. For someone already familiar with the netatm implementation and set up to perform ATM network testing, this should be straight forward and I'm happy to help in any way I can. If you are available to act in this role, my recommendation would be that we meet at BSDCan in Ottawa this May to discuss long term maintenance directions, and so that we can work out a plan for handling SMP behavior for netatm, as well as its integration with the socket code. Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 03:44:59 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC0DC16A401; Wed, 15 Mar 2006 03:44:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4907443D46; Wed, 15 Mar 2006 03:44:59 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2F3gqst099331; Tue, 14 Mar 2006 20:42:52 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 14 Mar 2006 20:42:52 -0700 (MST) Message-Id: <20060314.204252.74651890.imp@bsdimp.com> To: rwatson@freebsd.org From: Warner Losh In-Reply-To: <20060315004530.B5861@fledge.watson.org> References: <20060315004530.B5861@fledge.watson.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 14 Mar 2006 20:42:52 -0700 (MST) Cc: arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 03:44:59 -0000 > The main motivator for pruning has to do with the SMP network stack work: > we're reaching the point, discussed on a number of occasions previously on > this mailing list, where jettisoning unmaintained network stack components > that are unable to run MPSAFE, is highly desirable. What's the timeline for non-MPSAFE network drivers to be taken out behind the woodshed? Right now the list appears to be: an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip Of those, an, awi, cnw, cs, ex, ray, snc, and xe have PC Card attachments, so I may wind up doing at least some of them (snc is pc98 only, cnw and ray are very obsolete wireless cards, so I don't think I'll do them). Warner P.S. I grepped a slightly old tree, so I may have missed something. From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 06:36:31 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB0B816A401 for ; Wed, 15 Mar 2006 06:36:31 +0000 (UTC) (envelope-from liladude@aruba.it) Received: from vsmtp1.tin.it (vsmtp1.tin.it [212.216.176.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BD2F43D4C for ; Wed, 15 Mar 2006 06:36:31 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp1.tin.it (7.2.072.1) id 44057D3300B0606F; Wed, 15 Mar 2006 07:37:21 +0100 Message-ID: <4417B608.4000601@aruba.it> Date: Wed, 15 Mar 2006 07:36:56 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 References: <44140E09.3000203@aruba.it> <20060313.134509.25161363.imp@bsdimp.com> <4416A49A.6070206@aruba.it> <200603140818.09838.jhb@freebsd.org> In-Reply-To: <200603140818.09838.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 06:36:31 -0000 Thanks for your suggestion. I compiled my kernel with non ethernet driver inside, patched the driver and kldloaded it, but I could not find the card in my ifconfig. I tried twice to recompile kernel with dc driver, but ended due to fragmentation errors ... I'll try again later (kernel build is about two hours...). Lila John Baldwin ha scritto: > On Tuesday 14 March 2006 06:10 am, Lila wrote: > > dc(4) is a better candidate for most tulip cards than de(4). de(4) > only supports rather ancient tulip cards. dc(4) supports most of > the non-ancient cards. > > Try the patch at http://www.FreeBSD.org/~jhb/patches/drp-32txd.patch > From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 08:11:02 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F02DE16A401; Wed, 15 Mar 2006 08:11:02 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 651F443D48; Wed, 15 Mar 2006 08:11:01 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Mar 2006 09:10:59 +0100 Date: Wed, 15 Mar 2006 09:11:01 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Warner Losh In-Reply-To: <20060314.204252.74651890.imp@bsdimp.com> Message-ID: <20060315090615.I56469@beagle.kn.op.dlr.de> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 15 Mar 2006 08:10:59.0804 (UTC) FILETIME=[FE7A59C0:01C64807] Cc: arch@freebsd.org, rwatson@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 08:11:03 -0000 On Tue, 14 Mar 2006, Warner Losh wrote: WL>> The main motivator for pruning has to do with the SMP network stack work: WL>> we're reaching the point, discussed on a number of occasions previously on WL>> this mailing list, where jettisoning unmaintained network stack components WL>> that are unable to run MPSAFE, is highly desirable. WL> WL>What's the timeline for non-MPSAFE network drivers to be taken out WL>behind the woodshed? Right now the list appears to be: WL> WL> an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, WL> mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip Both patm and fatm are MPSAFE - I forgot, maybe, to set the INTR_MPSAFE flag. I'll fix that. harti From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 08:18:03 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C78C316A400; Wed, 15 Mar 2006 08:18:03 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3394C43D45; Wed, 15 Mar 2006 08:18:03 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Mar 2006 09:18:02 +0100 Date: Wed, 15 Mar 2006 09:18:01 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Robert Watson In-Reply-To: <20060315004530.B5861@fledge.watson.org> Message-ID: <20060315091218.E56469@beagle.kn.op.dlr.de> References: <20060315004530.B5861@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 15 Mar 2006 08:18:02.0176 (UTC) FILETIME=[FA3B3400:01C64808] Cc: arch@FreeBSD.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 08:18:04 -0000 On Wed, 15 Mar 2006, Robert Watson wrote: RW> RW>For some time now, the FreeBSD Project has been carrying around at least RW>three ATM stacks: RW> RW>- netatm - HARP, the Host ATM Research Platform RW> RW>- netnatm - A fairly minimal socket<->virtual circuit ATM wrapper for ATM RW> device drivers RW> RW>- ngatm - NetGraph ATM framework RW> RW>For a variety of reasons, it would be desirable to do a bit of pruning of ATM RW>stacks. In my previous conversations with Harti and Bruce, the conclusion RW>has generally been that ngatm and netnatm provide almost all functionality RW>provided by netatm and more, but in modern, and actively maintained, RW>frameworks. RW> RW>The main motivator for pruning has to do with the SMP network stack work: RW>we're reaching the point, discussed on a number of occasions previously on RW>this mailing list, where jettisoning unmaintained network stack components RW>that are unable to run MPSAFE, is highly desirable. This would allow us to RW>remove compatibility shims that are increasingly burdonsome in terms of RW>performance and complexity. Another aspect of this has to do with upcoming RW>changes to the socket and pcb code, which will require maintainers of RW>protocols to do a small but non-trivial amount of work to update protocols to RW>fit the new socket behavior. Right now, almost all other sections of the RW>network stack have active maintainers who are able to do this work, both RW>development and testing, except for the netatm code. RW> RW>We've reached the point where continuing to carry around a third ATM stack is RW>a significant impediment to continued work on network stack performance and RW>reliability work. This should not be a surprise to anyone who reads this RW>mailing list regularly, since I sent out e-mail on this very topic on July RW>18, 2005, warning that netatm (and several other components) were at risk as RW>unmaintained but substantial network stack components. RW> RW>The proposal is as follows: RW> RW>In order to begin to merge revised socket/pcb code, required to fix a number RW>of current races manifesting in the TCP code under load, and required for RW>breaking out the tcbinfo lock which is a significant bottleneck in high RW>performance TCP and multi-processor TCP scalability, I will disconnect netatm RW>and dependent components from the build on April 1, 2006. At that point, I RW>will merge updated socket and pcb reference counting. RW> RW>If a maintainer has not been found who can update and adequately test the RW>netatm code for the new socket/pcb interfaces by June 30, 2006, the netatm RW>code will be deleted from CVS HEAD (although remain available in Attic should RW>someone turn up later). I'm happy to provide some first cut patches for any RW>maintainer that arrives that do implement the changes, but I am unable to RW>test them, and suspect they will be significant deficient for this reason, so RW>will not commit them myself. RW> RW>This will leave us with at least two quite functional ATM implementations. RW>Please let me know if netatm is critical to your work and you will be able to RW>work with me to get netatm into shape. For someone already familiar with the RW>netatm implementation and set up to perform ATM network testing, this should RW>be straight forward and I'm happy to help in any way I can. If you are RW>available to act in this role, my recommendation would be that we meet at RW>BSDCan in Ottawa this May to discuss long term maintenance directions, and so RW>that we can work out a plan for handling SMP behavior for netatm, as well as RW>its integration with the socket code. I'm all for this removal. The only two reasons for carrying this around is that it supports CLIP over SVCs and that the driver for the IDT77211 chips is HARP-only. I have half of an ngatm driver for these chips and sent them out two at least two people during the last two years, but never heard back. I have also code for CLIP over SVCs but due to ENOTIME was not yet able to make this commit ready. If anybody knows somebody who could finish the driver it would be great. The CLIP stuff is not so critical - almost all people use PVCs only. harti From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 10:42:58 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95CE616A422 for ; Wed, 15 Mar 2006 10:42:58 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3838143D79 for ; Wed, 15 Mar 2006 10:42:58 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id AFA9646C12; Wed, 15 Mar 2006 05:42:33 -0500 (EST) Date: Wed, 15 Mar 2006 10:43:50 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Warner Losh In-Reply-To: <20060314.204252.74651890.imp@bsdimp.com> Message-ID: <20060315104037.J5861@fledge.watson.org> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 10:42:58 -0000 On Tue, 14 Mar 2006, Warner Losh wrote: >> The main motivator for pruning has to do with the SMP network stack work: >> we're reaching the point, discussed on a number of occasions previously on >> this mailing list, where jettisoning unmaintained network stack components >> that are unable to run MPSAFE, is highly desirable. > > What's the timeline for non-MPSAFE network drivers to be taken out behind > the woodshed? Right now the list appears to be: > > an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, > mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip > > Of those, an, awi, cnw, cs, ex, ray, snc, and xe have PC Card attachments, > so I may wind up doing at least some of them (snc is pc98 only, cnw and ray > are very obsolete wireless cards, so I don't think I'll do them). Currently, my focus is on getting the socket/pcb changes into the tree, so I've not had to revisit the device driver issue since 2005. The socket/pcb changes are particularly pressing because they are required for a number of other things that we need to do to the TCP code before 7.0 in order to improve TCP performance on SMP, all of which will need signficant time to settle before they hit a release. I'm very interested in our eliminating the Giant backward compatibility shims for device drivers, however. Despite the above drivers not being updated, I suspect a number are widely used, especially relating to pccard, and would like to see them updated. Would it make sense for us to set a similar set of date deadlines for non-MPSAFE drivers? I.e., August 2006 for removing them from the build, and October, 2006, for remove from the CVS HEAD? I suspect in that time several of the above will get updated. Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 10:47:46 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D86216A400; Wed, 15 Mar 2006 10:47:46 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id C595143D77; Wed, 15 Mar 2006 10:47:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id B245B1EC36C; Wed, 15 Mar 2006 11:47:36 +0100 (CET) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.4/8.13.4) with ESMTP id k2FAlQ6q025884; Wed, 15 Mar 2006 11:47:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 15 Mar 2006 10:43:50 GMT." <20060315104037.J5861@fledge.watson.org> Date: Wed, 15 Mar 2006 11:47:26 +0100 Message-ID: <25883.1142419646@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: arch@FreeBSD.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 10:47:46 -0000 In message <20060315104037.J5861@fledge.watson.org>, Robert Watson writes: >> an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, >> mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip When I last asked about interest in the mn driver, Milan Obuch said that they were shipping current products based on this chip, but I have not heard anything since. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 10:53:48 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0243116A422 for ; Wed, 15 Mar 2006 10:53:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id A18CE43D6E for ; Wed, 15 Mar 2006 10:53:47 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4EFAF46B03; Wed, 15 Mar 2006 05:53:23 -0500 (EST) Date: Wed, 15 Mar 2006 10:54:40 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Warner Losh In-Reply-To: <20060314.204252.74651890.imp@bsdimp.com> Message-ID: <20060315105031.E5861@fledge.watson.org> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 10:53:48 -0000 On Tue, 14 Mar 2006, Warner Losh wrote: >> The main motivator for pruning has to do with the SMP network stack work: >> we're reaching the point, discussed on a number of occasions previously on >> this mailing list, where jettisoning unmaintained network stack components >> that are unable to run MPSAFE, is highly desirable. > > What's the timeline for non-MPSAFE network drivers to be taken out > behind the woodshed? Right now the list appears to be: > > an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, > mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip > > Of those, an, awi, cnw, cs, ex, ray, snc, and xe have PC Card attachments, > so I may wind up doing at least some of them (snc is pc98 only, cnw and ray > are very obsolete wireless cards, so I don't think I'll do them). The other large chunk of non-MPSAFE network device driver and stack code, FYI, is the i4b code. In principle, a newly added committed is now available to work on the capi integration, and hopefully will do the SMP safety work as part of that. If not, it's also on the chopping block. It's a significant piece of otherwise unmaintained code, and something that's not trivially testable (at least, not by me or anyone I've talked to lately :-). I don't want to see it leave the tree, but it needs to be updated so that it can run MPSAFE before 7.0. Otherwise, with the exception of KAME IPSEC, the network stack code is actually in pretty good shape for removing the Giant compat shims. We've had at least a couple of people say they're willing to work on this and take steps in the right direction (including some initial patches for IPSEC improvement), but I guess we'll see come August whether it has happened. The discussion has always been about whether it's better to add IPv6 support to FAST_IPSEC, or lock down KAME IPSEC. Both are desirable, and both require significant familiarity with the code and protocols involved. Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 11:08:10 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDB4716A401; Wed, 15 Mar 2006 11:08:09 +0000 (UTC) (envelope-from flz@xbsd.org) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A1FE43D45; Wed, 15 Mar 2006 11:08:09 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id A7E5C11603; Wed, 15 Mar 2006 12:08:04 +0100 (CET) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01476-06; Wed, 15 Mar 2006 12:07:57 +0100 (CET) Received: from mayday.esat.net (mayday.esat.net [193.95.134.156]) by smtp.xbsd.org (Postfix) with ESMTP id 3597C11494; Wed, 15 Mar 2006 12:07:56 +0100 (CET) From: Florent Thoumie To: Poul-Henning Kamp In-Reply-To: <22176.1142358505@critter.freebsd.dk> References: <22176.1142358505@critter.freebsd.dk> Content-Type: text/plain Date: Wed, 15 Mar 2006 11:07:55 +0000 Message-Id: <1142420875.823.39.camel@mayday.esat.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at xbsd.org Cc: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= , Christian Kratzer , Andre Oppermann , freebsd-arch@freebsd.org Subject: Re: Import src/sys/sys/hash.h from OpenBSD/NetBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 11:08:10 -0000 On Tue, 2006-03-14 at 18:48 +0100, Poul-Henning Kamp wrote: > In message <20060314184157.V10576@vesihiisi.cksoft.de>, Christian Kratzer writes: > > >> IMHO, Open{BGP,OSPF}D belong in src/contrib, not in ports/net. > > > >please don't bloat the base system with something that can run > >equally well from ports. > > I would tend to agree. > > 90% or more of all FreeBSD systems will not run either of these routing > daemons, so their rightful place is in ports. > > Also, considering the general hazzleness of src/contrib I think ports > offer a far more flexible infrastructure for dealing with the software > (such as openospfd-stable vs openospfd-cvs versions etc.) I'll add openbgpd-devel and openospfd-devel while this is being debated. There are pros and cons having them in src/, but in the meantime it will be available for people willing to test them. -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 14:11:25 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7E6816A400; Wed, 15 Mar 2006 14:11:25 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id E009C43D48; Wed, 15 Mar 2006 14:11:24 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5EAB2.dip.t-dialin.net [84.165.234.178]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k2FDr6QK053688; Wed, 15 Mar 2006 14:53:07 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k2FEAxgS062329; Wed, 15 Mar 2006 15:10:59 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Wed, 15 Mar 2006 15:10:58 +0100 Message-ID: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> X-Priority: 3 (Normal) Date: Wed, 15 Mar 2006 15:10:58 +0100 From: Alexander Leidinger To: Robert Watson References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> In-Reply-To: <20060315105031.E5861@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: arch@freebsd.org, hselasky@c2i.net Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 14:11:25 -0000 Robert Watson wrote: > The other large chunk of non-MPSAFE network device driver and stack > code, FYI, is the i4b code. In principle, a newly added committed is The USB stack is also a part of the problem (USB network interfaces), I think. > now available to work on the capi integration, and hopefully will do > the SMP safety work as part of that. If not, it's also on the > chopping block. It's a significant piece of otherwise unmaintained > code, and something that's not trivially testable (at least, not by > me or anyone I've talked to lately :-). I don't want to see it leave > the tree, but it needs to be updated so that it can run MPSAFE before > 7.0. I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have tested or reviewed neither of them, but as far as I can read in the mailinglists, he adresses not only the issues you mention here, but he also provides bugfixes and additional features compared to our current code base. References: - http://www.turbocat.net/~hselasky/isdn4bsd/index_ObjC_00.html - http://www.turbocat.net/~hselasky/usb4bsd/index_ObjA_00.html Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 November: The eleventh twelfth of a weariness. From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 15:11:27 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C857F16A505; Wed, 15 Mar 2006 15:11:27 +0000 (UTC) (envelope-from arch@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF37D43D49; Wed, 15 Mar 2006 15:11:18 +0000 (GMT) (envelope-from arch@dino.sk) Received: from lex ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Wed, 15 Mar 2006 16:11:25 +0100 id 00000457.44182E9D.000125C9 From: Milan Obuch To: freebsd-arch@freebsd.org Date: Wed, 15 Mar 2006 16:11:01 +0100 User-Agent: KMail/1.8.3 References: <25883.1142419646@critter.freebsd.dk> In-Reply-To: <25883.1142419646@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603151611.04172.arch@dino.sk> Cc: Poul-Henning Kamp , Robert Watson Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 15:11:27 -0000 On Wednesday 15 March 2006 11:47, Poul-Henning Kamp wrote: > In message <20060315104037.J5861@fledge.watson.org>, Robert Watson writes: > >> an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, > >> mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip > > When I last asked about interest in the mn driver, Milan Obuch said > that they were shipping current products based on this chip, but I > have not heard anything since. There is no replacement for mn driver, AFAIK, and that was my objection whe= n=20 phk asked for removal of mn sources. I have no idea what does it mean to=20 change this driver to be MPSAFE, but with some guidance I can try it.=20 Actually we are using somehow modified mn driver supporting both original=20 MUNICH based card with framer and X21 card based on MUNICH chip (special=20 design by Hungarian company, see http://www.itc.hu). =46rom the list mentioned above I would like to see plip driver kept in sou= rces=20 in the future too, I found it usefull couple of times already, when no othe= r=20 driver functioned, and for testing purposes as well. Regards, Milan From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 16:24:53 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D16816A41F; Wed, 15 Mar 2006 16:24:53 +0000 (UTC) (envelope-from arr@watson.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 132B543D53; Wed, 15 Mar 2006 16:24:52 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.13.4/8.13.4) with ESMTP id k2FGPiQD030742; Wed, 15 Mar 2006 11:25:44 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost) by fledge.watson.org (8.13.4/8.13.4/Submit) with ESMTP id k2FGPiig030739; Wed, 15 Mar 2006 11:25:44 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Wed, 15 Mar 2006 11:25:44 -0500 (EST) From: "Andrew R. Reiter" To: Harti Brandt In-Reply-To: <20060315091218.E56469@beagle.kn.op.dlr.de> Message-ID: <20060315112537.S54629@fledge.watson.org> References: <20060315004530.B5861@fledge.watson.org> <20060315091218.E56469@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: arch@freebsd.org, Robert Watson Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 16:24:53 -0000 Sorry to top post, but I worked on trying to mold the netatm code to the various more recently implemented APIs (UMA for example) awhile back and even then I was kinda thinking to myself "Im all for netgraph instead of netatm". So, I guess you see my stance on this :-). $0.02, Andrew On Wed, 15 Mar 2006, Harti Brandt wrote: :On Wed, 15 Mar 2006, Robert Watson wrote: : :RW> :RW>For some time now, the FreeBSD Project has been carrying around at least :RW>three ATM stacks: :RW> :RW>- netatm - HARP, the Host ATM Research Platform :RW> :RW>- netnatm - A fairly minimal socket<->virtual circuit ATM wrapper for ATM :RW> device drivers :RW> :RW>- ngatm - NetGraph ATM framework :RW> :RW>For a variety of reasons, it would be desirable to do a bit of pruning of ATM :RW>stacks. In my previous conversations with Harti and Bruce, the conclusion :RW>has generally been that ngatm and netnatm provide almost all functionality :RW>provided by netatm and more, but in modern, and actively maintained, :RW>frameworks. :RW> :RW>The main motivator for pruning has to do with the SMP network stack work: :RW>we're reaching the point, discussed on a number of occasions previously on :RW>this mailing list, where jettisoning unmaintained network stack components :RW>that are unable to run MPSAFE, is highly desirable. This would allow us to :RW>remove compatibility shims that are increasingly burdonsome in terms of :RW>performance and complexity. Another aspect of this has to do with upcoming :RW>changes to the socket and pcb code, which will require maintainers of :RW>protocols to do a small but non-trivial amount of work to update protocols to :RW>fit the new socket behavior. Right now, almost all other sections of the :RW>network stack have active maintainers who are able to do this work, both :RW>development and testing, except for the netatm code. :RW> :RW>We've reached the point where continuing to carry around a third ATM stack is :RW>a significant impediment to continued work on network stack performance and :RW>reliability work. This should not be a surprise to anyone who reads this :RW>mailing list regularly, since I sent out e-mail on this very topic on July :RW>18, 2005, warning that netatm (and several other components) were at risk as :RW>unmaintained but substantial network stack components. :RW> :RW>The proposal is as follows: :RW> :RW>In order to begin to merge revised socket/pcb code, required to fix a number :RW>of current races manifesting in the TCP code under load, and required for :RW>breaking out the tcbinfo lock which is a significant bottleneck in high :RW>performance TCP and multi-processor TCP scalability, I will disconnect netatm :RW>and dependent components from the build on April 1, 2006. At that point, I :RW>will merge updated socket and pcb reference counting. :RW> :RW>If a maintainer has not been found who can update and adequately test the :RW>netatm code for the new socket/pcb interfaces by June 30, 2006, the netatm :RW>code will be deleted from CVS HEAD (although remain available in Attic should :RW>someone turn up later). I'm happy to provide some first cut patches for any :RW>maintainer that arrives that do implement the changes, but I am unable to :RW>test them, and suspect they will be significant deficient for this reason, so :RW>will not commit them myself. :RW> :RW>This will leave us with at least two quite functional ATM implementations. :RW>Please let me know if netatm is critical to your work and you will be able to :RW>work with me to get netatm into shape. For someone already familiar with the :RW>netatm implementation and set up to perform ATM network testing, this should :RW>be straight forward and I'm happy to help in any way I can. If you are :RW>available to act in this role, my recommendation would be that we meet at :RW>BSDCan in Ottawa this May to discuss long term maintenance directions, and so :RW>that we can work out a plan for handling SMP behavior for netatm, as well as :RW>its integration with the socket code. : :I'm all for this removal. The only two reasons for carrying this around is :that it supports CLIP over SVCs and that the driver for the IDT77211 chips :is HARP-only. I have half of an ngatm driver for these chips and sent them :out two at least two people during the last two years, but never heard :back. I have also code for CLIP over SVCs but due to ENOTIME was not yet :able to make this commit ready. If anybody knows somebody who could finish :the driver it would be great. The CLIP stuff is not so critical - almost :all people use PVCs only. : :harti :_______________________________________________ :freebsd-arch@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-arch :To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" : : -- arr@watson.org From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 17:15:19 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD6B016A466; Wed, 15 Mar 2006 17:15:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AD1243D67; Wed, 15 Mar 2006 17:15:19 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2FHDbQm011534; Wed, 15 Mar 2006 10:13:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 10:13:39 -0700 (MST) Message-Id: <20060315.101339.45743485.imp@bsdimp.com> To: harti@freebsd.org, hartmut.brandt@dlr.de From: "M. Warner Losh" In-Reply-To: <20060315090615.I56469@beagle.kn.op.dlr.de> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315090615.I56469@beagle.kn.op.dlr.de> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 15 Mar 2006 10:13:39 -0700 (MST) Cc: arch@freebsd.org, rwatson@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:15:20 -0000 In message: <20060315090615.I56469@beagle.kn.op.dlr.de> Harti Brandt writes: : On Tue, 14 Mar 2006, Warner Losh wrote: : : WL>> The main motivator for pruning has to do with the SMP network stack work: : WL>> we're reaching the point, discussed on a number of occasions previously on : WL>> this mailing list, where jettisoning unmaintained network stack components : WL>> that are unable to run MPSAFE, is highly desirable. : WL> : WL>What's the timeline for non-MPSAFE network drivers to be taken out : WL>behind the woodshed? Right now the list appears to be: : WL> : WL> an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, : WL> mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip : : Both patm and fatm are MPSAFE - I forgot, maybe, to set the INTR_MPSAFE : flag. I'll fix that. I might have missed something when I came up with the list. Warner From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 17:30:35 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C3016A424; Wed, 15 Mar 2006 17:30:35 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 704A043D7E; Wed, 15 Mar 2006 17:30:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2FHT01N011656; Wed, 15 Mar 2006 10:29:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 10:29:03 -0700 (MST) Message-Id: <20060315.102903.08650855.imp@bsdimp.com> To: Alexander@Leidinger.net From: "M. Warner Losh" In-Reply-To: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> References: <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 15 Mar 2006 10:29:10 -0700 (MST) Cc: arch@freebsd.org, rwatson@freebsd.org, hselasky@c2i.net Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:30:35 -0000 In message: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> Alexander Leidinger writes: : Robert Watson wrote: : : > The other large chunk of non-MPSAFE network device driver and stack : > code, FYI, is the i4b code. In principle, a newly added committed is : : The USB stack is also a part of the problem (USB network interfaces), I : think. It definitely is a problem. And I didn't list any usb interfaces as not being MPSAFE. : > now available to work on the capi integration, and hopefully will do : > the SMP safety work as part of that. If not, it's also on the : > chopping block. It's a significant piece of otherwise unmaintained : > code, and something that's not trivially testable (at least, not by : > me or anyone I've talked to lately :-). I don't want to see it leave : > the tree, but it needs to be updated so that it can run MPSAFE before : > 7.0. : : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from : scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have : tested or reviewed neither of them, but as far as I can read in the : mailinglists, he adresses not only the issues you mention here, but he also : provides bugfixes and additional features compared to our current code base. The problem is that this code isn't busdma safe at the moment. It was posted for review on the NetBSD lists and this was the biggest set of comments on tech-kern@netbsd.org. Since it isn't busdma safe, we'd lose usb on sparc64 (and maybe arm) when this code is brought into the tree. There have also been signficant concerns about the locking that's done in the code as well, but I've not reviewed it recently. There's been a lot of work done here, and that work is generally good, but last time I looked at the code it wasn't ready to be integrated to the tree. Warner From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 17:58:20 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1BEA16A400; Wed, 15 Mar 2006 17:58:19 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 362D043D46; Wed, 15 Mar 2006 17:58:18 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5E1B4.dip.t-dialin.net [84.165.225.180]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k2FHeAm1054434; Wed, 15 Mar 2006 18:40:10 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k2FHw33g004405; Wed, 15 Mar 2006 18:58:04 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 15 Mar 2006 18:58:03 +0100 From: Alexander Leidinger To: "M. Warner Losh" Message-ID: <20060315185803.1956114c@Magellan.Leidinger.net> In-Reply-To: <20060315.102903.08650855.imp@bsdimp.com> References: <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> <20060315.102903.08650855.imp@bsdimp.com> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: arch@freebsd.org, rwatson@freebsd.org, hselasky@c2i.net Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:58:20 -0000 Am Wed, 15 Mar 2006 10:29:03 -0700 (MST) schrieb "M. Warner Losh" : > : > now available to work on the capi integration, and hopefully will do > : > the SMP safety work as part of that. If not, it's also on the > : > chopping block. It's a significant piece of otherwise unmaintained > : > code, and something that's not trivially testable (at least, not by > : > me or anyone I've talked to lately :-). I don't want to see it leave > : > the tree, but it needs to be updated so that it can run MPSAFE before > : > 7.0. > : > : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from > : scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have > : tested or reviewed neither of them, but as far as I can read in the > : mailinglists, he adresses not only the issues you mention here, but he also > : provides bugfixes and additional features compared to our current code base. > > The problem is that this code isn't busdma safe at the moment. It was > posted for review on the NetBSD lists and this was the biggest set of > comments on tech-kern@netbsd.org. Since it isn't busdma safe, we'd > lose usb on sparc64 (and maybe arm) when this code is brought into the > tree. There have also been signficant concerns about the locking > that's done in the code as well, but I've not reviewed it recently. > > There's been a lot of work done here, and that work is generally good, > but last time I looked at the code it wasn't ready to be integrated to > the tree. The questions are: - What's less work to do? - Is there someone who is willing to do the work? Bye, Alexander. -- The computer revolution is over. The computers won. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 18:06:41 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F42416A420; Wed, 15 Mar 2006 18:06:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87ED843D48; Wed, 15 Mar 2006 18:06:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2FI3GYv012066; Wed, 15 Mar 2006 11:03:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 11:03:18 -0700 (MST) Message-Id: <20060315.110318.39462847.imp@bsdimp.com> To: Alexander@Leidinger.net From: "M. Warner Losh" In-Reply-To: <20060315185803.1956114c@Magellan.Leidinger.net> References: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> <20060315.102903.08650855.imp@bsdimp.com> <20060315185803.1956114c@Magellan.Leidinger.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 15 Mar 2006 11:03:18 -0700 (MST) Cc: arch@freebsd.org, rwatson@freebsd.org, hselasky@c2i.net Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:06:41 -0000 In message: <20060315185803.1956114c@Magellan.Leidinger.net> Alexander Leidinger writes: : Am Wed, 15 Mar 2006 10:29:03 -0700 (MST) : schrieb "M. Warner Losh" : : : > : > now available to work on the capi integration, and hopefully will do : > : > the SMP safety work as part of that. If not, it's also on the : > : > chopping block. It's a significant piece of otherwise unmaintained : > : > code, and something that's not trivially testable (at least, not by : > : > me or anyone I've talked to lately :-). I don't want to see it leave : > : > the tree, but it needs to be updated so that it can run MPSAFE before : > : > 7.0. : > : : > : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from : > : scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have : > : tested or reviewed neither of them, but as far as I can read in the : > : mailinglists, he adresses not only the issues you mention here, but he also : > : provides bugfixes and additional features compared to our current code base. : > : > The problem is that this code isn't busdma safe at the moment. It was : > posted for review on the NetBSD lists and this was the biggest set of : > comments on tech-kern@netbsd.org. Since it isn't busdma safe, we'd : > lose usb on sparc64 (and maybe arm) when this code is brought into the : > tree. There have also been signficant concerns about the locking : > that's done in the code as well, but I've not reviewed it recently. : > : > There's been a lot of work done here, and that work is generally good, : > but last time I looked at the code it wasn't ready to be integrated to : > the tree. : : The questions are: : - What's less work to do? : - Is there someone who is willing to do the work? Agreed. Hans-Petter's work has great potential, but I think someone with a lot of time and knowledge of FreeBSD specific issues is going to need to work with him to properly integrate it into the tree. It isn't a drop in right now, but could be with some work. If usb abd usbHPS can co-exist in the tree, we might be able to do some of this in-tree. But usb is a very important subsystem and transitioning to a new code base is a high-risk thing. Warner From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 18:09:05 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D47A16A420; Wed, 15 Mar 2006 18:09:05 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8F1943D48; Wed, 15 Mar 2006 18:09:04 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2FI6vwH012153; Wed, 15 Mar 2006 11:06:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 11:06:56 -0700 (MST) Message-Id: <20060315.110656.112623113.imp@bsdimp.com> To: rwatson@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20060315104037.J5861@fledge.watson.org> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315104037.J5861@fledge.watson.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 15 Mar 2006 11:06:58 -0700 (MST) Cc: arch@FreeBSD.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 18:09:05 -0000 In message: <20060315104037.J5861@fledge.watson.org> Robert Watson writes: : Would it make sense : for us to set a similar set of date deadlines for non-MPSAFE drivers? I.e., : August 2006 for removing them from the build, and October, 2006, for remove : from the CVS HEAD? I suspect in that time several of the above will get : updated. I think this only makes sense if we can solve the usb issue in that time frame. We could make it the deadline for non-usb drivers. Warner From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 20:32:03 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6661D16A400; Wed, 15 Mar 2006 20:32:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from mail44.e.nsc.no (mail44.e.nsc.no [193.213.115.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE4DD43D45; Wed, 15 Mar 2006 20:32:02 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from acer-43b73db2a3.lan (ti131310a080-4379.bb.online.no [85.165.209.27]) by mail44.nsc.no (8.13.5/8.13.5) with ESMTP id k2FKVRKN008501; Wed, 15 Mar 2006 21:31:28 +0100 (CET) From: Hans Petter Selasky To: "M. Warner Losh" Date: Wed, 15 Mar 2006 21:31:44 +0100 User-Agent: KMail/1.7 References: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> <20060315185803.1956114c@Magellan.Leidinger.net> <20060315.110318.39462847.imp@bsdimp.com> In-Reply-To: <20060315.110318.39462847.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603152131.45806.hselasky@c2i.net> Cc: Alexander@leidinger.net, rwatson@freebsd.org, arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 20:32:03 -0000 Hi, Thanks for CC'ing me. I cannot subscribe to all the mailing lists around :-) On Wednesday 15 March 2006 19:03, M. Warner Losh wrote: > In message: <20060315185803.1956114c@Magellan.Leidinger.net> > > Alexander Leidinger writes: > : Am Wed, 15 Mar 2006 10:29:03 -0700 (MST) > : > : schrieb "M. Warner Losh" : > : > : > now available to work on the capi integration, and hopefully will > : > : > do the SMP safety work as part of that. If not, it's also on the > : > : > chopping block. It's a significant piece of otherwise unmaintained > : > : > code, and something that's not trivially testable (at least, not by > : > : > me or anyone I've talked to lately :-). I don't want to see it > : > : > leave the tree, but it needs to be updated so that it can run > : > : > MPSAFE before 7.0. > : > : > : > : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written > : > : from scratch it seems) for I4B (AFAIK including capi) and the USB > : > : stack. I have tested or reviewed neither of them, but as far as I can > : > : read in the mailinglists, he adresses not only the issues you mention > : > : here, but he also provides bugfixes and additional features compared > : > : to our current code base. > : > > : > The problem is that this code isn't busdma safe at the moment. It was > : > posted for review on the NetBSD lists and this was the biggest set of > : > comments on tech-kern@netbsd.org. Since it isn't busdma safe, we'd > : > lose usb on sparc64 (and maybe arm) when this code is brought into the > : > tree. There have also been signficant concerns about the locking > : > that's done in the code as well, but I've not reviewed it recently. Again, all USB drivers are driven like if 32-bit addressing is used. Actually the issue was about a function having "u_int32_t" as return type or "bus_size_t". I will change that. > : > > : > There's been a lot of work done here, and that work is generally good, > : > but last time I looked at the code it wasn't ready to be integrated to > : > the tree. Yes, right. I am still working on the USB system, but I am only one person, and I really could need some help. > : > : The questions are: > : - What's less work to do? > : - Is there someone who is willing to do the work? > > Agreed. Hans-Petter's work has great potential, but I think someone > with a lot of time and knowledge of FreeBSD specific issues is going > to need to work with him to properly integrate it into the tree. It > isn't a drop in right now, but could be with some work. > > If usb abd usbHPS can co-exist in the tree, we might be able to do > some of this in-tree. But usb is a very important subsystem and > transitioning to a new code base is a high-risk thing. I would suggest that we freeze "/sys/dev/usb" or make a copy of it. Then we [a few people] start moving all USB device drivers over to the new USB API, which will end up under "/sys/dev/usb2". Sure this can be in the tree. Then if people want to activate it, they have to run, maybe something like: cd /sys/dev/usb2 make package S=src.temp # maybe this is not needed if all the # files are in place make install Or we can just use my SVN account at turbocat.net. --HPS From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 22:02:13 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE4DA16A4B3; Wed, 15 Mar 2006 22:02:13 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37DCA43DF7; Wed, 15 Mar 2006 22:00:39 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 697C951A3A; Wed, 15 Mar 2006 23:00:00 +0100 (CET) Received: from localhost (dkj188.neoplus.adsl.tpnet.pl [83.24.13.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id DA234516FE; Wed, 15 Mar 2006 22:59:53 +0100 (CET) Date: Wed, 15 Mar 2006 22:59:15 +0100 From: Pawel Jakub Dawidek To: Robert Watson Message-ID: <20060315215915.GB16188@garage.freebsd.pl> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4bRzO86E/ozDv8r1" Content-Disposition: inline In-Reply-To: <20060315105031.E5861@fledge.watson.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 22:02:13 -0000 --4bRzO86E/ozDv8r1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 15, 2006 at 10:54:40AM +0000, Robert Watson wrote: +> Otherwise, with the exception of KAME IPSEC, the network stack code is a= ctually in pretty good shape for removing the Giant compat shims. We've ha= d at least a couple of=20 +> people say they're willing to work on this and take steps in the right d= irection (including some initial patches for IPSEC improvement), but I gues= s we'll see come August=20 +> whether it has happened. The discussion has always been about whether i= t's better to add IPv6 support to FAST_IPSEC, or lock down KAME IPSEC. Bot= h are desirable, and both=20 +> require significant familiarity with the code and protocols involved. Let me add my two cents. There are actually two things to do with KAME IPsec: MPSAFE and crypto(9) support and only one thing (IPv6) in case of fast_ipsec(4), so I think it will be much easier to add IPv6 support to fast_ipsec(4) and just drop KAME IPsec, so we can have one, full functional IPsec stack. This is really confusing for the users. When I first heard of fast_ipsec(4) I thought it only works with crypto HW and if I need to do cryptography in software I need KAME IPsec. But that's just an opinion of a passive observer:) --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --4bRzO86E/ozDv8r1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEGI4yForvXbEpPzQRAuNJAKCJp1AqWN4F9QsSPY3rkNwFwMA5LQCfRNx3 T9TlhIZqePaUpBJsOgzfJ68= =L8YU -----END PGP SIGNATURE----- --4bRzO86E/ozDv8r1-- From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 23:50:25 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2AE016A434 for ; Wed, 15 Mar 2006 23:50:25 +0000 (UTC) (envelope-from nogin@dbzmail.com) Received: from 1Cust32.VR1.DEN4.broadband.uu.net (1Cust32.VR1.DEN4.broadband.uu.net [63.13.205.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E73043D45 for ; Wed, 15 Mar 2006 23:50:22 +0000 (GMT) (envelope-from nogin@dbzmail.com) Received: from dbzmail.com (dbzmail-com-bk.mr.outblaze.com [64.62.181.91]) by 1Cust32.VR1.DEN4.broadband.uu.net (Postfix) with ESMTP id 3A92F2652D for ; Wed, 15 Mar 2006 18:47:06 -0500 From: Bufetov A.P. To: freebsd-arch Date: Wed, 15 Mar 2006 18:47:06 -0500 Message-ID: <110101c6488a$06b8b95d$daa0ea4a@dbzmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: base64 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Kaspersky-Antivirus: passed Subject: =?windows-1251?b?4iDu8uTl6yDv8O7k4OYsIPLl9e3u6+7j6P8gQ1JNIA==?= X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 23:50:26 -0000 zyDQIMAgyiDSIMgg1yDFINEgyiDIIMkgICAgINEgxSDMIMggzSDAINANCg0KIkNSTS4g09HS wM3OwsvFzcjFIMTOy8PO0dDO183b1SDO0s3O2MXNyMkg0SDKy8jFzdLAzMgiDQoNCjI4LTI5 IOzg8PLgIDIwMDag4+7k4CAo8SAxMC4wMCDk7iAxOC4wMCkNCi09LT0tPS09LT0tPS09LT0t PS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0tPS09LT0t PS09LT0tDQoNCsDz5Ojy7vDo/zog8PPq7uLu5Ojy5evoIO7y5OXr7uIg7/Du5ODmLCDu8uTl 6+7iIO/uIPDg4e7y5SDxIOrr6OXt8uDs6Cwg7OXt5eTm5fD7IO/uIO/w7uTg5uDsLg0KDQrO 0c3Owtsg0sXO0MjIIMggz9DAytLIysigIENSTSAo8uX17e7r7uPo/yDu5O3o7CDi5+Pr/+Tu 7CkNCjEuIM7w4+Dt6Ofg9uj/IO/w7uTg5iwg/fLg7/sg7/Du5ODmIC0g4evu6i3x9eXs4CAo 4O3g6+jy6Pfl8ero6SD98uDvIC0g7vDj4O3o5+D26P8g6uvo5e3y8eru6SDh4Of7IOgg7/Du 5PPq8uA7IP309OXq8uji7eD/IO/w5efl7fLg9uj/OyDn4Orr/vfl7ejlIPHk5evq6Dsg4eXx 6u7t5fft4P8g8eTl6+rgLCDi5eTl7ejlIOgg7+Xw5eTg9+Ag6uvo5e3y4CkuDQoyLiDR8vDz 6vLz8OAg6CDy5fXt6OrgIO/u8fLw7uXt6P8gweDn+yDE4O3t+/UgKMHEKSAo8fLw8+ry8/Dg IMHELCDq4PDy7vfq4CDq6+jl7fLgLCDn4O/o8egg6CDv7uv/LCDv5fDl9+Xt/CDv7uvl6Tsg 8uX17ejq4CD07vDs6PDu4uDt6P8gwcQsIODq8vPg6+jn4Pbo/yDBxDsg4vXu5O3g/yDg7erl 8uAg5Ov/IPTu8Ozo8O7i4O3o/yDBxCkuDQozLiDI8e/u6/zn7uLg7ejlIMrr6OXt8vHq7ukg 4eDn+yDiIPLl9e3u6+7j6OggQ1JNICjy5fXt7uvu4+j/IOru7fLg6vLu4iAtINLHIOTr/yDx 7ufk4O3o/yDBxDsg9uXr6CDq7u3y4Ory7uI7IPP35fIsIODt4Ovo5ywg/fT05ery6OLt7vHy /CDq7u3y4Ory7uI7IPHy8ODy5ePo6CDq7uzs8+3o6uD26OkpLg0KDQrP0N/M28Ugz9DOxMDG yDogztDDwM3Ix8DWyN8gyCDKzs3S0M7L3A0KMS4g0ODh7vLgIOru7fLg6vLt+/Ug7OXt5eTm 5fDu4i4NCjIuIM/r4O3o8O7i4O3o5Swg7vDj4O3o5+D26P8g6CDq7u3y8O7r/CDv8O7k4OYu DQozLiDO8OPg7ejn4Pbo/yDq7uzg7eTt7uPuIOjx7+7r/Ofu4uDt6P8gwcQg4iDk5f/y5ev8 7e7x8ugg7OXt5eTm5fDu4iDv7iDv8O7k4Obg7C4NCjQuIM725e3q4CDx8u7o7O7x8ugg6u7s 7PPt6Org9ujpLg0KNS4gyO3x8vDz7OXt8uDw6Ogg7vDj4O3o5+D26Ogg6CDq7u3y8O7r/yDs 5e3l5Obl8O7iLg0KDQrP0MDK0sjKwCDKzs3SwMrSzsI6IOvo9+3g/yDv8OXn5e3y4Pbo/ywg 8uXr5fTu7e376SDoIP3v6PHy7uv/8O376SDq7u3y4OryLiDO7/Lo7ODr/O375SDx9uXt4PDo 6CDq7u3y4Ory7uIuDQoNCs/QzsPQwMzM2yDTwsXLyNfFzcjfIMvO38vczc7R0sggz87S0MXB yNLFy8XJIMggQ1JNDQoxLiDM7uTl6+gg8eXw4ujx7e7j7iD26Orr4Cwg5O7i7uv87fvlIOgg 7eXk7uLu6/zt++Ug6uvo5e3y+y4NCjIuIN3q7u3u7Oj35fHq4P8g/fT05ery6OLt7vHy/CDz 4uXr6Pfl7ej/IOvu/+v87e7x8uguDQozLiDM5fLu5Ojq4CBDUk0sIO/u8fLw7uXt6OUg8/Hy 7un36OL79SDu8u3u+OXt6Okg8SDq6+jl7fLg7OguDQoNCt3SwM/bIMjRz87L3MfOwsDNyN8g 0sXVzc7LzsPIyCBDUk0NCjEuIM7x7uHl7e3u8fLoIENSTS3v8O7j8ODs7C4NCjIuIM7x7uHl 7e3u8fLoIOjx7+7r/Ofu4uDt6P8g5Ojx6u7t8u379SDv8O7j8ODs7C4NCjMuINDg5+vo9+j/ IOTo8eru7fLt+/Ug7/Du4/Dg7Owg6CDy5fXt7uvu4+jpIENSTS4NCg0Kz9DIzMXQ2yDQxcDL 3M3OySDO0MPAzcjHwNbIyCDP0M7D0MDMzCBDUk0uINLF1c3IysAgz87R0tDOxc3I3yDO0s3O 2MXNyMkg0SDKy8jFzdLAzMgNCjEuIMru8O/u8ODy6OLt4P8g6vPr/PLz8OAgKO7x7e7i+yDg 7eDr6OfgKS4NCjIuINPx8uDt7uLr5e3o5SDq7u3y4Ory7uIgKOru7fLg6vLt++Ug7+7i7uT7 KS4NCjMuINHv7vHu4fsg7+7x8vDu5e3o/yDu8u3u+OXt6OkuIM7w4+Dt6Ofg9uj/IOgg8+/w 4OLr5e3o5SDv7vHy8O7l7ejl7CDu8u3u+OXt6OkuDQoNCsIg8OXn8+v88uDy5SDx5ezo7eDw 4CDz9+Dx8u3o6ug6DQoNCjEuIM/u6/P34PIg6O3x8vDz7OXt8vsg8ODh7vL7IPEg6uvo5e3y 8eru6SDh4Ofu6TsNCjIuIM/u6/P34PIg7/Dl5PHy4OLr5e3o5SDuIO/w4OLo6/zt7ukg8ODh 7vLlIPEg6uvo5e3y4OzoIOgg8e/u8e7h4PUg7+7i+/jl7ej/IOvu/+v87e7x8ugg6uvo5e3y 7uINCuru7O/g7ejoOw0KMy4g0+ft4P7yIO4g4+vg4u379SDv8Ojt9ujv4PUg7+7x8vDu5e3o /yD99PTl6vLo4u3u6SDB4Of7IMTg7e379SDoIPHs7uPz8iDw5eDr6Ofu4uDy/CD98ugg5+3g 7ej/IO3gIPHi7uj1IPDg4e736PUg7OXx8uD1Lg0KDQo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCsDi8u7w IPHl7Ojt4PDgOiDR4Ozu9ejtIMwu3i4gLSDv8O705fHx6O7t4Ov87fvpIOHo5+3l8S3y8OXt 5fAsIOru7fHz6/zy4O3yLCDs4PDq5fLu6+7jLCDg4vLu8CDw4Ofw4OHu8u7qIOIg7uHr4PHy 6CDg6vLo4u379SDs5fLu5O7iIO7h8/fl7ej/LCDv8OXv7uTg4uDy5ev8IMDN1Swg0ejt5fDj 6P8gKMzCwCksIMzI0MHI0SAozMLAKSwgwsrYLCDN7vDi5ebx6u4t0O7x8ejp8eru4+4g7uHw 4Ofu4uDy5ev87e7j7iDv8O7l6vLgIFNrZWRzbW8uINDz6u7i7uTo8uXr/CDg7eDr6PLo9+Xx 6u7pIOPw8+/v+yAo7ODw6uXy6O3j7uL75SDo8fHr5eTu4uDt6P8pLCDg4vLu8CDv8+Hr6Org 9ujpIOIg7uHr4PHy6CDz7/Dg4uvl7ej/IO/w7uXq8uDs6Cwg4fDl7eTo7ePgIOggQ1JNLiDN 5eru8u7w++Ug6u7w7+7w4PLo4u375SDq6+jl7fL7OiDS6O386u709CwgzOjr4OPw7iwgTGUg Q2FmZSwgxeLw7u7p6ywgxOjg8e708iwgwPDs7i3j8PPvLCBBc3N0cmEgKMHl6+Dw8/H8KSwg weXr/evl6vLw7u3q7uzv6+Xq8iAoweXr4PDz8fwpLCDR4PXg6+jtIN3t5fDk5uggKOru7fHu 8Pbo8+wgU2hlbGwsIE1pdHN1aSwgTWl0c3ViaXNpKSwgzOjw8OAgy/7q8Swgw+Dw4O3yLCDR 5fL8IPHg6+7t7uIg1ODh8Ojq4CDD8OXnIiwgyuDs7+7s7vEsINfl8Oro5+7i7iwgzO7x6u7i 8ero6SDY6O3t++kgx+Di7uQsIMzg6vHo8iAowuXy7u3o8iksIMT/8vzq7uLuLezl4eXr/Cwg 6Ofk4PLl6/zx8uLuIE1hY01pbGxhbiAo8O7x8ejp8ero6SDu9OjxKSwgzMjdy9wt7eXk4ujm 6Ozu8fL8LCDS7vDj7uL76SDk7uwgy+Di5fDt4Cwg0ejh8/Ag6CDk8PPj6OUg6u7s7+Dt6Ogu DQoNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09DQrR8u7o7O7x8vwg8/fg8fLo/zogODI2MCDw8+EuICjxIPP3 5fLu7CDNxNEpDQoNCsIg8fLu6Ozu8fL8IOLq6/735e37IODi8u7w8ero5SDw4Ofk4PLu9+37 5SDs4PLl8Ojg6/ssIOru9OUt4fDl6eroLCDu4eXkLg0K0ero5OroOiDh7uvl5SDu5O3u4+4g 8/fg8fLt6OrgIO7yIOru7O/g7ejoIC0g8ero5OrgIDEwJSwg7+7x8u7/7e377CDq6+jl7fLg 7CAtIDIwJS4NCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PQ0K0c/QwMLKyKAgyKAg0MXDyNHS0MDWyN8g7+4g 8uXrLjogWzQ5NV0gOTgwLTY3LTAwDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KZjJLbXA= From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 02:52:58 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F99C16A401; Thu, 16 Mar 2006 02:52:58 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7573E43D6D; Thu, 16 Mar 2006 02:52:54 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FJibX-0000Un-GP; Thu, 16 Mar 2006 02:52:47 +0000 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 478B665499; Thu, 16 Mar 2006 02:52:53 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26066-04; Thu, 16 Mar 2006 02:52:52 +0000 (GMT) Received: by arginine.spc.org (Postfix, from userid 1078) id 5499D653F9; Thu, 16 Mar 2006 02:52:52 +0000 (GMT) Date: Thu, 16 Mar 2006 02:52:52 +0000 From: Bruce M Simpson To: Harti Brandt Message-ID: <20060316025252.GB11850@spc.org> References: <20060315004530.B5861@fledge.watson.org> <20060315091218.E56469@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060315091218.E56469@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: arch@FreeBSD.org, Robert Watson Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 02:52:58 -0000 On Wed, Mar 15, 2006 at 09:18:01AM +0100, Harti Brandt wrote: > I'm all for this removal. The only two reasons for carrying this around is > that it supports CLIP over SVCs and that the driver for the IDT77211 chips > is HARP-only. I have half of an ngatm driver for these chips and sent them > out two at least two people during the last two years, but never heard > back. I have also code for CLIP over SVCs but due to ENOTIME was not yet > able to make this commit ready. If anybody knows somebody who could finish > the driver it would be great. The CLIP stuff is not so critical - almost > all people use PVCs only. I am one such guilty party. Sadly my time has been completely consumed. I second the removal of netatm. BMS From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 08:05:46 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0338116A424 for ; Thu, 16 Mar 2006 08:05:46 +0000 (UTC) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-174-86.sn2.eutelia.it [83.211.174.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A00543D4C for ; Thu, 16 Mar 2006 08:05:43 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 1F3532C90B for ; Thu, 16 Mar 2006 09:05:41 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 560692C90A; Thu, 16 Mar 2006 09:05:40 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 291A62C906; Thu, 16 Mar 2006 09:05:40 +0100 (CET) From: Massimo Lusetti To: Pawel Jakub Dawidek In-Reply-To: <20060315215915.GB16188@garage.freebsd.pl> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315215915.GB16188@garage.freebsd.pl> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 16 Mar 2006 09:05:40 +0100 Message-Id: <1142496340.4311.12.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: arch@freebsd.org, Robert Watson Subject: KAME/Fast IPSEC (was Re: netatm: plan for removal unless an active maintainer is found) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 08:05:46 -0000 On Wed, 2006-03-15 at 22:59 +0100, Pawel Jakub Dawidek wrote: > Let me add my two cents. There are actually two things to do with KAME > IPsec: MPSAFE and crypto(9) support and only one thing (IPv6) in case of > fast_ipsec(4), so I think it will be much easier to add IPv6 support to > fast_ipsec(4) and just drop KAME IPsec, so we can have one, full > functional IPsec stack. > > This is really confusing for the users. When I first heard of > fast_ipsec(4) I thought it only works with crypto HW and if I need to do > cryptography in software I need KAME IPsec. > > But that's just an opinion of a passive observer:) I also would like to see more clearness on this, Pawel is right saying it's a confusing situation. Ciao -- Massimo There are more way to do things, one is the bsd-way the others are wrong From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 08:40:13 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86DC916A434; Thu, 16 Mar 2006 08:40:13 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E101743D46; Thu, 16 Mar 2006 08:40:12 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 191ED2000C2; Thu, 16 Mar 2006 09:40:10 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 650D32000B2; Thu, 16 Mar 2006 09:40:07 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7A962444F41; Thu, 16 Mar 2006 08:36:20 +0000 (UTC) Date: Thu, 16 Mar 2006 08:36:19 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Massimo Lusetti In-Reply-To: <1142496340.4311.12.camel@massimo.datacode.it> Message-ID: <20060316082738.W2181@maildrop.int.zabbadoz.net> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315215915.GB16188@garage.freebsd.pl> <1142496340.4311.12.camel@massimo.datacode.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: arch@freebsd.org, Robert Watson , Pawel Jakub Dawidek Subject: Re: KAME/Fast IPSEC (was Re: netatm: plan for removal unless an active maintainer is found) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 08:40:13 -0000 On Thu, 16 Mar 2006, Massimo Lusetti wrote: Hi, > On Wed, 2006-03-15 at 22:59 +0100, Pawel Jakub Dawidek wrote: > >> Let me add my two cents. There are actually two things to do with KAME >> IPsec: MPSAFE and crypto(9) support and only one thing (IPv6) in case of >> fast_ipsec(4), so I think it will be much easier to add IPv6 support to >> fast_ipsec(4) and just drop KAME IPsec, so we can have one, full >> functional IPsec stack. >> >> This is really confusing for the users. When I first heard of >> fast_ipsec(4) I thought it only works with crypto HW and if I need to do >> cryptography in software I need KAME IPsec. >> >> But that's just an opinion of a passive observer:) > > I also would like to see more clearness on this, Pawel is right saying > it's a confusing situation. with hopefully enough time this problem will be solved during the year. This will also need some netinet6 work,... What you can find at http://sources.zabbadoz.net/freebsd/ipv6/ is far from being complete or fully up-to-date but it's a start... -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 10:42:18 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8970B16A425; Thu, 16 Mar 2006 10:42:18 +0000 (UTC) (envelope-from liladude@aruba.it) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BED943D53; Thu, 16 Mar 2006 10:42:15 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp3.tin.it (7.2.072.1) id 4416D3E0001A687B; Thu, 16 Mar 2006 11:43:05 +0100 Message-ID: <44194122.2010100@aruba.it> Date: Thu, 16 Mar 2006 11:42:42 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John Baldwin References: <44140E09.3000203@aruba.it> <200603140818.09838.jhb@freebsd.org> <4417B560.3080609@aruba.it> <200603150847.29175.jhb@freebsd.org> In-Reply-To: <200603150847.29175.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 10:42:18 -0000 John Baldwin ha scritto: > > Patching the module should be fine. Can you provide the output of dmesg > after you have kldloaded the module? Also, did the patch apply cleanly > or where there any rejects? And, what version are you testing this on? I finally managed to build and install my kernel with patched drivers. I'm working with FreeBSD 6.0-out-of-the-box (waiting for ethernet before I can Patch applied with no problem to both files. I'm sorry but my kernel with no ethernet was unstable, so I could not get a dmesg when I kloaded if_de (it only worked once...) Now the output when I insert my etherenet card (or I boot with card inserted) is this: TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: d11302ab Functions: Network Adaptor, Memory Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Product version: 5.0 Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 | | TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00 cardbus0: Opening BAR: type=IO, bar=10, len=0100 cardbus0: Opening BAR: type=MEM, bar=14, len=0400 CIS reading done cardbus0: Non-prefetchable memory at 88000000-880003ff cardbus0: IO port at 1000-10ff found-> vendor=0x1186, dev=0x1561, revid=0x11 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 dc0: port 0x1000-0x10ff mem 0x88000000-0x880003ff irq 10 at device 0.0 on cardbus0 dc0: MII without any PHY! device_attach: dc0 attach returned 6 I'm googling the "MII without any PHY" problem but haven't found a solution right now. thanks a lot for your attention. Lila From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 14:00:46 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DBC416A439 for ; Thu, 16 Mar 2006 14:00:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8404243D5A for ; Thu, 16 Mar 2006 14:00:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2GE0ciZ045961; Thu, 16 Mar 2006 09:00:38 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Lila Date: Thu, 16 Mar 2006 09:00:36 -0500 User-Agent: KMail/1.8.3 References: <44140E09.3000203@aruba.it> <200603150847.29175.jhb@freebsd.org> <44194122.2010100@aruba.it> In-Reply-To: <44194122.2010100@aruba.it> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603160900.37266.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 14:00:46 -0000 On Thursday 16 March 2006 05:42 am, Lila wrote: > John Baldwin ha scritto: > > Patching the module should be fine. Can you provide the output of dmesg > > after you have kldloaded the module? Also, did the patch apply cleanly > > or where there any rejects? And, what version are you testing this on? > > I finally managed to build and install my kernel with patched drivers. > I'm working with FreeBSD 6.0-out-of-the-box (waiting for ethernet before > I can > Patch applied with no problem to both files. > I'm sorry but my kernel with no ethernet was unstable, so I could not > get a dmesg when I kloaded if_de (it only worked once...) > Now the output when I insert my etherenet card (or I boot with card > inserted) is this: > > TUPLE: LINKTARGET [3]: 43 49 53 > Manufacturer ID: d11302ab > Functions: Network Adaptor, Memory > Function Extension: 0102 > Function Extension: 0280969800 > Function Extension: 0200e1f505 > Function Extension: 0301 > Product version: 5.0 > Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 | | > TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00 > cardbus0: Opening BAR: type=3DIO, bar=3D10, len=3D0100 > cardbus0: Opening BAR: type=3DMEM, bar=3D14, len=3D0400 > CIS reading done > cardbus0: Non-prefetchable memory at 88000000-880003ff > cardbus0: IO port at 1000-10ff > found-> vendor=3D0x1186, dev=3D0x1561, revid=3D0x11 > bus=3D2, slot=3D0, func=3D0 > class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 > cmdreg=3D0x0000, statreg=3D0x0290, cachelnsz=3D8 (dwords) > lattimer=3D0xa8 (5040 ns), mingnt=3D0xff (63750 ns), maxlat=3D0xff (6375= 0 ns) > intpin=3Da, irq=3D10 > powerspec 2 supports D0 D1 D2 D3 current D0 > dc0: port 0x1000-0x10ff mem > 0x88000000-0x880003ff irq 10 at device 0.0 on cardbus0 > dc0: MII without any PHY! > device_attach: dc0 attach returned 6 > > I'm googling the "MII without any PHY" problem but haven't found a > solution right now. > thanks a lot for your attention. > Lila I think I see it. In the Linux driver they treat all the ADMTek cards the same (as COMET). In dc(4), the ADMTek cards are split into two classes: the AL981 and the AN985. All the extra rebadge IDs are for the AN985, but I treated your card as an AL981 when it is probably an AN985. I just updated the patch at=20 http://www.FreeBSD.org/~jhb/patches/drp-32txd.patch. Please try the newer= =20 patch and let me know if it works. Thanks! =2D-=20 John Baldwin =C2=A0<>< =C2=A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =C2=A0=3D =C2=A0http://www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 18:56:27 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3CC716A41F; Thu, 16 Mar 2006 18:56:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from mail49.e.nsc.no (mail49.e.nsc.no [193.213.115.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA6C43D45; Thu, 16 Mar 2006 18:56:26 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from acer-43b73db2a3.lan (ti131310a080-4379.bb.online.no [85.165.209.27]) by mail49.nsc.no (8.13.5/8.13.5) with ESMTP id k2GIuLda003255; Thu, 16 Mar 2006 19:56:22 +0100 (CET) From: Hans Petter Selasky To: "M. Warner Losh" Date: Thu, 16 Mar 2006 19:56:37 +0100 User-Agent: KMail/1.7 References: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> <20060315.110318.39462847.imp@bsdimp.com> <200603152131.45806.hselasky@c2i.net> In-Reply-To: <200603152131.45806.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161956.39299.hselasky@c2i.net> Cc: Alexander@leidinger.net, rwatson@freebsd.org, arch@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 18:56:27 -0000 On Wednesday 15 March 2006 21:31, Hans Petter Selasky wrote: > Hi, I have tested my ISDN4BSD driver on a Sparc64 using NetBSD, and the driver that is in SVN works. Not the one I released. That means all alignment and endian issues have been resolved, and I now better understand how to write portable code. However I would also like to test on a Sparc64 using FreeBSD 6.1? Anyone that wants to do some testing or debugging for me? --HPS From owner-freebsd-arch@FreeBSD.ORG Thu Mar 16 19:32:36 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1E16A400; Thu, 16 Mar 2006 19:32:36 +0000 (UTC) (envelope-from liladude@aruba.it) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF0D743D83; Thu, 16 Mar 2006 19:32:32 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp3.tin.it (7.2.072.1) id 4416D3E00021AE49; Thu, 16 Mar 2006 20:33:23 +0100 Message-ID: <4419BD72.30207@aruba.it> Date: Thu, 16 Mar 2006 20:33:06 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John Baldwin References: <44140E09.3000203@aruba.it> <200603150847.29175.jhb@freebsd.org> <44194122.2010100@aruba.it> <200603160900.37266.jhb@freebsd.org> In-Reply-To: <200603160900.37266.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 19:32:36 -0000 Took me some time to recompile patched drivers, but that was the thing! Now it works fine, I'm going to download all fixes for 6.0 asap! Thanks a lot. Lila John Baldwin ha scritto: > > I think I see it. In the Linux driver they treat all the ADMTek cards > the same (as COMET). In dc(4), the ADMTek cards are split into two > classes: the AL981 and the AN985. All the extra rebadge IDs are for > the AN985, but I treated your card as an AL981 when it is probably an > AN985. I just updated the patch at > http://www.FreeBSD.org/~jhb/patches/drp-32txd.patch. Please try the newer > patch and let me know if it works. Thanks! > From owner-freebsd-arch@FreeBSD.ORG Fri Mar 17 02:32:44 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FA2616A400; Fri, 17 Mar 2006 02:32:44 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A8D043D45; Fri, 17 Mar 2006 02:32:44 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id k2H2VpJt027086; Thu, 16 Mar 2006 18:31:52 -0800 (PST) Date: Fri, 17 Mar 2006 10:28:09 +0900 Message-ID: From: "George V. Neville-Neil" To: "Bjoern A. Zeeb" In-Reply-To: <20060316082738.W2181@maildrop.int.zabbadoz.net> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315215915.GB16188@garage.freebsd.pl> <1142496340.4311.12.camel@massimo.datacode.it> <20060316082738.W2181@maildrop.int.zabbadoz.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: arch@freebsd.org, Massimo Lusetti , Robert Watson , Pawel Jakub Dawidek Subject: Re: KAME/Fast IPSEC (was Re: netatm: plan for removal unless an active maintainer is found) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 02:32:44 -0000 At Thu, 16 Mar 2006 08:36:19 +0000 (UTC), Bjoern A. Zeeb wrote: > with hopefully enough time this problem will be solved during > the year. This will also need some netinet6 work,... > > What you can find at > http://sources.zabbadoz.net/freebsd/ipv6/ > is far from being complete or fully up-to-date but it's a start... > Sorry to chime in late, server upgrade. We (Bjoern, myself and a few others) are actively working on this. I am working first to make the system work in this way: 1) INET6: Kame IPv6, no IPSec 2) INET6 + IPSEC: Pure Kame IPv6 and IPSec 3) FAST_IPSEC: v4 Fast IPSec 4) INET6 + FAST_IPSEC: Kame v6 + FAST IPsec v4 and v6 That is we will be able to use Kame IPv6 with either Kame IPSec or FAST_IPSEC. The long term goal is to have only one set of code for IPv6 and for IPSec, but that is going to take a bit more work. I have started the changes to make 4 possible in a p4 branch. For those with access look at branches marked fast_ipsec. I want to do a lot of testing on this before putting it into CVS and even though there is the TAHI test framework testing takes a while and I want to try this with some more complex real networks. Help, of course, is always appreciated ;-) If anyone wants to be on my "little list of concerned parties" send me your email and I'll try to send out regular patches and mails. Later, George From owner-freebsd-arch@FreeBSD.ORG Fri Mar 17 11:43:54 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C8D516A401; Fri, 17 Mar 2006 11:43:54 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6E8D43D46; Fri, 17 Mar 2006 11:43:42 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:E+wAIlnJinQ0Zk0pbutn64gu/09N4tBuCg/2uhHLUz3Ugl84bZ/I8va7T9HAaErY@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id k2HBhZmK024692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Mar 2006 20:43:38 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 17 Mar 2006 20:43:34 +0900 Message-ID: From: Hajimu UMEMOTO To: arch@FreeBSD.org, current@FreeBSD.org In-Reply-To: References: User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.1) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.1-PRERELEASE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.1.3 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Fri, 17 Mar 2006 20:43:38 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: Subject: Re: [CFR] Upgrading base version of our resolver in libc to BIND9 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 11:43:54 -0000 Hi, >>>>> On Tue, 14 Mar 2006 02:08:50 +0900 >>>>> Hajimu UMEMOTO said: ume> I wish to upgrade the base version of our resolver in libc to BIND9's ume> one. I updated the patches: - merged our local changes more. - defined some IPv6 related definitions. - thread-safeness for mtctxres which is used from res_debug. - upgraded the base version of inet_*(3) to BIND9's one as well. - re-made the patch against latest HEAD. The patches are: http://www.imasy.or.jp/~ume/FreeBSD/libc-bind9-7c-20060317.diff.gz (for HEAD as of today) http://www.imasy.or.jp/~ume/FreeBSD/libc-bind9-6s-20060317.diff.gz (for RELENG_6 as of today) You need to remove some obsolete files. Please refer the instruction written in the head of the patch. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/