Skip to content
Snippets Groups Projects
  1. Jun 18, 2019
  2. Feb 06, 2019
  3. Jan 22, 2019
    • Finn Thain's avatar
      scsi/atari_scsi: Don't select CONFIG_NVRAM · 83d2aed4
      Finn Thain authored
      
      On powerpc, setting CONFIG_NVRAM=n builds a kernel with no NVRAM support.
      Setting CONFIG_NVRAM=m enables the /dev/nvram misc device module without
      enabling NVRAM support in drivers. Setting CONFIG_NVRAM=y enables the
      misc device (built-in) and also enables NVRAM support in drivers.
      
      m68k shares the valkyriefb driver with powerpc, and since that driver uses
      NVRAM, it is affected by CONFIG_ATARI_SCSI, because of the use of
      "select NVRAM". We can avoid the "select" here, but drivers still have
      to interpret the CONFIG_NVRAM symbol consistently regardless of platform.
      
      In this patch and the subsequent fbdev driver patch, the convention is
      adopted across all relevant platforms whereby NVRAM functionality gets
      enabled in a given device driver when the nvram misc device is built-in
      or when both drivers are modules.
      
      Acked-by: default avatarMichael Schmitz <schmitzmic@gmail.com>
      Signed-off-by: default avatarFinn Thain <fthain@telegraphics.com.au>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      83d2aed4
  4. Jan 12, 2019
  5. Jan 09, 2019
  6. Nov 07, 2018
  7. Nov 06, 2018
  8. Nov 01, 2018
  9. Oct 18, 2018
  10. Aug 27, 2018
  11. Jul 11, 2018
  12. Apr 19, 2018
    • Michael Schmitz's avatar
      scsi: zorro_esp: New driver for Amiga Zorro NCR53C9x boards · 3109e5ae
      Michael Schmitz authored
      
      New combined SCSI driver for all ESP based Zorro SCSI boards for m68k Amiga.
      
      Code largely based on board specific parts of the old drivers (blz1230.c,
      blz2060.c, cyberstorm.c, cyberstormII.c, fastlane.c which were removed after
      the 2.6 kernel series for lack of maintenance) with contributions by Tuomas
      Vainikka (TCQ bug tests and workaround) and Finn Thain (TCQ bugfix by use of
      PIO in extended message in transfer).
      
      New Kconfig option and Makefile entries for new Amiga Zorro ESP SCSI driver
      included in this patch.
      
      Use DMA transfers wherever possible, with board-specific DMA set-up functions
      copied from the old driver code. Three byte reselection messages do appear to
      cause DMA timeouts. So wire up a PIO transfer routine for these
      instead. esp_reselect_with_tag explicitly sets
      esp->cmd_block_dma as target address for the message bytes but PIO
      requires a virtual address.  Substiute kernel virtual address
      esp->cmd_block in PIO transfer call if DMA address is esp->cmd_block_dma
      and phase is message in.
      
      PIO code taken from mac_esp.c where the reselection timeout issue was debugged
      and fixed first, with minor macro and function rename.
      
      Signed-off-by: default avatarMichael Schmitz <schmitzmic@gmail.com>
      Reviewed-by: default avatarFinn Thain <fthain@telegraphics.com.au>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      Tested-by: default avatarChristian T. Steigies <cts@debian.org>
      Tested-by: default avatarJohn Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
      Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      3109e5ae
  13. Mar 20, 2018
  14. Mar 15, 2018
  15. Feb 14, 2018
  16. Nov 02, 2017
    • Arnd Bergmann's avatar
      block: fix CDROM dependency on BLK_DEV · c091fbe9
      Arnd Bergmann authored
      
      After the cdrom cleanup, I get randconfig warnings for some configurations:
      
      warning: (BLK_DEV_IDECD && BLK_DEV_SR) selects CDROM which has unmet direct dependencies (BLK_DEV)
      
      This adds an explicit BLK_DEV dependency for both drivers. The other
      drivers that select 'CDROM' already have this and don't need a change.
      
      Fixes: 2a750166 ("block: Rework drivers/cdrom/Makefile")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      c091fbe9
  17. Nov 01, 2017
  18. Oct 12, 2017
  19. Sep 05, 2017
    • Arnd Bergmann's avatar
      scsi: scsi_transport_sas: select BLK_DEV_BSGLIB · 580b71e9
      Arnd Bergmann authored
      
      Without CONFIG_BLK_DEV_BSGLIB, we get a link error here:
      
      drivers/scsi/scsi_transport_sas.o: In function `sas_bsg_initialize':
      scsi_transport_sas.c:(.text+0xcc0): undefined reference to `bsg_setup_queue'
      scsi_transport_sas.c:(.text+0xd10): undefined reference to `bsg_setup_queue'
      drivers/scsi/scsi_transport_sas.o: In function `sas_smp_dispatch':
      scsi_transport_sas.c:(.text+0xe8c): undefined reference to `bsg_job_done'
      
      This modifies the Kconfig 'select' statement accordingly, and matching
      what we do for the other two scsi_transport implementations that use
      bsglib.
      
      Fixes: 651a0136 ("scsi: scsi_transport_sas: switch to bsg-lib for SMP passthrough")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      580b71e9
  20. Aug 17, 2017
  21. Jul 25, 2017
  22. Jun 28, 2017
  23. Mar 15, 2017
    • James Smart's avatar
      scsi: lpfc: Finalize Kconfig options for nvme · 7d708033
      James Smart authored
      
      Reviewing the result of what was just added for Kconfig, we made a poor
      choice. It worked well for full kernel builds, but not so much for how
      it would be deployed on a distro.
      
      Here's the final result:
      - lpfc will compile in NVME initiator and/or NVME target support based
        on whether the kernel has the corresponding subsystem support.
        Kconfig is not used to drive this specifically for lpfc.
      - There is a module parameter, lpfc_enable_fc4_type, that indicates
        whether the ports will do FCP-only or FCP & NVME (NVME-only not yet
        possible due to dependency on fc transport). As FCP & NVME divvys up
        exchange resources, and given NVME will not be often initially, the
        default is changed to FCP only.
      
      Signed-off-by: default avatarDick Kennedy <dick.kennedy@broadcom.com>
      Signed-off-by: default avatarJames Smart <james.smart@broadcom.com>
      Signed-off-by: default avatarMartin K. Petersen <martin.petersen@oracle.com>
      7d708033
  24. Mar 07, 2017
  25. Feb 23, 2017
  26. Feb 22, 2017
  27. Jan 31, 2017
  28. Dec 14, 2016
  29. Nov 18, 2016
  30. Nov 08, 2016
Loading