From owner-freebsd-current@FreeBSD.ORG Sat Jul 16 17:30:56 2005 Return-Path: X-Original-To: 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 1F35416A41C for ; Sat, 16 Jul 2005 17:30:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B675643D45 for ; Sat, 16 Jul 2005 17:30:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j6GHUHBP031276; Sat, 16 Jul 2005 11:30:17 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 16 Jul 2005 11:30:59 -0600 (MDT) Message-Id: <20050716.113059.82101301.imp@bsdimp.com> To: harrycoin@qconline.com From: "M. Warner Losh" In-Reply-To: <4.3.2.7.2.20050716114020.01f0fcb8@mail.qconline.com> References: <42D82D59.9060605@root.org> <20050716.103028.04060625.imp@bsdimp.com> <4.3.2.7.2.20050716114020.01f0fcb8@mail.qconline.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, nate@root.org Subject: Re: mss.c pcm fix to ' attach returned 6 ' load failure for v5.x acpi and up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2005 17:30:56 -0000 In message: <4.3.2.7.2.20050716114020.01f0fcb8@mail.qconline.com> Harry Coin writes: : I think all that's needed to wrap this up is for the powers that be to : offer clarity about one thing, final decision about the case of arbitrary : (beyond com1, etc.) non-pnp ISA devices probe routines. As far as I kow, there's nothing wrong with them. Please state the problem. They work and work well today. Without a clear problem statement, it is hard to know what you are complaining about. : A great many sound : chips of various register demands are in this list. (Admittedly older : devices, but I ran into serious breakage of an isa pnp device driver : because of interactions with the related non-pnp probe routine that : supported earlier chipsets in the same family that were largely register : compatible with the pnp versions). I just took a look at mss. I'm not at all sure what you are talking about. mss.c specifically doesn't probe devices that aren't PNP for its identify the device case. pnpmss does only pnp devices. The mss_probe routine won't look anywhere other than it has been specifically instructed to look by the hints mechanism. Can you be more specific about the exact breakage? Vague statements like the above don't convey the information that I need to help you solve your problem. Warner