Re: I2O on sparc64 (Was: Re: mlx on sparc?)

[Jan-Hinrich Fessel <oskar%fessel.org@localhost>]

Am 14.09.2008 um 20:16 schrieb Michael L. Hitch:

> On Sun, 14 Sep 2008, Martin Husemann wrote:
>
> > DMA on sparc64 goes through the iommu, so bus addresses have  
> > usually no
> > similarity with neither kernel VA nor kernel PA. Not using
> > bus_dmamap_alloc/load would certainly guarantee the driver to not  
> > work on
> > sparc64.
>
>  It was using bus_dmamem_alloc() and bus_dmamap_load(), but was  
> using the
> address from the bus_dmamem_alloc() rather than the one from the  
> bus_dmamap_load().  I've committed the change, which makes it work  
> on the
> alpha, and should now work on sparc64.

indeed, doesn't look too bad:
Distributed Processing Technology Memory Controller (miscellaneous  
memory, revision 0x02) at pci2 dev 3 function 0 not configured
iop0 at pci2 dev 4 function 0: I2O adapter <DPT PM3755U2B>
iop0: orgid=0x001b version=1
iop0: type want have cbase
iop0: mem  0000 0000 00000000
iop0: i/o  0000 0000 00000000
iop0: interrupting at ivec 1c
iop0: queue depths: inbound 256/256, outbound 256/256

mem and i/o - is that correct?

later then:
iopsp0 at iop0 tid 8: SCSI port <QLOGIC, ISP1080, 00000001>
iopsp0: 16-bit, max sync rate 40MHz, initiator ID 7
scsibus4 at iopsp0: 16 targets, 8 luns per target
iop0: async reconfig: requested 0x00000003

# iopctl showstatus
organization id          27
iop id                   4095
host unit id             0
segment number           0
i2o version              1
iop state                8
messenger type           0
inbound frame sz         8388608
init code                128
max inbound queue depth  256
inbound queue depth      256
max outbound queue depth 256
product id string        <DPT PM3755U2B>
expected lct size        3693
iop capabilities         0x00000000
desired priv mem sz      0x00000000
current priv mem sz      0x00000000
current priv mem base    0x00000000
desired priv io sz       0x00000000
current priv io sz       0x00000000
current priv io base     0x00000000

I probably need to source a power cable for the external drive now...

Cheers and Thanks
        Oskar

Attachment: PGP.sig
Description: This is a digitally signed message part