scsi: Documentation: Correct spelling

	  lpfc_sli_chipset_init static.

	* Cleaned up references to list_head->next field in the driver.

	* Replaced lpfc_discq_post_event with lpfc_workq_post_event.

	* Implmented Christoph Hellwig's review from 2/5: Check for return

	* Implemented Christoph Hellwig's review from 2/5: Check for return

	  values of kmalloc.

	* Integrated Christoph Hellwig's patch from 1/30: Protecting

	  scan_tmo and friends in !FC_TRANSPORT_PATCHES_V2 &&

	* Integrated Christoph Hellwig's patch from 1/30: Some fixes in

	  the evt handling area.

	* Integrated Christoph Hellwig's patch from 1/30: Remove usage of

	  intr_inited variable. The interrupt initilization from OS side

	  intr_inited variable. The interrupt initialization from OS side

	  now happens in lpfc_probe_one().

	* Integrated Christoph Hellwig's patch from 1/30: remove shim

	  lpfc_alloc_transport_attr - remove shim lpfc_alloc_shost_attrs -

	  moved to kthread. kthread_stop() is not able to wake up thread

	  waiting on a semaphore and "modprobe -r lpfc" is not always

	  (most of the times) able to complete. Fix is in not using

	  semaphore for the interruptable sleep.

	  semaphore for the interruptible sleep.

	* Small Makefile cleanup - Remove remnants of 2.4 vs. 2.6

	  determination.

	  hardware actually found).

	* Integrate Christoph Hellwig's patch for 8.0.14: Add missing

	  __iomem annotations, remove broken casts, mark functions static.

	  Only major changes is chaning of some offsets from word-based to

	  byte-based so we cans simply do void pointer arithmetics (gcc

	  Only major changes is changing of some offsets from word-based to

	  byte-based so we can simply do void pointer arithmetic (gcc

	  extension) instead of casting to uint32_t.

	* Integrate Christoph Hellwig's patch for 8.0.14: flag is always

	  LPFC_SLI_ABORT_IMED, aka 0 - remove dead code.

	  a result of removing from the txcmpl list item which was already

	  removed (100100 is a LIST_POISON1 value from the next pointer

	  and 8 is an offset of the "prev") Driver runs out of iotags and

	  does not handle that case well. The root of the proble is in the

	  does not handle that case well. The root of the problem is in the

	  initialization code in lpfc_sli.c

	* Changes to work with proposed linux kernel patch to support

	  hotplug.

	  associated I/Os to complete before returning.

	* Fix memset byte count in lpfc_hba_init so that

	  LP1050 would initialize correctly.

	* Backround nodev_timeout processing to DPC This enables us to

	  unblock (stop dev_loss_tmo) when appopriate.

	* Background nodev_timeout processing to DPC. This enables us to

	  unblock (stop dev_loss_tmo) when appropriate.

	* Fix array discovery with multiple luns.  The max_luns was 0 at

	  the time the host structure was initialized.  lpfc_cfg_params

	  then set the max_luns to the correct value afterwards.

	  LINK_[UP|DOWN] and RSCN events.

	* Get rid of delay_iodone timer.

	* Remove qfull timers and qfull logic.

	* Convert mbox_tmo, nlp_xri_tmo to 1 argment clock handler

	* Convert mbox_tmo, nlp_xri_tmo to 1 argument clock handler

	* Removed duplicate extern defs of the bind variables.

	* Streamline usage of the defines CLASS2 and CLASS3, removing

	  un-necessary checks on config[LPFC_CFG_FCP_CLASS].

	* Removed lpfc_max_target from lpfc_linux_attach

	* Replace references to lpfcDRVR.pHba[] with lpfc_get_phba_by_inst()

	* Change lpfc_param to lpfc-param

	* Partially removed 32 HBA restriction within driver.  Incorported

	* Partially removed 32 HBA restriction within driver.  Incorporated

	  lpfc_instcnt, lpfc_instance[], and pHba[] into lpfcDRVR

	  structure Added routines lpfc_get_phba_by_inst()

	  lpfc_get_inst_by_phba() lpfc_check_valid_phba()

	* Use Linux list macros for DMABUF_t

	* Break up ioctls into 3 sections, dfc, util, hbaapi

	  rearranged code so this could be easily separated into a

	  differnet module later All 3 are currently turned on by

	  different module later. All 3 are currently turned on by

	  defines in lpfc_ioctl.c LPFC_DFC_IOCTL, LPFC_UTIL_IOCTL,

	  LPFC_HBAAPI_IOCTL

	* Misc cleanup: some goto's; add comments; clarify function

	* Remove unused log message.

	* Collapse elx_crtn.h and prod_crtn.h into lpfc_crtn.h

	* Ifdef Scheduler specific routines

	* Removed following ununsed ioclt's: ELX_READ_IOCB

	* Removed following unused ioctl's: ELX_READ_IOCB

	  ELX_READ_MEMSEG ELX_READ_BINFO ELX_READ_EINVAL ELX_READ_LHBA

	  ELX_READ_LXHBA ELX_SET ELX_DBG LPFC_TRACE 

	* Removed variable fc_dbg_flg

	  3-digit HBAs.  Also changed can_queue so midlayer will only

	  send (HBA_Q_DEPTH - 10) cmds.

	* Clean up code in the error path, check condition.  Remove

	  ununsed sense-related fields in lun structure.

	  unused sense-related fields in lun structure.

	* Added code for safety pools for following objects: mbuf/bpl,

	  mbox, iocb, ndlp, bind

	* Wrapped '#include <elx_sched.h>' in '#ifdef USE_SCHEDULER'.

	  ELX_READ_HBA ELX_INSTANCE ELX_LIP.  Also introduced

	  attribute "set" to be used in conjunction with the above

	  attributes.

	* Removed DLINK, enque and deque declarations now that clock

	* Removed DLINK, enqueue and dequeue declarations now that clock

	  doesn't use them anymore

	* Separated install rule so that BUILD_IPFC has to be set when

	  make is called in order for the install rule to attempt to

	* Create utility clock function elx_start_timer() and

	  elx_stop_timer().  All timeout routines now use these common

	  routines.

	* Minor formating changes fix up comments

	* Minor formatting changes fix up comments

	* Minor formatting changes get rid of failover defines for

	  syntax checking

	* Minor formatting changes remove ISCSI defines.

	  will not exist otherwise.

	* Removed unused malloc counters from lpfcLINUXfcp.c.

	* Remove some unnecessary #includes in lpfcLINUXfcp.c

	* Remove unncessary #includes in elxLINUXfcp.c

	* Remove unnecessary #includes in elxLINUXfcp.c

	* Minor formatting cleanups in Makefile to avoid some

          linewrapping.

	* Removed unused elx_mem_pool data structure.

	  elx_str_atox).

	* Replaced DLINK_t and SLINK_t by standard Linux list_head

	* Removed deque macro

	* Replaced ELX_DLINK_t ans ELX_SLINK_t by Linux struct list_head

	* Replaced ELX_DLINK_t and ELX_SLINK_t by Linux struct list_head

	  (except for clock)

	* Removed following functions from code: linux_kmalloc linux_kfree

	  elx_alloc_bigbuf elx_free_bigbuf

	* Correct Iocbq completion routine for 2.6 kernel case

	* Change void *pOSCmd to Scsi_Smnd *pCmd

	* Change void *pOScmd to struct sk_buff *pCmd

	* Remove data directon code.

	* Remove data direction code.

	* Removed memory pool for buf/bpl buffers and use kmalloc/kfree

	  pci_pool_alloc/free directly.

	* Move PPC check for DMA address 0 in scatter-gather list, into

	Customer reported "garbage in file on x86_64 platform".

	Root Cause: the driver registered controllers as 64-bit DMA capable

	for those which are not support it.

	Fix: Made change in the function inserting identification machanism

	Fix: Made change in the function inserting identification mechanism

	identifying 64-bit DMA capable controllers.

	> -----Original Message-----

	Fix: MegaRAID F/W has fixed the problem and being process of release,

	soon. Meanwhile, driver will filter out the request.

