1. 05 5月, 2010 2 次提交
  2. 04 5月, 2010 3 次提交
    • T
      omap2/3: Fix DEBUG_LL for omap zoom2/3 · a4f57b81
      Tony Lindgren 提交于
      Zoom2 and 3 have UARTs only on the external debug board.
      GPMC needs to be mapped early to use it for DEBUG_LL.
      
      Additionally, 0xfb000000 overlaps with other areas, so
      use 0xfa400000 for the virtual address instead.
      
      Note that with the pending serial.c patches you need to
      set console=ttyS0,115200n8 as it will be the only UART
      mapped. To use DEBUG_LL, you need to pass also earlyprintk
      in cmdline.
      
      Cc: Allen Pais <allen.pais@ti.com>
      Acked-by: NVikram Pandita <vikram.pandita@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      a4f57b81
    • T
      omap: Use a memory address for storing the debug port info instead of UART1 scratchpad · 96554d70
      Tony Lindgren 提交于
      This removes the dependency to the UART1 being available for storing
      the debug configuration in uncompress.h. This will simplify the
      DEBUG_LL UART configuration for boards that may not have UART1, or
      have an external UART as it requires only one mapping for DEBUG_LL.
      
      The patch has a few limitations. Basically now we're assuming that
      the kernel uncompress code won't overlap with OMAP_UART_INFO. We also
      assume the printascii is called at least once before paging_init in
      order for addruart to have a chance to read the UART setup from
      OMAP_UART_INFO.
      
      As suggested by Cyril Chemparathy <cyril@ti.com>,
      Vikram Pandita <vikram.pandita@ti.com> and
      Kevin Hilman <khilman@deeprootsystems.com>. Based on an earlier
      patch posted for Davinci by Cyril Chemparathy <cyril@ti.com>.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      96554d70
    • T
      omap2/3/4: Fix multi.h when omap3 and omap4 are selected without omap2 · daa49495
      Tony Lindgren 提交于
      Otherwise we'll get an error about get_irqnr_and_base being defined
      twice. Add an entry for omap4, and use ARCH_OMAP3 for omap3 instead of
      ARCH_OMAP3430.
      
      Also fix the check for omap1 to use ARCH_OMAP2PLUS to avoid having to
      add ARCH_OMAP4 separately there.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      daa49495
  3. 30 4月, 2010 1 次提交
  4. 29 4月, 2010 2 次提交
  5. 28 4月, 2010 4 次提交
  6. 27 4月, 2010 2 次提交
  7. 25 4月, 2010 1 次提交
    • D
      VMware Balloon driver · 453dc659
      Dmitry Torokhov 提交于
      This is a standalone version of VMware Balloon driver.  Ballooning is a
      technique that allows hypervisor dynamically limit the amount of memory
      available to the guest (with guest cooperation).  In the overcommit
      scenario, when hypervisor set detects that it needs to shuffle some
      memory, it instructs the driver to allocate certain number of pages, and
      the underlying memory gets returned to the hypervisor.  Later hypervisor
      may return memory to the guest by reattaching memory to the pageframes and
      instructing the driver to "deflate" balloon.
      
      We are submitting a standalone driver because KVM maintainer (Avi Kivity)
      expressed opinion (rightly) that our transport does not fit well into
      virtqueue paradigm and thus it does not make much sense to integrate with
      virtio.
      
      There were also some concerns whether current ballooning technique is the
      right thing.  If there appears a better framework to achieve this we are
      prepared to evaluate and switch to using it, but in the meantime we'd like
      to get this driver upstream.
      
      We want to get the driver accepted in distributions so that users do not
      have to deal with an out-of-tree module and many distributions have
      "upstream first" requirement.
      
      The driver has been shipping for a number of years and users running on
      VMware platform will have it installed as part of VMware Tools even if it
      will not come from a distribution, thus there should not be additional
      risk in pulling the driver into mainline.  The driver will only activate
      if host is VMware so everyone else should not be affected at all.
      Signed-off-by: NDmitry Torokhov <dtor@vmware.com>
      Cc: Avi Kivity <avi@redhat.com>
      Cc: Jeremy Fitzhardinge <jeremy@goop.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      453dc659
  8. 24 4月, 2010 25 次提交