Subject: Re: -current (1.2A-960626) snapshot available
To: Noriyuki Soda <soda@sra.co.jp>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-i386
Date: 07/13/1996 07:57:55
On Sat, 13 Jul 1996 05:38:35 +0900
Noriyuki Soda <soda@sra.co.jp> wrote:
> Does this mean that you don't accept neither
> ahc* at eisa? slot ?
> or
> ahc0 at isa? port ? irq ?
> for AHA-284x ?
Currently, ahc* at eisa? slot ? _should_ work for 284x controllers
_providing_ an EISA signature appears in the BIOS. Otherwise, the EISA
bus is never probed.
As for ahc at isa, that front-end went away with the mass-update of the
ahc driver a month-ish or so (or more?) ago. The lack of said front-end
is _definitely_ a bug.
I just sent off the front-end I wrote for ahc_isa yesterday to Michael
and Noriyuki. Hopefully, they can get is tested and put into the tree in
a reasonable amount of time. (I can't test it, so I don't feel
comfortable committing it myself.)
> It may not conflict with other devices (at least, if Jason's extent
> map manager is available), and if you want to hard-code the address,
> then you can easily do either
Yes, that's true, however my extent code (and thus, the i386 i/o port
accounting code built in to bus_io_{,un}map()) only exists in the
post-1.2 sources. IMO, it should be pulled up into the release branch,
since leaving it out means that a large number of users could be left out
in the code (for want of a SCSI driver). I'll discuss this with the
release engineer early next week.
> ahc* at eisa? slot 1
> or
> ahc0 at isa? port 0x1c00 irq ?
Actually, I pretty much stole the EISA front-end outright, stole some of
the EISA bus code, and then glued it together. So, the offset is dealt
with within the driver. This is to make it easier to read the ID string
off the card...
ahc0 at isa? port ? irq ?
or
ahc0 at isa? port 0x1000 irq ?
> I want to see official decision which config stuff should be used for
> 284x, EISA or ISA ?
If the ahc_isa front-end is committed, I want to see the handling of the
284x taken out of ahc_eisa. However, I want to see the eisadevs entry
(for EISA_PRODUCT_ADP7756 and EISA_PRODUCT_7757) remain. They should be
denoted as VLbus devices in eisadevs (a comment explaining why they're
there should suffice).
-- save the ancient forests - http://www.bayarea.net/~thorpej/forest/ --
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: 408.866.1912
NAS: M/S 258-6 Work: 415.604.0935
Moffett Field, CA 94035 Pager: 415.428.6939