1. 02 6月, 2011 1 次提交
    • R
      ARM: Allow SoCs to enable scatterlist chaining · 74facffe
      Russell King 提交于
      Allow SoCs to enable the scatterlist chaining support, which allows
      scatterlist tables to be broken up into smaller allocations.
      
      As support for this feature depends on the implementation details of
      the users of the scatterlists, we can't enable this globally without
      auditing all the users, which is a very big task.  Instead, let SoCs
      progressively switch over to using this.
      
      SoC drivers using scatterlists and SoC DMA implementations need
      auditing before this option can be enabled for the SoC.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      74facffe
  2. 28 5月, 2010 1 次提交
  3. 15 5月, 2010 1 次提交
  4. 03 8月, 2008 1 次提交
  5. 23 10月, 2007 2 次提交
    • J
      Add CONFIG_DEBUG_SG sg validation · d6ec0842
      Jens Axboe 提交于
      Add a Kconfig entry which will toggle some sanity checks on the sg
      entry and tables.
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      d6ec0842
    • J
      Change table chaining layout · 18dabf47
      Jens Axboe 提交于
      Change the page member of the scatterlist structure to be an unsigned
      long, and encode more stuff in the lower bits:
      
      - Bits 0 and 1 zero: this is a normal sg entry. Next sg entry is located
        at sg + 1.
      - Bit 0 set: this is a chain entry, the next real entry is at ->page_link
        with the two low bits masked off.
      - Bit 1 set: this is the final entry in the sg entry. sg_next() will return
        NULL when passed such an entry.
      
      It's thus important that sg table users use the proper accessors to get
      and set the page member.
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      18dabf47
  6. 04 1月, 2006 1 次提交
  7. 17 4月, 2005 1 次提交
    • 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