From owner-freebsd-current  Tue Jun 25 11:52:23 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA28265
          for current-outgoing; Tue, 25 Jun 1996 11:52:23 -0700 (PDT)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28260;
          Tue, 25 Jun 1996 11:52:19 -0700 (PDT)
Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id LAA22753; Tue, 25 Jun 1996 11:51:30 -0700 (PDT)
Message-Id: <199606251851.LAA22753@rah.star-gate.com>
X-Mailer: exmh version 1.6.5 12/11/95
To: Terry Lambert <terry@lambert.org>
cc: kallio@cc.jyu.fi (Seppo Kallio), multimedia@FreeBSD.org, users@FreeBSD.org,
        current@FreeBSD.org
Subject: Re: * GUS PnP Pro + SNAP 960612 + SOYO - please help * 
In-reply-to: Your message of "Tue, 25 Jun 1996 11:17:49 PDT."
             <199606251817.LAA00193@phaeton.artisoft.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Jun 1996 11:51:30 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

I would disable the Plug and Play option for the BIOS and insert the
IRQs manually on the CMOS. I had do that once with a buggy AMI Plug & Play
BIOS.

To configure the gus pnp in the above scenario, generate a config entry 
similar to this:

device gus0 at isa? port 0x220 irq 11 drq 7 flags 0x5 vector gusintr

In other words let the gus pnp sound driver fully configure the gus pnp
for you. 

The config entry:

> > device gus0 at isa? vector gusintr

Tells the gus pnp driver to rely on the BIOS to fill in the appropiate 
values in the gus pnp card ...

	Hope this helps,
	Amancio


>From The Desk Of Terry Lambert :
> > > Does the motherboard actually have PnP BIOS?
> > 
> > Award Plug and Play BIOS Extension v1.0A
> > Copyright Award Software Inc
> [ ... ]
> 
> > > The ethernet cards must be identified to the PnP BIOS as well so that
> > > their address assignments aren't conflicted.  A Real(tm) PnP BIOS
> > > will have a CMOS setup that lets you locate state cards in the
> > > interference graph so the PnP assignments will not conflict.
> > 
> > In my test today:
> > 
> > SMC irq is 10, port is 300, iomem is cc000
> > GUS irq is 11, port is 220, dma is now 5,7 (1,3 tested also)
> 
> These are BIOS-generated messages?
> 
> > In kernel I have
> > 
> > device ed0 at isa? port 0x300 net irq 10  iomem 0xcc000 vector edintr
> > controller      snd0
> > device gus0 at isa? vector gusintr
> > 
> > If gus is in the box I am getting    ed0 timeout  if I take gus out ed0
> > works OK.
> > 
> > So there must be some other pci card conflicting with ed0 when gus is in.
> > 
> > * Ah. Now it works. I did change ed0 to irq 3 port 280 iomem d0000 *
> > 
> > But I understand this at all ...
> 
> It is the GUS.  It is swallowing a lot of ports, but you have only a 1.0A
> (very old) version of the BIOS.  You will need to turn off PnP or physically
> relocate the cards to avoid collision.
> 
> You haven't really said whether the ethernet card is a PnP card or not.
> If it isn't, you must put it in the CMOS, or the PnP BIOS can't see it.
> Since an old PnP BIOS can't see the multiple ranges used by the GUS
> anyway, this is probably irrelevant.
> 
> 
> 					Terry Lambert
> 					terry@lambert.org
> ---
> Any opinions in this posting are my own and not those of my present
> or previous employers.