AnyBody worked with TSB43AB22 FireWire OHCI chip

Rishabh Kumar Goel <[email protected]>
Newsgroups gmane.os.netbsd.devel.general,gmane.os.netbsd.general
Organization SoCrates Software India Pvt. Ltd
Message-ID <[email protected]>
Hi,

I have a TSB43AB22 FireWire PCI controller card. I m trying get my FireWire 
HDD workable on NetBSD. Though the ohci driver is fine with NEC OHCI 
chip(72873) but it stucks with TSB43AB22 Card. 

________Dmesg________
sbpscsi0 at fwnode0fwohci_handler_set: ctx 2, tcode 1, key 0x0, 0xf0010004, 
0x0

scsibus0 at sbpscsi0: 1 target, 1 lun per target
Called sbpscsi_scsipi_request
Got req_run_xfer
xs control: 0x000001c4, timeout: 10000
opcode: 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Alloc'ing more orbs
fwohci_handler_set: ctx 2, tcode 5, key 0x0, 0xf0010008, 0x0
fwohci_handler_set: ctx 2, tcode 1, key 0x0, 0xf001000c, 0x0
fwohci_at_output: tcode 0x1, tlabel 0x37 hlen 16, dlen 8
    0002dd10 ffc0ffff f0030000 00080000$
    00000000 f0010008$
fwohci_at_output: desc 24
    02000010 00000000 00000000 00000000 0002dd10 ffc0ffff f0030000 00080000
    103c0008 00535b30 00000000 00000000
fwohci1: intmask=0x00000001: ReqTxComplete(0x8052)
fwohci1: intmask=0x00000030: RQPkt(0x8452) RSPkt(0x9451)
fwohci_handler_set: ctx 2, tcode 5, key 0x0, 0xf0010010, 0x0
fwohci_handler_set: ctx 2, tcode 5, key 0x0, 0xf0010014, 0x0
fwohci_event_thread: intmask 00000031 ReqTxComp RQPkt RSPkt
fwohci_at_done: desc 24 (3)
    02000010 00000000 00000000 00000000 0002dd10 ffc0ffff f0030000 00080000
    103c0008 00535b30 00000000 8452c799
fwohci_buf_pktget: desc 0, off 0, req 4096, res 4060, len 4, avail 36
fwohci_buf_pktget: desc 0, off 4, req 4096, res 4060, len 8, avail 32
fwohci_buf_input: tcode=0xe, tlabel=0x0, hlen=12, dlen=0
fwohci_buf_pktget: desc 0, off 12, req 4096, res 4060, len 4, avail 24
fwohci_phy_input: BusReset: 0x00010000
fwohci_buf_pktget: desc 0, off 16, req 4096, res 4060, len 4, avail 20
fwohci_buf_pktget: desc 0, off 20, req 4096, res 4060, len 12, avail 16
fwohci_buf_input: tcode=0x5, tlabel=0x16, hlen=16, dlen=0
fwohci_buf_pktget: desc 0, off 32, req 4096, res 4060, len 4, avail 4

sbp2_login_ans: (addr): (0x80053d4c)
fwohci_at_output: tcode 0x7, tlabel 0x16 hlen 16, dlen 32
    00025970 ffc00020 00000000 00200000$
    00000000 00000000 00000000 f001000c 90400000 00000010 00000000 f0010004$
fwohci_at_output: desc 24
    02000010 00000000 00000000 000031d6 00025970 ffc00020 00000000 00200000
    103c0020 00cb3c00 00000000 00000000
fwohci_buf_pktget: desc 0, off 36, req 4096, res 4060, len 4, avail 0
fwohci1: intmask=0x00000002: RespTxComplete(0x8051)
fwohci_buf_input: no input for 2
fwohci_buf_pktget: desc 16, off 1068, req 4096, res 3012, len 4, avail 16
fwohci_buf_pktget: desc 16, off 1072, req 4096, res 3012, len 8, avail 12
fwohci_buf_input: tcode=0x2, tlabel=0x37, hlen=12, dlen=0
fwohci_buf_pktget: desc 16, off 1080, req 4096, res 3012, len 4, avail 4
fwohci_arrs_input: tcode 0x2, from 0xffc0, tlabel 0x37, rcode 0x0, hlen 12, 
dle0
fwohci_arrs_input: no listner
fwohci_buf_pktget: desc 16, off 1084, req 4096, res 3012, len 4, avail 0
fwohci_buf_input: no input for 3
fwohci_event_thread: intmask 00000002 RespTxComp
fwohci_at_done: desc 24 (3)
    02000010 00000000 00000000 000031d6 00025970 ffc00020 00000000 00200000
    103c0020 00cb3c00 00000000 84510000

sbp2_login_ans: (addr): (0x80053d4c)

sbp2_free_orb:(addr):(0x8005575c)
Freeing orb at addr: 0x00000000f0010008 status_rec: 0x0
sbpscsi_timeout
Called sbp2_abort
________Dmesg________

I have seen some mails regarding this chip on linux mailing lists, but i m 
unable to apply it with netbsd code?

http://sourceforge.net/mailarchive/message.php?msg_id=1458191
-- 
Regards,
Rishabh Kumar Goel
Software Engineer
SoCrates Software India Pvt. Ltd.
Bangalore

Scanned by SecureSynergy VirusScreen Service. 
For more information log on to : http://www.securesynergyonline.com or http://www.securesynergy.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.