1. 14 12月, 2016 1 次提交
  2. 19 12月, 2013 1 次提交
  3. 09 10月, 2012 1 次提交
  4. 20 7月, 2012 1 次提交
    • H
      s390/comments: unify copyright messages and remove file names · a53c8fab
      Heiko Carstens 提交于
      Remove the file name from the comment at top of many files. In most
      cases the file name was wrong anyway, so it's rather pointless.
      
      Also unify the IBM copyright statement. We did have a lot of sightly
      different statements and wanted to change them one after another
      whenever a file gets touched. However that never happened. Instead
      people start to take the old/"wrong" statements to use as a template
      for new files.
      So unify all of them in one go.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      a53c8fab
  5. 02 8月, 2008 1 次提交
  6. 14 7月, 2008 1 次提交
  7. 26 1月, 2008 1 次提交
  8. 12 10月, 2007 1 次提交
  9. 04 12月, 2006 1 次提交
  10. 20 9月, 2006 2 次提交
    • R
      [S390] zcrypt secure key cryptography extension. · 5432114b
      Ralph Wuerthner 提交于
      Allow the user space to send extended cprb messages directly to the
      PCIXCC / CEX2C cards. This allows the CCA library to construct special
      crypto requests that use "secure" keys that are stored on the card.
      Signed-off-by: NRalph Wuerthner <rwuerthn@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      5432114b
    • M
      [S390] zcrypt user space interface. · 2dbc2418
      Martin Schwidefsky 提交于
      The user space interface of the zcrypt device driver implements the old
      user space interface as defined by the old z90crypt driver. Everything
      is there, the /dev/z90crypt misc character device, all the lovely ioctls
      and the /proc file. Even writing to the z90crypt proc file to configure
      the crypto device still works. It stands to reason to remove the proc
      write function someday since a much cleaner configuration via the sysfs
      is now available.
      
      The ap bus device drivers register crypto cards to the zcrypt user
      space interface. The request router of the user space interface
      picks one of the registered cards based on the predicted latency
      for the request and calls the driver via a callback found in the
      zcrypt_ops of the device. The request router only knows which
      operations the card can do and the minimum / maximum number of bits
      a request can have.
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NRalph Wuerthner <rwuerthn@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      2dbc2418