On Wed, Dec 02, 1998 at 08:25:17AM +0800, David Campbell wrote: > > I am going to hack ppa.c (my only scsi host) to generate custom scsi reset > > and so have a way to test the code... (David any hint btw ? ;). > > What exactly are you trying to achieve here Andrea?, reset the drive (that is > easy) or get the mid-level driver to ask for a reset. How about a /proc entry > so that the next SCSI command fails horribly requiring a reset? > > Something like "cat 'fail=0x1234' > /proc/scsi/ppa/0" where the number will be > used as the high 16 bits of the cmd->result for the next immediate SCSI command > that the interface recieves. This will allow the error processing to work and > hopefully clean itself up. I have echo "RESET" >/proc/scsi/tmscsim/? implemented in the driver I maintain (DC390/AM53C974/tmscsim driver). I think this won't help you, as * you don't have an AM53C974 adapter * the command resets the SCSI bus without intervention of the mid-level code I think you should consider the last fact when designing something to test your mid-level timeout changes. And that's why I post this ... Reagrds, -- Kurt Garloff <[EMAIL PROTECTED]> (Dortmund, FRG) PGP key on http://student.physik.uni-dortmund.de/homepages/garloff The second clause "open source code of derivative works" has been the most controversial (and, potentially the most successful) aspect of CopyLeft licensing. -- Halloween Document - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
