From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 29 19:54:48 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE03B16A4CE for ; Wed, 29 Sep 2004 19:54:48 +0000 (GMT) Received: from intelli7.com (host350.jtan.com [207.106.6.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69E7943D39 for ; Wed, 29 Sep 2004 19:54:48 +0000 (GMT) (envelope-from bcg@intelli7.com) Received: from [192.168.0.2] (unknown [65.222.158.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by intelli7.com (Postfix) with ESMTP id 7B5F17DC86A; Wed, 29 Sep 2004 15:59:02 -0400 (EDT) From: Brenden Grace To: Peter Buckingham In-Reply-To: <415B0DDA.2040200@pantasys.com> References: <1096476707.2670.1088.camel@localhost.localdomain> <415AF2D0.7090002@pantasys.com> <1096485467.2670.1127.camel@localhost.localdomain> <415B0DDA.2040200@pantasys.com> Content-Type: text/plain Message-Id: <1096487538.2670.1147.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 29 Sep 2004 15:52:19 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: Device probe issue with an em(4) compatible device X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 19:54:48 -0000 On Wed, 2004-09-29 at 15:32, Peter Buckingham wrote: > experience then just not compiling in the em driver or an ugly like i > describe (or you suggest) should be fine. I wasn't trying to be rude, but DEVICE_PROBE(9) seems to describe how conflicts like this should be handled. I was wondering if I am in fact correct that devices that attempt to be generic enough for wide support (accepting PCI_ANY_ID) should also properly pass the probing (by returning some negative) so that a driver that may better fit the exact device can attach. > If you are doing it for the > later reason why aren't you just extending the em driver to support your > device? I _really_ am only interested in answers to the above question. -- Brenden C. Grace Intelli7