From owner-freebsd-current@FreeBSD.ORG  Fri Oct  3 15:58:13 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D8F5D16A4C0; Fri,  3 Oct 2003 15:58:12 -0700 (PDT)
Received: from smtp-out3.iol.cz (smtp-out3.iol.cz [194.228.2.91])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7181C43FBF; Fri,  3 Oct 2003 15:57:56 -0700 (PDT)
	(envelope-from dan@obluda.cz)
Received: from obluda.cz (gprs176-166.eurotel.cz [160.218.176.166])
	by smtp-out3.iol.cz (Internet on Line ESMP server) with ESMTP
	id 39B5B350FC; Sat,  4 Oct 2003 00:58:44 +0200 (CEST)
Message-ID: <3F7DFEE7.4060804@obluda.cz>
Date: Sat, 04 Oct 2003 00:57:43 +0200
From: Dan Lukes <dan@obluda.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624
X-Accept-Language: cs, sk, en
MIME-Version: 1.0
To: ivan.dolezal@vsb.cz
References: <3F7D52A5.9070406@vsb.cz>
	<Pine.SOL.4.58-Blink.0310031350360.6638@tea.blinkenlights.nl>
	<3F7D8B1C.5010000@vsb.cz>
In-Reply-To: <3F7D8B1C.5010000@vsb.cz>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
cc: FreeBSD mailing list <users-l@freebsd.cz>
cc: freebsd-current@freebsd.org
cc: freebsd-alpha@freebsd.org
Subject: Re: can't compile kernel without bpf
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Fri, 03 Oct 2003 22:58:13 -0000

Ivan Dole=9Eal wrote:

> As for kernel compilation (wireless does need bpf), this was it!

	The new 802.11 layer (device wlan) and some WiFi device drivers (ath=20
and wi) uses the bpfattach2() function call. The bpfattach2()=20
implementation has no stub counterpart in "non-bpf" section of=20
net/bpf.c, so the kernel can't be succesfully linked without BPF support.=


	It's the immediate cause why we need bpf in kernel now.

	The question is - is presence of bpf mandatory for functionality of=20
802.11 devices ?

	I think the correct answer is NO, so it's bug and stub bpfattach2()=20
should be added to apropriate place of net/bpf.c. But I'm not sure.=20
Someone who know should decide and send PR ...


							Dan