1. 14 Jun, 2005 9 commits
  2. 13 Jun, 2005 23 commits
  3. 12 Jun, 2005 1 commit
    • David Brownell's avatar
      [PATCH] ARM: 2709/1: Systems with PCMCIA should also see IDE options (for CompactFlash memories) · bb011b8e
      David Brownell authored
      Patch from David Brownell
      
      The ARM generic Kconfig filters out IDE options ... except for
      an error prone ARMload of special cases.
      This adds one general case to the systems that will offer IDE options:
      kernels with PCMCIA support, which probably want to use IDE to access
      CompactFlash cards.  This might allow many (most?) of the other cases
      to disappear, for systems that only see IDE hardware through CF cards.
      Right now this one patch is used to gate access to CF cards, including
      MicroDrives, for both omap_cf and at91_cf drivers.
      
      Signed-off-by: David Brownell
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      bb011b8e
  4. 11 Jun, 2005 2 commits
  5. 10 Jun, 2005 4 commits
    • Linus Torvalds's avatar
      ppc: remove two extraneous descriptors for the 405EP CPU · 90abb7b5
      Linus Torvalds authored
      The patch to add them keeps on getting applied, over and
      over again ;)
      
      Hopefully no more.
      90abb7b5
    • Dave Airlie's avatar
      [PATCH] remove bogus hack from radeon IRQ handler · 74e8ebc5
      Dave Airlie authored
      This removes a bogus hack from the radeon IRQ handler.
      There is a better fix from myself and benh in DRM CVS but I'll wait
      until 2.6.13-rc so it gets more testing.
      Signed-off-by: default avatarDave Airlie <airlied@linux.ie>
      74e8ebc5
    • Dave Airlie's avatar
      [PATCH] drm add i945G pci id · e98ded32
      Dave Airlie authored
      Add pci identifier for i945G chipset
      Signed-off-by: default avatarDave Airlie <airlied@linux.ie>
      e98ded32
    • Benjamin Herrenschmidt's avatar
      [PATCH] ppc32: Fix nasty sleep/wakeup problem · 0086b5ec
      Benjamin Herrenschmidt authored
      Despite all the care lately in making the powermac sleep/wakeup as
      robust as possible, there is still a nasty related to the use of cpufreq
      on PMU based machines.  Unfortunately, it affects paulus old powerbook
      so I have to fix it :)
      
      We didn't manage to understand what is precisely going on, it leads to
      memory corruption and might have to do with RAM not beeing properly
      refreshed when a cpufreq transition is done right before the sleep.
      
      The best workaround (and less intrusive at this point) we could come up
      with is included in this patch.  We basically do _not_ force a switch to
      high speed on suspend anymore (that is what is causing the problem) on
      those machines.  We still force a speed switch on wakeup (since we don't
      know what speed we are coming back from sleep at, and that seems to work
      fine).
      
      Since, during this short interval, the actual CPU speed might be
      incorrect, we also hack around by multiplying loops_per_jiffy by 2 (max
      speed factor on those machines) during early wakeup stage to make sure
      udelay's during that time aren't too short.
      
      For after 2.6.12, we'll change udelay implementation to use the CPU
      timebase (which is always constant) instead like we do on ppc64 and thus
      get rid of all those problems.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0086b5ec
  6. 09 Jun, 2005 1 commit
    • Michael Ellerman's avatar
      [PATCH] iseries_veth: Supress spurious WARN_ON() at module unload · 243cd55e
      Michael Ellerman authored
      My patch from a few weeks back (now in mainline), called "Cleanup skbs to
      prevent unregister_netdevice() hanging", can cause our TX timeout code to
      fire on machines with lots of VLANs (because it takes > 2 seconds between
      when we stop the queues and when we're finished stopping the connections).
      
      When that happens the TX timeout code freaks out and does a WARN_ON()
      because as far as it's concerned there shouldn't be a TX timeout happening,
      which is fair enough.
      
      I have a "proper" fix for this, which is to a) do refcounting on
      connections and b) implement a proper ack timer so we don't keep unacked
      skbs lying around for ever.  But for 2.6.12 I propose just supressing the
      WARN_ON().  Users will still see the "NETDEV WATCHDOG" warning, but that's
      not nearly as bad as a WARN_ON() which users interpret as an Oops.
      Signed-off-by: default avatarMichael Ellerman <michael@ellerman.id.au>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      243cd55e