1. 29 11月, 2011 1 次提交
  2. 26 7月, 2011 1 次提交
    • R
      iomap: make IOPORT/PCI mapping functions conditional · fea80311
      Randy Dunlap 提交于
      When CONFIG_PCI is not enabled, CONFIG_EISA=y, and CONFIG_GENERIC_IOMAP=y,
      drivers/net/3c59x.c build fails due to a recent small change to
      <asm-generic/iomap.h> that surrounds pci_iomap() and pci_iounmap() with
      #ifdef CONFIG_PCI/#endif.
      
      Since that patch to iomap.h looks correct, add stubs for pci_iomap() and
      pci_iounmap() with CONFIG_PCI is not enabled to fix the build errors.
      
        drivers/net/3c59x.c:1026: error: implicit declaration of function 'pci_iomap'
        drivers/net/3c59x.c:1038: error: implicit declaration of function 'pci_iounmap'
      Signed-off-by: NRandy Dunlap <rdunlap@xenotime.net>
      Cc: Jonas Bonn <jonas@southpole.se>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      fea80311
  3. 23 7月, 2011 1 次提交
  4. 25 4月, 2008 1 次提交
  5. 09 2月, 2008 1 次提交
  6. 17 4月, 2005 2 次提交
    • J
      [PATCH] add Big Endian variants of ioread/iowrite · dae409a2
      James Bottomley 提交于
      In the new io infrastructure, all of our operators are expecting the
      underlying device to be little endian (because the PCI bus, their main
      consumer, is LE).
      
      However, there are a fair few devices and busses in the world that are
      actually Big Endian.  There's even evidence that some of these BE bus and
      chip types are attached to LE systems.  Thus, there's a need for a BE
      equivalent of our io{read,write}{16,32} operations.
      
      The attached patch adds this as io{read,write}{16,32}be.  When it's in,
      I'll add the first consume (the 53c700 SCSI chip driver).
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      dae409a2
    • 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