Subject: kern/7179: support for AVA-1505
To: None <gnats-bugs@gnats.netbsd.org>
From: Elephant's Root <root@elephant.nervana.montana.edu>
List: netbsd-bugs
Date: 03/17/1999 12:54:54
>Number:         7179
>Category:       kern
>Synopsis:       support for AVA-1505
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 17 12:05:00 1999
>Last-Modified:
>Originator:     Chris Jones
>Organization:
	
>Release:        Roughly Mar. 7, 1999
>Environment:
	
System: NetBSD elephant.nervana.montana.edu 1.3K NetBSD 1.3K (ELEPHANT) #3: Wed Mar 17 12:17:41 MST 1999 root@elephant.nervana.montana.edu:/usr/src/sys/arch/i386/compile/ELEPHANT i386


>Description:
I recently bought an Adaptec AVA-1505, a low-end 16-bit SCSI card.  In
non-PNP mode, it appears to act just like an aic6360, assuming you get
the irq right.  It also appears to work with DMA enabled.  So we might
want to add an entry to GENERIC for i386:

aic1	at isa? port 0x140 irq 10 drq 5

The default settings for the card are actually port 0x140, irq 10, no
DMA.  So I don't know if we should leave the drq in there or not.  The
thing is, the only way to get the card out of isapnp mode is to run
SCSISelect (which comes with it), and you can set the drq from
SCSISelect.

Also, the card can work in isapnp mode.  The dmesg output I get says:
NetBSD 1.3K (ELEPHANT) #3: Wed Mar 17 12:17:41 MST 1999
    root@elephant.nervana.montana.edu:/usr/src/sys/arch/i386/compile/ELEPHANT
cpu0: Intel 486DX (486-class)
[...]
isapnp0: read port 0x203
isapnp0: <Adaptec AVA-1505A       , ADP1505, ADP1530, SCSI Controller> port 0x140/32 irq 9 not configured
[...]

I added ADP1505 to isapnpdevs, and it worked.  Should I have added
ADP1530 instead?

The thing is, the card is now detected twice, once by isa and once by
isapnp.  This happens whenever the card's IO address is the same as
what the isa attachment is looking for.  What is this a bug in?  I get
the same symptom with my ep0.

One more reminder:  This should probably be added to the list of
supported devices on the web page and in the install document.

>How-To-Repeat:
See above.
>Fix:
See above.
>Audit-Trail:
>Unformatted: