1. 04 Aug, 2005 14 commits
  2. 03 Aug, 2005 20 commits
  3. 02 Aug, 2005 6 commits
    • Linus Torvalds's avatar
      pci: make bus resource start address override minimum IO address · 688d1918
      Linus Torvalds authored
      The reason we have PCIBIOS_MIN_IO and PCIBIOS_MIN_CARDBUS_IO is because
      we want to protect badly documented motherboard PCI resources and thus
      don't want to allocate new resources in low IO/MEM space.
      
      However, if we have already discovered a PCI bridge with a specified
      resource base, that should override that decision.
      
      This change will allow us to move the "careful" region upwards without
      resulting in problems allocating resources in low mappings.  This was
      brought on by us having allocated a bus resource at 0x1000, conflicting
      with a undocumented VAIO Sony PI resources.
      688d1918
    • Jens Axboe's avatar
      [PATCH] cfq-iosched: fix problem with barriers and max_depth == 1 · d7ed538a
      Jens Axboe authored
      CFQ will currently stall when using write barriers and the default
      max_depth setting of 1, since we artificially need a depth of 2 when
      pre-pending the first flush. So never deny the barrier request going to
      the device.
      
      This is a regression since 2.6.12, it was found in SUSE testing.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      d7ed538a
    • Olaf Hering's avatar
      [PATCH] aic byteorder fixes after recent cleanup · f7c80c9f
      Olaf Hering authored
      Rebuild the aic7xxx firmware doesn't work anymore after this change
      which appeared int 2.6.13-rc1:
      
         [SCSI] aic7xxx/aic79xx: remove useless byte order macro cruft
      
      Two files did not include byteorder.h, resulting in aic dying with a panic
      
      	"Unknown opcode encountered in seq program"
      
      This fixes it for me.
      Signed-off-by: default avatarOlaf Hering <olh@suse.de>
      Acked-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      f7c80c9f
    • Paul Mackerras's avatar
      [PATCH] Obvious bugfix for yenta resource allocation · f7d1d23c
      Paul Mackerras authored
      Recent changes (well, dating from 12 July) have broken cardbus on my
      powerbook: I get 3 messages saying "no resource of type xxx available,
      trying to continue", and if I plug in my wireless card, it complains
      that there are no resources allocated to the card.  This all worked in
      2.6.12.
      
      Looking at the code in yenta_socket.c, function yenta_allocate_res,
      it's obvious what is wrong: if we get to line 639 (i.e. there wasn't a
      usable preassigned resource), we will always flow through to line 668,
      which is the printk that I was seeing, even if a resource was
      successfully allocated.  It looks to me as though there should be a
      return statement after the two config_writel's in each of the 3
      branches of the if statements, so that the function returns after
      successfully setting up the resource.
      
      The patch below adds these return statements, and with this patch,
      cardbus works on my powerbook once again.
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      Acked-by: default avatarDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      f7d1d23c
    • Linus Torvalds's avatar
      Linux v2.6.13-rc5 · 9a351e30
      Linus Torvalds authored
      Ok, let's get it right this time
      9a351e30
    • Mike Kravetz's avatar
      [PATCH] ppc64: POWER 4 fails to boot with NUMA · 96cd5b08
      Mike Kravetz authored
      If CONFIG_NUMA is set, some POWER 4 systems will fail to boot.  This is
      because of special processing needed to handle invalid node IDs (0xffff) on
      POWER 4.  My previous patch to handle memory 'holes' within nodes forgot to
      add this special case for POWER 4 in one place.
      
      In reality, I'm not sure that configuring the kernel for NUMA on POWER 4 makes
      much sense.  Are there POWER 4 based systems with NUMA characteristics that
      are presented by the firmware?  But, distros want one kernel for all systems
      so NUMA is on by default in their kernels.  The patch handles those cases.
      Signed-off-by: default avatarMike Kravetz <kravetz@us.ibm.com>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      96cd5b08