1. 19 4月, 2006 17 次提交
  2. 18 4月, 2006 2 次提交
    • P
      powerpc: Use correct sequence for putting CPU into nap mode · f39224a8
      Paul Mackerras 提交于
      We weren't using the recommended sequence for putting the CPU into
      nap mode.  When I changed the idle loop, for some reason 7447A cpus
      started hanging when we put them into nap mode.  Changing to the
      recommended sequence fixes that.
      
      The complexity here is that the recommended sequence is a loop that
      keeps putting the cpu back into nap mode.  Clearly we need some way
      to break out of the loop when an interrupt (external interrupt,
      decrementer, performance monitor) occurs.  Here we use a bit in
      the thread_info struct to indicate that we need this, and the exception
      entry code notices this and arranges for the exception to return
      to the value in the link register, thus breaking out of the loop.
      We use a new `local_flags' field in the thread_info which we can
      alter without needing to use an atomic update sequence.
      
      The PPC970 has the same recommended sequence, so we do the same thing
      there too.
      
      This also fixes a bug in the kernel stack overflow handling code on
      32-bit, since it was causing a value that we needed in a register to
      get trashed.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      f39224a8
    • D
      [SPARC64]: Export pcibios_resource_to_bus(). · 5fdfd42e
      David S. Miller 提交于
      SYM2 driver uses it.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5fdfd42e
  3. 15 4月, 2006 4 次提交
    • D
      Fix AT91RM9200 build breakage · 2c536200
      David Brownell 提交于
      The at91_cf driver got out of sync with certain changes in the PCMCIA
      layer, notably getting rid of some duplication of data ... causing the
      version merged to kernel.org to fail compiling.
      
      This patch gives the at91_cf platform device a new iomem resource, using
      it so this new pcmcia scheme works.  It also cleans up some whitepsace
      bugs that have accumulated over time (mostly too-long lines).
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      2c536200
    • D
      5fdef394
    • G
      [PATCH] arch/i386/pci/irq.c - new VIA chipsets (fwd) · 40d8b89b
      Grzegorz Janoszka 提交于
      I use 2.6.15.6 Linux kernel and found some problems. I have about 100
      Linux boxes (all with the same (binary the same) kernel). Last time I have
      upgraded all those boxes from 2.4.32 to 2.6.15.6 (first 2.6.15.1, next .2,
      .4 and .6) and I have found some problems on VIA based PC's. Probably the
      reason of this is that some VIA chipsets are unrecognized by IRQ router.
      
      In line 586 there is: /* FIXME: add new ones for 8233/5 */
      
      There were only a few of chipsets ID's there, some of my VIA chipsets were
      not present and kernel used default IRQ router.
      
      I have added three entries, so that the code looks like:
      
              case PCI_DEVICE_ID_VIA_82C596:
              case PCI_DEVICE_ID_VIA_82C686:
              case PCI_DEVICE_ID_VIA_8231:
              case PCI_DEVICE_ID_VIA_8233A:
              case PCI_DEVICE_ID_VIA_8235:
              case PCI_DEVICE_ID_VIA_8237:
              case PCI_DEVICE_ID_VIA_8237_SATA:
                      /* FIXME: add new ones for 8233/5 */
                      r->name = "VIA";
                      r->get = pirq_via_get;
                      r->set = pirq_via_set;
                      return 1;
              }
      
      The kernel goes fine but I haven't testes it for weeks, I'm just a moment
      after reboot :)
      One thing is different (better?):
      Using previus kernel I had:
      PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 0
      now I have:
      PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 11
      
      Maybe it is good idea to add there some more VIA chipsets?
      The ones I have added seem to be OK.
      
      From: Grzegorz Janoszka <Grzegorz@Janoszka.pl>
      Acked-by: NMartin Mares <mj@ucw.cz>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      40d8b89b
    • B
      [PATCH] DMI: move dmi_scan.c from arch/i386 to drivers/firmware/ · 4f705ae3
      Bjorn Helgaas 提交于
      dmi_scan.c is arch-independent and is used by i386, x86_64, and ia64.
      Currently all three arches compile it from arch/i386, which means that ia64
      and x86_64 depend on things in arch/i386 that they wouldn't otherwise care
      about.
      
      This is simply "mv arch/i386/kernel/dmi_scan.c drivers/firmware/" (removing
      trailing whitespace) and the associated Makefile changes.  All three
      architectures already set CONFIG_DMI in their top-level Kconfig files.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Cc: Andi Kleen <ak@muc.de>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Andrey Panin <pazke@orbita1.ru>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      4f705ae3
  4. 14 4月, 2006 9 次提交
  5. 13 4月, 2006 1 次提交
  6. 12 4月, 2006 1 次提交
  7. 11 4月, 2006 6 次提交