From owner-freebsd-stable Thu Jul 20 5:33: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.145.166]) by hub.freebsd.org (Postfix) with SMTP id 2DE8237BA97 for ; Thu, 20 Jul 2000 05:32:21 -0700 (PDT) (envelope-from avatar@www.mmlab.cse.yzu.edu.tw) Received: (qmail 72016 invoked from network); 20 Jul 2000 12:31:40 -0000 Received: from www.mmlab.cse.yzu.edu.tw (HELO www.mmlab.cse.yzu.edu.tw.) (@140.138.145.166) by www.mmlab.cse.yzu.edu.tw with SMTP; 20 Jul 2000 12:31:40 -0000 Date: Thu, 20 Jul 2000 20:31:40 +0800 (CST) From: Tai-hwa Liang To: freebsd-stable@FreeBSD.org Subject: -stable ISA PnP config(controller pnp0) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to upgrade from 3.4-RELEASE to 4.1-RC hours ago, and noticed that "controller pnp0" was removed from kernel configuration; furthermore, it seems that the "pnp" config option was also removed from "boot -c" editor. Without the ISA PnP configuration support, my SoundBlaster 16 PnP would unable to playback MIDI synth via VOXWARE snd driver(sb_reset_dsp failed during system startup). It also seems that the newpcm driver in 4-stable still doesn't support MIDI synth(/dev/sequencer) as the pcm0 device in 3-stable; therefore, I have to use VOXWARE to play with MIDI synth before new-midi being merged in the tree. Is there any workaround for me to manually config my ISA PnP device in 4-stable such that the VOXWARE snd driver can detect my sound card? Can anyone enlighten me the relation between PNPBIOS and "controller pnp0?" TIA. FYI(4.1-RC with PNPBIOS, snd, sb0, sbxvi0 & sbmidi0): sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sb_reset_dsp failed sb_reset_dsp failed ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown0: at iomem 0-0x9ffff,0x100000-0xfffffff,0xe8000-0xeffff,0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfffff,0xcd000-0xcffff,0xfffe0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x75 irq 8 on isa0 unknown: can't assign resources unknown3: at port 0xf0 irq 13 on isa0 unknown4: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown5: at port 0x61 on isa0 unknown6: at port 0xcf8-0xcff on isa0 unknown7: at port 0xe400-0xe47f,0xe800-0xe83f on isa0 unknown8: