From owner-freebsd-net@FreeBSD.ORG Tue Dec 8 23:42:21 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05B851065672 for ; Tue, 8 Dec 2009 23:42:21 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id E8AB18FC13 for ; Tue, 8 Dec 2009 23:42:17 +0000 (UTC) Received: from park.js.berklix.net (p549A7B2A.dip.t-dialin.net [84.154.123.42]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id nB8NB4LL073496; Tue, 8 Dec 2009 23:11:05 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id nB8NBCqI067758; Wed, 9 Dec 2009 00:11:12 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id nB8NAlDQ038723; Wed, 9 Dec 2009 00:10:52 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200912082310.nB8NAlDQ038723@fire.js.berklix.net> To: "David Christensen" From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Dec 2009 14:22:20 PST." <5D267A3F22FD854F8F48B3D2B52381933A31693938@IRVEXCHCCR01.corp.ad.broadcom.com> Date: Wed, 09 Dec 2009 00:10:47 +0100 Sender: jhs@berklix.com Cc: "freebsd-net@freebsd.org" , Julian Elischer , Rafael Ganascim Subject: Re: bge driver and MSI X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2009 23:42:21 -0000 > As a more general question, what would be the right medium to > document such device errata as it relates to a driver? Is the > man page the best location or would it be better to add a > table near the top of the driver file which summarizes the > bugs and the workarounds? Is there a general consensus? Lots of Unix users dont have use or understand sources, so IMO A) If person reporting is willing to code a fix, use send-pr to send .c patch. B) Else use send-pr with a diff to add a BUGS section to eg bge.5 man file, & cc programmers if known, who can delete BUGS lines when fixed. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64: http://asciiribbon.org