From owner-freebsd-net@FreeBSD.ORG Mon Nov 17 07:44:25 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA3C9F15 for ; Mon, 17 Nov 2014 07:44:25 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A6CDC42 for ; Mon, 17 Nov 2014 07:44:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id sAH7i9EC063099; Mon, 17 Nov 2014 18:44:10 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 17 Nov 2014 18:44:09 +1100 (EST) From: Ian Smith To: John-Mark Gurney Subject: Re: Whither ep(4) on 9.3-RELEASE? In-Reply-To: <20141111211530.GQ24601@funkthat.com> Message-ID: <20141113233208.G31139@sola.nimnet.asn.au> References: <20141111203429.I31139@sola.nimnet.asn.au> <20141111211530.GQ24601@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Gary Aitken , freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 07:44:26 -0000 On Tue, 11 Nov 2014 13:15:30 -0800, John-Mark Gurney wrote: > Ian Smith wrote this message on Tue, Nov 11, 2014 at 21:31 +1100: [..] > > So can anyone confirm that ep(4) is present on 9.3-R, even if only i386? > > Yeh, it looks like ep is in GENERIC on i386.. We also compile ep on > amd64 too, though not sure anyone would ever want to use ep on there... > > On HEAD we only compile the ep modules on i386... so not sure why you > weren't able to find it... 'cos I was relying on the hardware compatibility lists for all versions mentioned, and man.cgi - before and after discovering the 'Default' arch doesn't mean default arch for a given component, but needed searching by just i386 - but those are just docs/web issues, 'scuse the noise here. > I'd just try booting a memstick or other image to confirm that there > is support... So would I, for everything on board .. Thanks, and to Darren and Julian also. cheers, Ian "My friends all drive Xeons, I must make amends." -- janis joytest(6)