From owner-freebsd-current Mon Nov 29 18:10: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id C09EA15691 for ; Mon, 29 Nov 1999 18:09:29 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id LAA80372; Tue, 30 Nov 1999 11:09:16 +0900 (JST) Date: Tue, 30 Nov 1999 11:09:15 +0900 Message-ID: <14403.12747.511556.68187Y@rina.r.dl.itc.u-tokyo.ac.jp> From: tanimura@r.dl.itc.u-tokyo.ac.jp To: peter@netplex.com.au Cc: winter@jurai.net, hibma@skylink.it, current@FreeBSD.ORG Subject: Re: sbc and pcm In-Reply-To: In your message of "Tue, 23 Nov 1999 04:22:39 +0800" <19991122202239.5A75C1C6D@overcee.netplex.com.au> References: <19991122202239.5A75C1C6D@overcee.netplex.com.au> Cc: tanimura@r.dl.itc.u-tokyo.ac.jp User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 6) (Big Bend) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Nov 1999 04:22:39 +0800, Peter Wemm said: >> Mostly, sbc.c is handling PnP ID matching in a totally bogus manner. Peter> Yes, it's quite bogus and is incompatible with motherboard devices. There Peter> should be no vendor ID references in there at all, that's for card ID, not Peter> device id. I am now working to tidy up the sbc probe. Would it be enough for the sound chips on motherboards to check the logical device ID of 0x??008c0e? How does the result of pnpinfo(1) for a motherboard chip look like? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message