3.	One of member in the data structure of the driver leads unaligne

3.	One member in the data structure of the driver leads to unaligned

	issue on 64-bit platform.

	Customer reporeted "kernel unaligned access addrss" issue when

	Customer reported "kernel unaligned access address" issue when

	application communicates with MegaRAID HBA driver.

	Root Cause: in uioc_t structure, one of member had misaligned and it

	led system to display the error message.

	avoid getting the stale values for busy bit. We want to set the busy

	bit just before issuing command to the FW.

ii.	In the reset handling, if the reseted command is not owned by the

ii.	In the reset handling, if the reset command is not owned by the

	driver, do not (wrongly) print information for the "attached" driver

	packet.

2 Current Version : 00.00.03.02

3 Older Version   : 00.00.03.01

i.	Added FW tranistion state for Hotplug scenario

i.	Added FW transition state for Hotplug scenario

1 Release Date    : Sun May 14 22:49:52 PDT 2006 - Sumant Patro <Sumant.Patro@lsil.com>

2 Current Version : 00.00.03.01

	- Still a buglet in the tags initial settings that needed to be fixed.

	  It was not possible to disable TGQ at system startup for devices 

	  that claim TGQ support. The driver used at least 2 for the queue 

	  depth but did'nt keep track of user settings for tags depth lower 

	  depth but didn't keep track of user settings for tags depth lower

	  than 2.

