Oops in fb_set_cmap caused by palette_cmap.transp uninitialized.

By inspection, fb_blank appears to have the same problem.

into home.transmeta.com:/home/torvalds/v2.5/linux

This removes the agpgart assumption that memory is contiguous.

[Forward port of a 2.4 patch that got applied last month -- DJ] 
 
AGP/DRM currently assume that GATT entries can be converted
to physical addresses with a simple mask.  Additionally, agpgart
assumes in a couple places that the mask is ~0xfff, i.e., that
all the GART control bits are in the low 12 bits.  Both assumptions
are bogus, so:
  
Make agp_memory.memory[] (exported from agpgart to DRM) contain physical
addresses, not GATT entries.
  
DRM assumes agp_memory contains GATT entries, and it converts them to
physical addresses with "paddr = agp_memory.memory[i] & mask".  460GX
requires both a shift and a mask, so exporting plain physical addresses
and a mask of ~0UL allows agpgart to add 460GX support without requiring
DRM interface changes.

- global loops_per_jiffy, x86 cpu_khz and x86
   fast_gettimeoffset_quotient can only be safely adjusted on UP
- x86 per-CPU loops_per_jiffy does not depend on TSC
- save reference values so that rounding errors do not accumulate

Clean up searching code for best frequency multiplier, and add a
safety check. Also, SAFE_FREQ wasn't used.

The "get current speed" algorithm wasn't aware of the disable/enable bit,
and the policy verification function wasn't aware of the N44 / O17
bug. Also, some unused code is removed.

into home.transmeta.com:/home/torvalds/v2.5/linux

into kernel.bkbits.net:/home/davem/net-2.5

into kernel.bkbits.net:/home/davem/sparc-2.5

1. All the memory barriers are SMP-only avoiding unnecessary overhead on UP.
2, My forward porting merge of the rt_rcu patch dropped two changes in
   rt_intern_hash() in around 2.5.43 that ordered the writes while
   inserting a dst entry at the start of a hash chain. The dst entry updates
   must be visible to other (weakly ordered) CPUs before it is inserted.
   The necessary smp_wmb()s are added.
3. Comments to go with the write ordering.

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

  As part of the Linux Kernel Janitors project, I would like to submit my
  patch for sa1100_ir.c.

  The document Documentation/cli-sti-removal.txt says that cli() should no
  longer be used to disable interrupts. This patch removes the last
  references to cli() and {save,restore}_flags, changing them to
  local_irq_save and local_irq_restore respectively.

  This patch for saphir.c isdn driver for Linux removes one call to
  check_region using request_region instead

  I don't have this hardware so patch is not tested at all (I hope I got
  it right).  This patch removes all references to check_region in this
  driver.

  This is patch number 11 in a series of check_region patches I am doing
  as part of the kernel janitors project.

  As part of my work on the Linux Kernel Janitors project, cleaning up on
  functions which call misc_register and don't check for an error
  return, I would like to submit my patch to drivers/sgi/char/usema.c

  This module did not check the return code of misc_register. I found Uttam
  Pawar's patch for this on GeoCrawler
  (http://www.geocrawler.com/archives/3/9221/2002/8/0/9246517/), but it
  doesn't appear to have been applied. This patch basically does exactly the
  same as his, so all credit is due to him.

  This patch for Documentation/DocBook/videobook.tmpl removes two
  references check_region in the documentation using request_region
  instead.

  This patch removes all references to check_region in videobook.tmpl

  This is patch number 29 in a series of check_region patches I am doing as
  part of the kernel janitors project.

  This patch for isdn/hisax/nj_u.c driver for Linux removes one call to
  check_region using request_region instead.

  I don't have this hardware so I hope I got it right.  This patch
  removes all references to check_region in this driver.

  This is patch number 15 in a series of check_region patches I am doing as
  part of the kernel janitors project.

  This patch for sportster.c isdn driver for Linux removes one call to
  check_region using request_region instead

  I don't have this hardware so patch is not tested at all (I hope I got
  it right).  This patch removes all references to check_region in this
  driver.

  This is patch number 10 in a series of check_region patches I am doing
  as part of the kernel janitors project.

  This patch for driver drivers/isdn/hisax/bkm_a8.c for Linux removes
  one call to check_region using request_region instead.

  I don't have this hardware so I hope I got it right.  This patch
  removes all references to check_region in this driver.

  This is patch number 22 in a series of check_region patches I am doing as
  part of the kernel janitors project.

  Since it looks like Linus isn't going to rip the code out...

  As part of my work on the Linux Kernel Janitors project, cleaning up on
  functions which call misc_register and don't check for an error
  return, I would like to submit my patch to drivers/macintosh/via-pmu*.c.

  There is one call in each file which calls misc_register without checking
  the return value. The attached patch should fix that.

  This patch for drivers/isdn/hisax/avm_pci.c isdn driver removes one
  call to check_region using request_region instead

  I don't have this hardware so patch is not tested. This patch removes all
  references to check_region in this driver.

  This is patch number 24 in a series of check_region patches I am doing as
  part of the kernel janitors project.

  This is version 2 of my proposed patch for fdc-io.c tape driver for
  Linux.  It

  	1) removes three calls to check_region using request_region instead.
  	2) in case of fatal error calls release_region to liberate region
	   resources already allocated (as pointed out by Matthew Wilcox my
	   first patch wasn't doing that)

  Remark regarding allocation of regions in this driver:

  If BROKEN_FLOPPY_DRIVER is defined the driver keeps going even if it
  can't allocate one or more region resources.  The driver does not
  store information concerning which allocations succeeded and which
  failed.  When and if subroutine fdc_release_regions is called it will
  then try to release all regions it normally reserves.  I don't know if
  this could cause any trouble in some (rare) situations?

  I don't have this hardware so only compilation is tested.  This patch
  removes all references to check_region in this driver.

  This is patch number 13 in a series of check_region patches I am doing as
  part of the kernel janitors project.