|
From: <ski...@su...> - 2001-11-20 19:43:09
|
On Tue, Nov 20, 2001 at 09:11:57AM +0000, Mark Kilmartin wrote: > OK I was hoping I might only have implement one more command ;) You can test the system with only INQUIRY and WRITE10 done. > I would appreciate that, I had a bit of a look on the net but the only > copy of it I could find was a zip file which won't unzip for me. I don't have the standart in this computer. Tomorow i will fetch it from another computer. But i must go there to get it... :(( > So if I'm right I should probably firstly implement the IDENTIFY INQUIRY (the two are diferent). Inquiry is to see what kind of controller is there in the other side. IDENTIFY is to select a lun inside a device > command, followed by the WRITE10 command and then the COMMAND COMPLETE > WDTR and SDTR commands Yep... > Any help would be greatly appreciated. > > In our case, the SYM53C8XX has a integrated processor. We can program it > > using a special language called SCRIPTS. What we made was to change the > > flow of the program so that it would make a WAIT SELECT. This command > > waits for a controler to select our target. Then we decoded the command > > and made a hardware interrupt so that to read the information. As I > > said, the best way is to do INQUIRY and then make WRITE10. I will check > > the code to see if I can help anymore. > > I'm not sure exactly how much time I'll have to work on this for the > next couple of weeks. > But I'll start looking at code and trying to come up with ways to > implement this stuff. We took a long time before starting writing SCRIPTS... SCSI is a real Bit*h when you got something wrong. The least that can happen is the controler stoping to work, and worst is the two computer begin to reset each other... :((( Pedro Semeano |