31 Mar, 2011

1 commit


04 Aug, 2010

1 commit

  • Below you will find an updated version from the original series bunching all patches into one big patch
    updating broken web addresses that are located in Documentation/*
    Some of the addresses date as far far back as 1995 etc... so searching became a bit difficult,
    the best way to deal with these is to use web.archive.org to locate these addresses that are outdated.
    Now there are also some addresses pointing to .spec files some are located, but some(after searching
    on the companies site)where still no where to be found. In this case I just changed the address
    to the company site this way the users can contact the company and they can locate them for the users.

    Signed-off-by: Justin P. Mattock
    Signed-off-by: Thomas Weber
    Signed-off-by: Mike Frysinger
    Cc: Paulo Marques
    Cc: Randy Dunlap
    Cc: Michael Neuling
    Signed-off-by: Jiri Kosina

    Justin P. Mattock
     

21 Sep, 2009

1 commit


17 Oct, 2008

1 commit


14 Jan, 2007

1 commit

  • 1. Changes in Initialization to fix kdump failure.
    Send SYNC command on loading.
    This command clears the pending commands in the adapter
    and re-initialize its internal RAID structure.
    Without this change, megaraid driver either panics or fails to
    initialize the adapter during kdump's second kernel boot
    if there are pending commands or interrupts from other devices
    sharing the same IRQ.
    2. Authors email-id domain name changed from lsil.com to lsi.com.
    Also modified the MODULE_AUTHOR to megaraidlinux@lsi.com

    Signed-off-by: Sumant Patro
    Signed-off-by: James Bottomley

    Sumant Patro
     

29 Jul, 2006

3 commits

  • There was an issue in the data structure defined by megaraid driver
    casuing "kernel unaligned access.." messages to be displayed during
    IOCTL on IA64 platform.

    The issue has been reported/fixed by Sakurai Hiroomi
    [sakurai_hiro@soft.fujitsu.com].

    Signed-Off By: Seokmann Ju
    Signed-off-by: James Bottomley

    Ju, Seokmann
     
  • With this patch, driver will protect data corruption created by
    INQUIRY with EVPD request to megaraid controllers. As specified in
    the changelog, megaraid F/W already has fixed the issue and being
    under process of release. Meanwhile, driver will protect the system
    with this patch.

    Signed-Off By: Seokmann Ju
    Signed-off-by: James Bottomley

    Ju, Seokmann
     
  • This patch contains
    - a fix for 64-bit DMA capability check in megaraid_{mm,mbox} driver.
    - includes changes (going back to 32-bit DMA mask if 64-bit DMA mask
    failes) suggested by James with previous patch.
    - addition of SATA 150-4/6 as commented by Vasily Averin.

    With patch, the driver access PCIconfiguration space with dedicated
    offset to read a signature. If the signature read, it means that the
    controller has capability to handle 64-bit DMA.
    Without this patch, the driver used to blindly claim 64-bit DMA
    capability.
    The issue has been reported by Vasily Averin [vvs@sw.ru].
    Thank you Vasily for the reporting.

    Signed-Off By: Seokmann Ju
    Signed-off-by: James Bottomley

    Ju, Seokmann
     

28 Apr, 2006

1 commit

  • When abort failed, the driver gets reset handleer called. In the reset
    handler, driver calls 'scsi_done()' callback for same SCSI command packet
    (struct scsi_cmnd) multiple times if there are multiple SCSI command packet
    in the pend_list. More over, if there are entry in the pend_lsit with
    IOCTL packet associated, the driver returns it to wrong free_list so that,
    in turn, the driver could end up with 'NULL pointer dereference..' during
    I/O command building with incorrect resource.

    Also, the patch contains several minor/cosmetic changes besides this.

    Signed-off-by: Seokmann Ju
    Signed-off-by: Andrew Morton
    Signed-off-by: James Bottomley

    Ju, Seokmann
     

14 Dec, 2005

1 commit


21 May, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds