Thread: [Linux1394-cvslog] ieee1394 sbp2.c

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv15967

Modified Files:
	sbp2.c 
Log Message:
Fixing minor typo causing wrong debug message to spit out


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv6270

Modified Files:
      Tag: busmgr
	sbp2.c 
Log Message:
Fixed bus reset for busmgr branch.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv7247

Modified Files:
      Tag: busmgr
	sbp2.c 
Log Message:
Fix minor typo (merged from trunk).


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv16927

Modified Files:
      Tag: bcollins-branch
	sbp2.c 
Log Message:
Add hotplug support


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv3965

Modified Files:
	sbp2.c 
Log Message:
Merge changes from Alan Cox's tree for sleep in spinlock. Also reformat sbp2_add_host


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv10264

Modified Files:
	sbp2.c 
Log Message:
mask out the lower 24 bits of sw_version


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv20209

Modified Files:
	sbp2.c 
Log Message:
Change all interruptible_sleep_on to just sleep_on, since the
call to call_usermodehelper in nodemgr.c eventuallly delivers a
SIGCHLD to keventd, which causes login to fail.  We cant really
deal with signals reasonably anyway.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv16331

Modified Files:
	sbp2.c 
Log Message:
Add MODULE_LICENSE


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv17647

Modified Files:
	sbp2.c 
Log Message:
Fix max payload format for printk


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv17556

Modified Files:
	sbp2.c 
Log Message:
Add 2.2 proc entries (again).


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv10426

Modified Files:
	sbp2.c 
Log Message:
Add a kbuild-2.5 wrap around some scsi includes.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv12384

Modified Files:
	sbp2.c 
Log Message:
Lock io_request_lock to prevent lockups on SMP


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv11969

Modified Files:
	sbp2.c 
Log Message:
Remove io_request_lock when completing scsi commands now that we're
running as an enhanced scsi driver (no longer uses old scsi_done routine).
Have tested this against an SMP 2.4 kernel, but not a true SMP machine.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv12338

Modified Files:
	sbp2.c 
Log Message:
Make printk for node fmt match nodemgr's style


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv24933

Modified Files:
	sbp2.c 
Log Message:
Add a little more info to the proc info output


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv21831

Modified Files:
	sbp2.c 
Log Message:
Added one final (hopefully) scsi inquiry data fix from HJ Lu. One place 
where CMD_DMA_SINGLE and CMD_DMA_PAGE were mixed up. Also added in 
compatibility for 2.4.12 and earlier.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv25744

Modified Files:
      Tag: linux_2_2
	sbp2.c 
Log Message:
Following changes made:
- Minor inquiry hack change (for better device compatibility)
- If device type not in device's config rom, pull from scsi inquiry
  response data


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv26978

Modified Files:
	sbp2.c 
Log Message:
Added io_reuest_lock around callback to scsi stack. Maybe can remove this
later after cleaning up sbp2 driver smp-wise.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv27684

Modified Files:
      Tag: linux_2_2
	sbp2.c 
Log Message:
Grab io_request_lock before making callbacks to scsi mid-level.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv11028

Modified Files:
	sbp2.c 
Log Message:
Support more than 8 sbp2 devices if SBP2SCSI_MAX_SCSI_IDS bumped up.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv11503

Modified Files:
      Tag: linux_2_2
	sbp2.c 
Log Message:
Support more than 8 sbp2 devices if SBP2SCSI_MAX_SCSI_IDS bumped up.


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv28578

Modified Files:
	sbp2.c 
Log Message:
Oops. Accidently re-enabled deserialized I/O. I hope to actually commit this
soon, but need to do some heavy testing first.   =)


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv14418

Modified Files:
	sbp2.c 
Log Message:
Only ise io_request_lock on 2.4.x


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv29328

Modified Files:
	sbp2.c 
Log Message:
Host scsi_host->host_lock on 2.5.x, instead of io_request_lock


Update of /cvsroot/linux1394/ieee1394
In directory usw-pr-cvs1:/tmp/cvs-serv26110

Modified Files:
	sbp2.c 
Log Message:
Minor change to sbp2 status handling to deal with broken firmware on
QPS CDRW drive. The firmware on this drive actually stores the ORB
at the end of the sbp2 status it writes to us, and since the length is
longer, we think that an error occured. Now, pull the sbp2 status length
from the actual status data, and don't depend on how much data is 
actually written by the drive. Perhaps the QPS folk forgot to pull out
some debug code from their firmware???

Thread: [Linux1394-cvslog] ieee1394 sbp2.c

linux1394-cvslog