You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
|---|
|
From: Mark K. <mr...@re...> - 2001-11-21 15:11:02
|
After some consideration I don't currently have the time to convert the aic7xxx driver (I'm heading back to college next year though and will be looking for a project and this is currently top of my list.) I still want to play around with IP over SCSI though so I was thinking of buying a couple of symbios cards. But when I tried to go to www.symbios.com I am redirected to www.lsilogic.com According to the web page the LSI cards are the same as the symbios cards just with different letters in front of the card name. Well what I was wondering is what card should I go for. I was thinking of getting at least the Ultra 160 cards http://www.lsilogic.com/products/storage_standard_prod/hba/scsi/ultra160_scsi/index.html But would really like to try the Ultra 320 cards. http://www.lsilogic.com/products/storage_standard_prod/hba/scsi/ultra320_scsi/index.html What do you think? Would these cards work with the Target Mode driver? MArk |
|
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 |
|
From: Mark K. <mr...@re...> - 2001-11-20 09:12:39
|
> > I believe the commands it needs to support are INQUIRY and WRITE10 is > > this correct? > > Is there more? OK I was hoping I might only have implement one more command ;) > You need some more. WDTR (Wide data transfer request) for 16 bits > comunications. SDTR (Sync data transfer request) Syncrouns transfer, for > more than 10MB/s transfer rate. IDENTIFY so that you can choose you LUN. > This last is very easy. You just accept it. It normaly appears before > WDTR and SDTR. This messages are sent by the other controler to > negotiate the speed of comunications. But you also need COMMAND COMPLETE > to indicate if the command was done correctly. > > > It seems to support the INQUIRY command but I'm not sure if it supports > > it enough for the purposes. Excelent > The only thing that INQUIRY is needed is to say to the other party what > this board is. I think it's the first command to implement. When you can > do a IDENTIFY all the others are more or less the same. 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. > You will need the SCSI standart to see how to do this messages. We got a > copy in the internet, but it wasn't easy. If you whant, i can send you > a copy. > > > It does not seem to support the WRITE10 command though :( > > WRITE10 is the way we use to send data. It's the main command. If you > got WRITE10 and IDENTIFY done, it will work, but slowly (5/10 MB/s). All > the other commands are not essenstial. If you make IDENTIFY work, > WRITE10 is easy. So if I'm right I should probably firstly implement the IDENTIFY command, followed by the WRITE10 command and then the COMMAND COMPLETE WDTR and SDTR commands > > What I now need is any advice on how to get it to support the WRITE10 > > command. 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. |
|
From: <ski...@su...> - 2001-11-19 19:27:37
|
On Mon, Nov 19, 2001 at 02:52:19PM +0000, Mark Kilmartin wrote: > OK I had a better look through the AIC7xxx code this weekend. > > I believe the commands it needs to support are INQUIRY and WRITE10 is > this correct? > Is there more? > You need some more. WDTR (Wide data transfer request) for 16 bits comunications. SDTR (Sync data transfer request) Syncrouns transfer, for more than 10MB/s transfer rate. IDENTIFY so that you can choose you LUN. This last is very easy. You just accept it. It normaly appears before WDTR and SDTR. This messages are sent by the other controler to negotiate the speed of comunications. But you also need COMMAND COMPLETE to indicate if the command was done correctly. > It seems to support the INQUIRY command but I'm not sure if it supports > it enough for the purposes. The only thing that INQUIRY is needed is to say to the other party what this board is. I think it's the first command to implement. When you can do a IDENTIFY all the others are more or less the same. You will need the SCSI standart to see how to do this messages. We got a copy in the internet, but it wasn't easy. If you whant, i can send you a copy. > It does not seem to support the WRITE10 command though :( WRITE10 is the way we use to send data. It's the main command. If you got WRITE10 and IDENTIFY done, it will work, but slowly (5/10 MB/s). All the other commands are not essenstial. If you make IDENTIFY work, WRITE10 is easy. > > What I now need is any advice on how to get it to support the WRITE10 > command. 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. > > MArk > > > Pedro Semeano |
|
From: <ski...@su...> - 2001-11-15 22:26:02
|
On Wed, Nov 14, 2001 at 10:15:56AM +0000, Mark Kilmartin wrote: > I have had a look through the aic7xxx driver code and there seems to be > some support for target mode already in the driver. I also looked in the driver, and you are right. There seems to be a target mode system. Must, you must checkit to see if it works correctly. The way we use ou SCSI controllers, we only need a couple messages for the driver to take care. If the aic driver supports them all, then you don't need to do almost nothing... :)) You must also, see who to turn target mode on. > I have two adaptec cards the first is an ISA model based on the aic7770 > chip acording to the driver code this does not support target mode so > this is useless for ipoverscsi development. > > But I also have two PCI cards based on the aic7880 chip which does seem > to support target mode. > > As I said there does seem to be some support for target mode in the > driver can anybody confirm this. > > Either way can you tell me what my next step should be to try and get > this working. Try to see if it works. In http://ipoverscsi.sourceforge.net/ we will put the latest code today. It works very well with our boards, and we get a good speed (23MB/s) for a 40MB/s board. If this board can support to lose abritation, you can get real good transfers rates, but you must change a part of scsinet.c. If you need something, just send me a mail and i will try to help you. > > I also have some access to newer cards in work including Adaptec cards > with support for up to Ultra160 SCSI. It would be great if you can check the speed of that boards. We are using relativly slow boards, and don't have access to a better one. We also have a benchmark program made (we will put it in the project page), so you can check the speed that you got. Pedro Semeano |
|
From: Mark K. <mr...@re...> - 2001-11-14 10:16:42
|
I have had a look through the aic7xxx driver code and there seems to be some support for target mode already in the driver. I have two adaptec cards the first is an ISA model based on the aic7770 chip acording to the driver code this does not support target mode so this is useless for ipoverscsi development. But I also have two PCI cards based on the aic7880 chip which does seem to support target mode. As I said there does seem to be some support for target mode in the driver can anybody confirm this. Either way can you tell me what my next step should be to try and get this working. I also have some access to newer cards in work including Adaptec cards with support for up to Ultra160 SCSI. |
|
From: Mark K. <mr...@re...> - 2001-11-12 16:40:22
|
Has anybody gotten any aic7xx cards to work. I would love to help with development but I only have adaptec cards currently. If somebody could point me in the right direction I would be willing to have a go at getting these cards working. Mark Kilmartin |