Wed Nov 11  10:00 1998 Gerard Roudier (groudier@club-internet.fr)

	  were due to a SCSI selection problem triggered by a clearly 

	  documented feature that in fact seems not to work: (53C8XX chips  

	  are claimed by the manuals to be able to execute SCSI scripts just 

	  after abitration while the SCSI core is performing SCSI selection).

	  after arbitration while the SCSI core is performing SCSI selection).

	  This optimization is broken and has been removed.

	- Some broken scsi devices are confused when a negotiation is started 

	  on a LUN that does not correspond to a real device. According to 

	- Code cleanup and simplification:

	  Remove kernel 1.2.X and 1.3.X support.

	  Remove the _old_ target capabilities table.

	  Remove the error recovery code that have'nt been really useful.

	  Remove the error recovery code that hasn't been really useful.

	  Use a single alignment boundary (CACHE_LINE_SIZE) for data 

	  structures.

	- Several aggressive SCRIPTS optimizations and changes:

	- Some simplification for 64 bit arch done ccb address testing.

	- Add a check of the MSG_OUT phase after Selection with ATN.

	- The new tagged queue stuff seems ok, so some informationnal 

	  message have been conditionned by verbose >= 3.

	- Donnot reset if a SBMC interrupt reports the same bus mode.

	  message have been conditioned by verbose >= 3.

	- Do not reset if a SBMC interrupt reports the same bus mode.

	- Print out the whole driver set-up. Some options were missing and 

	  the print statement was misplaced for modules.

	- Ignore a SCSI parity interrupt if the chip is not connected to 

	  context on phase mismatch.

	- The above allows now to use the on-chip RAM without requiring 

	  to get access to the on-chip RAM from the C code. This makes 

	  on-chip RAM useable for linux-1.2.13 and for Linux-Alpha for 

	  on-chip RAM usable for linux-1.2.13 and for Linux-Alpha for

	  instance.

	- Some simplifications and cleanups in the SCRIPTS and C code.

	- Buglet fixed in parity error recovery SCRIPTS (never tested).

