From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 16 21:16:02 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F20671065696 for ; Mon, 16 Aug 2010 21:16:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C29648FC27 for ; Mon, 16 Aug 2010 21:16:02 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7208846B35; Mon, 16 Aug 2010 17:16:02 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 72C438A04F; Mon, 16 Aug 2010 17:16:01 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 16 Aug 2010 16:19:35 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100217; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201008161619.35740.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 16 Aug 2010 17:16:01 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Garrett Cooper Subject: Re: Why doesn't ppc(4) check non-ENXIO failures during probe? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Aug 2010 21:16:03 -0000 On Sunday, August 15, 2010 1:33:38 am Garrett Cooper wrote: > One thing that's puzzling me about the ppc(4) driver's ISA > routines is that it only checks to see whether or not the device has > an IO error: Your patch would break hinted ppc devices. ENXIO means that the device_t being probed has an ISA PNP ID, but it does not match any of the IDs in the list. ENONET means that the device_t does not have an ISA ID at all. For the isa bus that means it was explicitly created via a set of ppc.X hints. -- John Baldwin