From owner-freebsd-multimedia Thu Jul 31 02:57:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24208 for multimedia-outgoing; Thu, 31 Jul 1997 02:57:50 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA24159; Thu, 31 Jul 1997 02:57:06 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA05446; Thu, 31 Jul 1997 10:57:09 +0200 From: Luigi Rizzo Message-Id: <199707310857.KAA05446@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 31 Jul 1997 10:57:09 +0200 (MET DST) Cc: se@FreeBSD.ORG, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707310722.AAA00321@rah.star-gate.com> from "Amancio Hasty" at Jul 31, 97 00:22:32 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-multimedia@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Whatever solution we finally implement, we must be able to > > > attach PnP boards without any help from the PnP BIOS. > > > > Ok, so you are calling for a more powerful configuration mechanism, ... > > > What do you think about my proposed sequence ? > > > > I like it, the only problem is I am unable to implement it myself :) > > You can . The gus pnp sub module does just that. For non-PnP > boards it takes the configuration information from the config > file . > --- > device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr > --- > When the driver sees the configuration information for the card > it just simply overrides whatever the BIOS set the card to or honestly, I would call that a quick hack, not a general configuration mechanism. Especially because I plan to support more than one sound card, and the PnP cards would show up as pcm1, pcm2, ... I think I will look at the userconfig stuff and see if changes are not too hard to implement... Cheers Luigi