Tue Mar 26 23:00 1998 Gerard Roudier (groudier@club-internet.fr)

	* revision 2.6g

	- New done queue. 8 entries by default (6 always useable).

	- New done queue. 8 entries by default (6 always usable).

	  Can be increased if needed.

	- Resources management using doubly linked queues.

	- New auto-sense and QUEUE FULL handling that does not need to 

	- generalization of the restart of CCB on special condition as 

          Abort, QUEUE FULL, CHECK CONDITION.

          This has been called 'silly scheduler'.

	- make all the profiling code conditionned by a config option.

	- make all the profiling code conditioned by a config option.

	  This spare some PCI traffic and C code when this feature is not 

          needed.

	- handle more cleanly the situation where direction is unknown.

	- Work-around PCI chips being reported twice on some platforms.

	- Add some redundant PCI reads in order to deal with common 

	  bridge misbehaviour regarding posted write flushing.

	- Add some other conditionnal code for people who have to deal 

	- Add some other conditional code for people who have to deal

	  with really broken bridges (they will have to edit a source 

	  file to try these options).

	- Handle correctly (hopefully) jiffies wrap-around.

Tue May 25  23:00 1999 Gerard Roudier (groudier@club-internet.fr)

	* version sym53c8xx-1.5a

	- Add support for task abort and bus device reset SCSI message 

	  and implement proper synchonisation with SCRIPTS to handle 

	  and implement proper synchronisation with SCRIPTS to handle

          correctly task abortion without races.

	- Send an ABORT message (if untagged) or ABORT TAG message (if tagged)

	  when the driver is told to abort a command that is disconnected and 

	  the support of non compliant SCSI removal, insertion and all 

	  kinds of screw-up that may happen on the SCSI BUS.

	  Hopefully, the driver is now unbreakable or may-be, it is just 

	  quite brocken. :-)

	  quite broken. :-)

	  Many thanks to Johnson Russel (Symbios) for having responded to 

	  my questions and for his interesting advices and comments about 

	  support of SCSI hot-plug.

Sun Jan 24  18:00 1999 Gerard Roudier (groudier@club-internet.fr)

	* version sym53c8xx-1.1

	- Major rewrite of the SCSI parity error handling.

	  The informations contained in the data manuals are incomplete about 

	  The information contained in the data manuals is incomplete about

	  this feature.

	  I asked SYMBIOS about and got in reply the explanations that are 

	  _indeed_ missing in the data manuals.

	- Revamp slightly the Symbios NVRAM lay-out based on the excerpt of 

	  the header file I received from Symbios.

	- Check the PCI bus number for the boot order (Using a fast 

	  PCI controller behing a PCI-PCI bridge seems sub-optimal).

	  PCI controller behind a PCI-PCI bridge seems sub-optimal).

	- Disable overlapped PCI arbitration for the 896 revision 1.

	- Reduce a bit the number of IO register reads for phase mismatch 

	  by reading DWORDS at a time instead of BYTES.

Tue Nov 24  23:00 1998 Gerard Roudier (groudier@club-internet.fr)

	* version pre-sym53c8xx-0.16

	- Add SCSI_NCR_OPTIMIZE_896_1 compile option and 'optim' boot option.

	  When set, the driver unconditionnaly assumes that the interrupt 

	  When set, the driver unconditionally assumes that the interrupt

	  handler is called for command completion, then clears INTF, scans 

	  the done queue and returns if some completed CCB is found. If no 

	  completed CCB are found, interrupt handling will proceed normally.

	- Still a buglet in the tags initial settings that needed to be fixed.

	  It was not possible to disable TGQ at system startup for devices 

	  that claim TGQ support. The driver used at least 2 for the queue 

	  depth but did'nt keep track of user settings for tags depth lower 

	  depth but didn't keep track of user settings for tags depth lower

	  than 2.

Thu Nov 19  23:00 1998 Gerard Roudier (groudier@club-internet.fr)