1. 27 Jul, 2011 3 commits
  2. 26 Jul, 2011 12 commits
  3. 25 Jul, 2011 3 commits
  4. 22 Jul, 2011 2 commits
  5. 18 Jul, 2011 2 commits
  6. 17 Jul, 2011 3 commits
    • Mingkai Hu's avatar
      powerpc/p2041rdb: Add p2041rdb board support · 4f1d1b7d
      Mingkai Hu authored
      P2041RDB Specification:
      Memory subsystem:
       * 4Gbyte unbuffered DDR3 SDRAM SO-DIMM(64bit bus)
       * 128 Mbyte NOR flash single-chip memory
       * 256 Kbit M24256 I2C EEPROM
       * 16 Mbyte SPI memory
       * SD connector to interface with the SD memory card
       * dTSEC1: connected to the Vitesse SGMII PHY (VSC8221)
       * dTSEC2: connected to the Vitesse SGMII PHY (VSC8221)
       * dTSEC3: connected to the Vitesse SGMII PHY (VSC8221)
       * dTSEC4: connected to the Vitesse RGMII PHY (VSC8641)
       * dTSEC5: connected to the Vitesse RGMII PHY (VSC8641)
       * Lanes E, F, G and H of Bank1 are connected to one x4 PCIe SLOT1
       * Lanes C and Land D of Bank2 are connected to one x4 PCIe SLOT2
      SATA: Lanes C and Land D of Bank2 are connected to two SATA connectors
      USB 2.0: connected via a internal UTMI PHY to two TYPE-A interfaces
       * I2C1: Real time clock, Temperature sensor, Memory module
       * I2C2: Vcore Regulator, 256Kbit I2C Bus EEPROM, PCIe slot1/2
      UART: supports two UARTs up to 115200 bps for console
      Signed-off-by: default avatarMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
    • Albert ARIBAUD's avatar
      Remove volatile qualifier in get_ram_size() calls · a55d23cc
      Albert ARIBAUD authored
      Checkpatch.pl complains about the volatile qualifier in calls to
      get_ram_size(). Remove this qualifier in the prototype and in the
      calls where it is useless, and leave it only in the function body
      where it is needed.
      Signed-off-by: default avatarAlbert ARIBAUD <albert.u.boot@aribaud.net>
    • Chan-Taek Park's avatar
      TI: TNETV107X Fix Build Error · 930f3355
      Chan-Taek Park authored
      This patch provides SDRAM base address and initial stack address to fix
      build errors.
      Signed-off-by: default avatarChan-Taek Park <c-park@ti.com>
  7. 16 Jul, 2011 4 commits
  8. 15 Jul, 2011 4 commits
    • Gerald Van Baren's avatar
      fdt: introduce fdt_create_phandle() · a8d2a75d
      Gerald Van Baren authored
      The ePAPR specification says that phandle properties should be called
      "phandle", and not "linux,phandle".  To facilitate the migration from
      "linux,phandle" to "phandle", introduce function fdt_create_phandle(),
      which creates a phandle in a given node.  For now, we create both the
      "phandle" and "linux,phandle" properties.  A later version of this
      function will remove support for "linux,phandle".
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
    • Timur Tabi's avatar
      fdt: add prototype for fdt_increase_size() · b3606f14
      Timur Tabi authored
      Add a prototype for fdt_increase_size() so that anyone can call it.
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
    • Timur Tabi's avatar
      fdt: introduce fdt_verify_alias_address() and fdt_get_base_address() · bb682001
      Timur Tabi authored
      Introduce two functions, fdt_verify_alias_address() and
      fdt_get_base_address(), which can be used to verify the physical address
      of a device in a device tree.
      fdt_get_base_address() returns the base address of an SOC or PCI node.
      fdt_verify_alias_address() prints a message if the address of a node
      specified by an alias does not match the given physical address.
      Signed-off-by: default avatarTimur Tabi <timur@freescale.com>
    • David Gibson's avatar
      libfdt: Implement property iteration functions · d1c63148
      David Gibson authored
      For ages, we've been talking about adding functions to libfdt to allow
      iteration through properties.  So, finally, here are some.
      I got bogged down on this for a long time because I didn't want to
      expose offsets directly to properties to the callers.  But without
      that, attempting to make reasonable iteration functions just became
      horrible.  So eventually, I settled on an interface which does now
      expose property offsets.  fdt_first_property_offset() and
      fdt_next_property_offset() are used to step through the offsets of the
      properties starting from a particularly node offset.  The details of
      the property at each offset can then be retrieved with either
      fdt_get_property_by_offset() or fdt_getprop_by_offset() which have
      interfaces similar to fdt_get_property() and fdt_getprop()
      No explicit testcases are included, but we do use the new functions to
      reimplement the existing fdt_get_property() function.
      Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
      This was extracted from the DTC commit:
      73dca9ae0b9abe6924ba640164ecce9f8df69c5a Mon Sep 17 00:00:00 2001
      Signed-off-by: default avatarGerald Van Baren <vanbaren@cideas.com>
  9. 14 Jul, 2011 6 commits
  10. 11 Jul, 2011 1 commit