1. 07 9月, 2005 1 次提交
  2. 05 9月, 2005 1 次提交
  3. 31 8月, 2005 1 次提交
    • J
      [SCSI] embryonic RAID class · 61a7afa2
      James Bottomley 提交于
      The idea behind a RAID class is to provide a uniform interface to all
      RAID subsystems (both hardware and software) in the kernel.
      
      To do that, I've made this class a transport class that's entirely
      subsystem independent (although the matching routines have to match per
      subsystem, as you'll see looking at the code).  I put it in the scsi
      subdirectory purely because I needed somewhere to play with it, but it's
      not a scsi specific module.
      
      I used a fusion raid card as the test bed for this; with that kind of
      card, this is the type of class output you get:
      
      jejb@titanic> ls -l /sys/class/raid_devices/20\:0\:0\:0/
      total 0
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 component-0 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:0/20:1:0:0/
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 component-1 -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:1:1/20:1:1:0/
      lrwxrwxrwx  1 root root     0 Aug 16 17:21 device -> ../../../devices/pci0000:80/0000:80:04.0/host20/target20:0:0/20:0:0:0/
      -r--r--r--  1 root root 16384 Aug 16 17:21 level
      -r--r--r--  1 root root 16384 Aug 16 17:21 resync
      -r--r--r--  1 root root 16384 Aug 16 17:21 state
      
      So it's really simple: for a SCSI device representing a hardware raid,
      it shows the raid level, the array state, the resync % complete (if the
      state is resyncing) and the underlying components of the RAID (these are
      exposed in fusion on the virtual channel 1).
      
      As you can see, this type of information can be exported by almost
      anything, including software raid.
      
      The more difficult trick, of course, is going to be getting it to
      perform configuration type actions with writable attributes.
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      61a7afa2
  4. 24 8月, 2005 1 次提交
  5. 06 8月, 2005 1 次提交
  6. 31 7月, 2005 1 次提交
    • A
      [PATCH] SCSI_SATA has to be a tristate · faa72533
      Adrian Bunk 提交于
      SCSI=m must disallow static drivers.
      
      The problem is that all the SATA drivers depend on SCSI_SATA.
      
      With SCSI=m and SCSI_SATA=y this allows the static enabling of the SATA
      drivers with unwanted effects, e.g.:
      - SCSI=m, SCSI_SATA=y, SCSI_ATA_ADMA=y
        -> SCSI_ATA_ADMA is built statically but scsi/built-in.o is not linked
           into the kernel
      - SCSI=m, SCSI_SATA=y, SCSI_ATA_ADMA=y, SCSI_SATA_AHCI=m
        -> SCSI_ATA_ADMA and libata are built statically but
           scsi/built-in.o is not linked into the kernel,
           SCSI_SATA_AHCI is built modular (unresolved symbols due to missing
                                            libata)
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Cc: Jeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      faa72533
  7. 13 6月, 2005 1 次提交
  8. 21 5月, 2005 2 次提交
  9. 04 5月, 2005 1 次提交
  10. 19 4月, 2005 1 次提交
  11. 17 4月, 2005 2 次提交
    • [PATCH] finally fix 53c700 to use the generic iomem infrastructure · 56fece20
      提交于
      This driver has had it's own different infrastructure for doing this for
      ages, but it's time it used the common one.
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      56fece20
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4