From owner-freebsd-current@FreeBSD.ORG Tue Mar 4 16:10:20 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E91F31065679; Tue, 4 Mar 2008 16:10:20 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 434018FC19; Tue, 4 Mar 2008 16:10:20 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m24G7DsB071798; Tue, 4 Mar 2008 09:07:13 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 04 Mar 2008 09:07:41 -0700 (MST) Message-Id: <20080304.090741.-1631526462.imp@bsdimp.com> To: dfr@rabson.org From: "M. Warner Losh" In-Reply-To: <57AF36D8-0F83-4DF8-BEAA-CF3B59EAA361@rabson.org> References: <9299FBBE-F58A-4107-991D-1C851EB8802C@rabson.org> <20080304.083606.-1253045570.imp@bsdimp.com> <57AF36D8-0F83-4DF8-BEAA-CF3B59EAA361@rabson.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: gnn@freebsd.org, xcllnt@mac.com, re@freebsd.org, current@freebsd.org Subject: Re: IPSEC/crypto is broken in FreeBSD/powerpc 7.0-RELEASE! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 16:10:21 -0000 In message: <57AF36D8-0F83-4DF8-BEAA-CF3B59EAA361@rabson.org> Doug Rabson writes: : : On 4 Mar 2008, at 15:36, M. Warner Losh wrote: : : > In message: <9299FBBE-F58A-4107-991D-1C851EB8802C@rabson.org> : > Doug Rabson writes: : > : I can't see the code which adds this device on a first look. Can you : > : tell me the filename and I'll take a quick look at it. : > : > The problem actually turns out to be in how the powerpc nexus does : > things. It does them in a very un-nexus-like way. The nexus attached : > drivers ask for hardware details, which isn't done elsewhere. This : > means when you mix and match the ones that expect to be explicitly set : > and the ones that don't that you run into trouble. : > : > This needs to be reworked. : : Perhaps the crypto stuff should add itself to root0 instead of nexus. I think that would cause other problems... Warner