From owner-freebsd-current@FreeBSD.ORG  Wed Mar  5 05:30:56 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3EFF3106566B;
	Wed,  5 Mar 2008 05:30:56 +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 DB2548FC17;
	Wed,  5 Mar 2008 05:30:55 +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 m255UBeB079895;
	Tue, 4 Mar 2008 22:30:11 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Tue, 04 Mar 2008 22:30:40 -0700 (MST)
Message-Id: <20080304.223040.195748645.imp@bsdimp.com>
To: grehan@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <47CE2BA1.8000505@freebsd.org>
References: <47CE2BA1.8000505@freebsd.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: freebsd-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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2008 05:30:56 -0000

In message: <47CE2BA1.8000505@freebsd.org>
            Peter Grehan <grehan@freebsd.org> writes:
: Hi Warner,
: 
:  >The other way to fix this is to return a better value from the probe
:  >routine for those devices that attach to the nexus.
:    ...
:  >Comments?
: 
:   Looks good to me, and is a whole lot better than the previous 
: suggestion :)

This seems safer too...  For me it was a toss up between this method
and having a new call to newbus asking if the device was a wildcard or
not.

Warner