1. 25 Aug, 2014 1 commit
    • Heiko Schocher's avatar
      mtd, ubi, ubifs: resync with Linux-3.14 · ff94bc40
      Heiko Schocher authored
      resync ubi subsystem with linux:
      
      commit 455c6fdbd219161bd09b1165f11699d6d73de11c
      Author: Linus Torvalds <torvalds@linux-foundation.org>
      Date:   Sun Mar 30 20:40:15 2014 -0700
      
          Linux 3.14
      
      A nice side effect of this, is we introduce UBI Fastmap support
      to U-Boot.
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      Signed-off-by: default avatarTom Rini <trini@ti.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Sergey Lapin <slapin@ossfans.org>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Joerg Krause <jkrause@posteo.de>
      ff94bc40
  2. 30 Jul, 2014 2 commits
    • Masahiro Yamada's avatar
      Add board MAINTAINERS files · 93d4334f
      Masahiro Yamada authored
      We have switched to Kconfig and the boards.cfg file is going to
      be removed. We have to retrieve the board status and maintainers
      information from it.
      
      The MAINTAINERS format as in Linux Kernel would be nice
      because we can crib the scripts/get_maintainer.pl script.
      
      After some discussion, we chose to put a MAINTAINERS file under each
      board directory, not the top-level one because we want to collect
      relevant information for a board into a single place.
      
      TODO:
      Modify get_maintainer.pl to scan multiple MAINTAINERS files.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Suggested-by: default avatarTom Rini <trini@ti.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      93d4334f
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      dd84058d
  3. 25 Nov, 2013 2 commits
  4. 01 Nov, 2013 1 commit
  5. 20 Aug, 2013 1 commit
  6. 24 Jul, 2013 1 commit
  7. 27 Nov, 2012 1 commit
    • Andy Fleming's avatar
      8xxx: Change all 8*xx_DDR addresses to 8xxx · e76cd5d4
      Andy Fleming authored
      There were a number of shared files that were using
      CONFIG_SYS_MPC85xx_DDR_ADDR, or CONFIG_SYS_MPC86xx_DDR_ADDR, and
      several variants (DDR2, DDR3). A recent patchset added
      85xx-specific ones to code which was used by 86xx systems.
      After reviewing places where these constants were used, and
      noting that the type definitions of the pointers assigned to
      point to those addresses were the same, the cleanest approach
      to fixing this problem was to unify the namespace for the
      85xx, 83xx, and 86xx DDR address definitions.
      
      This patch does:
      
      s/CONFIG_SYS_MPC8.xx_DDR/CONFIG_SYS_MPC8xxx_DDR/g
      
      All 85xx, 86xx, and 83xx have been built with this change.
      Signed-off-by: default avatarAndy Fleming <afleming@freescale.com>
      Tested-by: default avatarAndy Fleming <afleming@freescale.com>
      Acked-by: default avatarKim Phillips <kim.phillips@freescale.com>
      e76cd5d4
  8. 15 Oct, 2011 1 commit
  9. 03 Oct, 2011 1 commit
  10. 12 May, 2011 1 commit
    • Wolfgang Denk's avatar
      Fix incorrect use of getenv() before relocation · f0c0b3a9
      Wolfgang Denk authored
      A large number of boards incorrectly used getenv() in their board init
      code running before relocation.  In some cases this caused U-Boot to
      hang when certain environment variables grew too long.
      Fix the code to use getenv_r().
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Cc: Stefan Roese <sr@denx.de>
      Cc: The LEOX team <team@leox.org>
      Cc: Michael Schwingen <michael@schwingen.org>
      Cc: Georg Schardt <schardt@team-ctech.de>
      Cc: Werner Pfister <Pfister_Werner@intercontrol.de>
      Cc: Dirk Eibach <eibach@gdsys.de>
      Cc: Peter De Schrijver <p2@mind.be>
      Cc: John Zhan <zhanz@sinovee.com>
      Cc: Rishi Bhattacharya <rishi@ti.com>
      Cc: Peter Tyser <ptyser@xes-inc.com>
      f0c0b3a9
  11. 04 Apr, 2011 2 commits
  12. 14 Jan, 2011 2 commits
    • Becky Bruce's avatar
      mpc85xx boards: initdram() cleanup/bugfix · 38dba0c2
      Becky Bruce authored
      Correct initdram to use phys_size_t to represent the size of
      dram; instead of changing this all over the place, and correcting
      all the other random errors I've noticed, create a
      common initdram that is used by all non-corenet 85xx parts.  Most
      of the initdram() functions were identical, with 2 common differences:
      
      1) DDR tlbs for the fixed_sdram case were set up in initdram() on
      some boards, and were part of the tlb_table on others.  I have
      changed them all over to the initdram() method - we shouldn't
      be accessing dram before this point so they don't need to be
      done sooner, and this seems cleaner.
      
      2) Parts that require the DDR11 erratum workaround had different
      implementations - I have adopted the version from the Freescale
      errata document.  It also looks like some of the versions were
      buggy, and, depending on timing, could have resulted in the
      DDR controller being disabled.  This seems bad.
      
      The xpedite boards had a common/fsl_8xxx_ddr.c; with this
      change only the 517 board uses this so I have moved the ddr code
      into that board's directory in xpedite517x.c
      Signed-off-by: default avatarBecky Bruce <beckyb@kernel.crashing.org>
      Tested-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      38dba0c2
    • Becky Bruce's avatar
      socrates: rename sdram_setup fixed_sdram() · 2e81ad05
      Becky Bruce authored
      This will help us go to a fixed initdram() for all 85xx boards going
      forward.  sdram_setup() had an argument that it didn't need, since the
      value was #defined.
      Signed-off-by: default avatarBecky Bruce <beckyb@kernel.crashing.org>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      2e81ad05
  13. 17 Nov, 2010 1 commit
    • Sebastien Carlier's avatar
      Switch from archive libraries to partial linking · 6d8962e8
      Sebastien Carlier authored
      Before this commit, weak symbols were not overridden by non-weak symbols
      found in archive libraries when linking with recent versions of
      binutils.  As stated in the System V ABI, "the link editor does not
      extract archive members to resolve undefined weak symbols".
      
      This commit changes all Makefiles to use partial linking (ld -r) instead
      of creating library archives, which forces all symbols to participate in
      linking, allowing non-weak symbols to override weak symbols as intended.
      This approach is also used by Linux, from which the gmake function
      cmd_link_o_target (defined in config.mk and used in all Makefiles) is
      inspired.
      
      The name of each former library archive is preserved except for
      extensions which change from ".a" to ".o".  This commit updates
      references accordingly where needed, in particular in some linker
      scripts.
      
      This commit reveals board configurations that exclude some features but
      include source files that depend these disabled features in the build,
      resulting in undefined symbols.  Known such cases include:
      - disabling CMD_NET but not CMD_NFS;
      - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.
      Signed-off-by: default avatarSebastien Carlier <sebastien.carlier@gmail.com>
      6d8962e8
  14. 18 Oct, 2010 2 commits
    • Wolfgang Denk's avatar
      Makefile: move all Power Architecture boards into boards.cfg · 2ae18241
      Wolfgang Denk authored
      Clean up Makefile, and drop a lot of the config.mk files on the way.
      
      We now also automatically pick all boards that are listed in
      boards.cfg (and with all configurations), so we can drop the redundant
      entries from MAKEALL to avoid building these twice.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      2ae18241
    • Wolfgang Denk's avatar
      Rename TEXT_BASE into CONFIG_SYS_TEXT_BASE · 14d0a02a
      Wolfgang Denk authored
      The change is currently needed to be able to remove the board
      configuration scripting from the top level Makefile and replace it by
      a simple, table driven script.
      
      Moving this configuration setting into the "CONFIG_*" name space is
      also desirable because it is needed if we ever should move forward to
      a Kconfig driven configuration system.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      14d0a02a
  15. 19 Sep, 2010 1 commit
  16. 16 Jul, 2010 1 commit
    • Becky Bruce's avatar
      83xx/85xx/86xx: LBC register cleanup · f51cdaf1
      Becky Bruce authored
      Currently, 83xx, 86xx, and 85xx have a lot of duplicated code
      dedicated to defining and manipulating the LBC registers.  Merge
      this into a single spot.
      
      To do this, we have to decide on a common name for the data structure
      that holds the lbc registers - it will now be known as fsl_lbc_t, and we
      adopt a common name for the immap layouts that include the lbc - this was
      previously known as either im_lbc or lbus; use the former.
      
      In addition, create accessors for the BR/OR regs that use in/out_be32
      and use those instead of the mismash of access methods currently in play.
      
      I have done a successful ppc build all and tested a board or two from
      each processor family.
      Signed-off-by: default avatarBecky Bruce <beckyb@kernel.crashing.org>
      Acked-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      f51cdaf1
  17. 31 Oct, 2009 1 commit
    • Wolfgang Grandegger's avatar
      video: mb862xx: improve board-specific Lime configuration · c28d3bbe
      Wolfgang Grandegger authored
      To avoid board-specific code accessing the mb862xx registers directly,
      the public function mb862xx_probe() has been introduced. Furthermore,
      the "Change of Clock Frequency" and "Set Memory I/F Mode" registers
      are now defined by CONFIG_SYS_MB862xx_CCF and CONFIG_SYS_MB862xx__MMR,
      respectively. The BSPs for the socrates and lwmon5 boards have been
      adapted accordingly.
      Signed-off-by: default avatarWolfgang Grandegger <wg@denx.de>
      c28d3bbe
  18. 03 Oct, 2009 1 commit
  19. 24 Sep, 2009 1 commit
  20. 28 Aug, 2009 1 commit
  21. 03 Jun, 2009 1 commit
    • Wolfgang Denk's avatar
      Redundant Environment: protect full sector size · dfcd7f21
      Wolfgang Denk authored
      Several boards used different ways to specify the size of the
      protected area when enabling flash write protection for the sectors
      holding the environment variables: some used CONFIG_ENV_SIZE and
      CONFIG_ENV_SIZE_REDUND, some used CONFIG_ENV_SECT_SIZE, and some even
      a mix of both for the "normal" and the "redundant" areas.
      
      Normally, this makes no difference at all. However, things are
      different when you have to deal with boards that can come with
      different types of flash chips, which may have different sector
      sizes.
      
      Here we may have to chose CONFIG_ENV_SECT_SIZE such that it fits the
      biggest sector size, which may include several sectors on boards using
      the smaller sector flash types. In such a case, using CONFIG_ENV_SIZE
      or CONFIG_ENV_SIZE_REDUND to enable the protection may lead to the
      case that only the first of these sectors get protected, while the
      following ones aren't.
      
      This is no real problem, but it can be confusing for the user -
      especially on boards that use CONFIG_ENV_SECT_SIZE to protect the
      "normal" areas, while using CONFIG_ENV_SIZE_REDUND for the
      "redundant" area.
      
      To avoid such inconsistencies, I changed all sucn boards that I found
      to consistently use CONFIG_ENV_SECT_SIZE for protection. This should
      not cause any functional changes to the code.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Cc: Paul Ruhland
      Cc: Pantelis Antoniou <panto@intracom.gr>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Gary Jennejohn <garyj@denx.de>
      Cc: Dave Ellis <DGE@sixnetio.com>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      dfcd7f21
  22. 20 Mar, 2009 1 commit
    • Trent Piepho's avatar
      Fix all linker script to handle all rodata sections · f62fb999
      Trent Piepho authored
      A recent gcc added a new unaligned rodata section called '.rodata.str1.1',
      which needs to be added the the linker script.  Instead of just adding this
      one section, we use a wildcard ".rodata*" to get all rodata linker section
      gcc has now and might add in the future.
      
      However, '*(.rodata*)' by itself will result in sub-optimal section
      ordering.  The sections will be sorted by object file, which causes extra
      padding between the unaligned rodata.str.1.1 of one object file and the
      aligned rodata of the next object file.  This is easy to fix by using the
      SORT_BY_ALIGNMENT command.
      
      This patch has not be tested one most of the boards modified.  Some boards
      have a linker script that looks something like this:
      
      *(.text)
      . = ALIGN(16);
      *(.rodata)
      *(.rodata.str1.4)
      *(.eh_frame)
      
      I change this to:
      
      *(.text)
      . = ALIGN(16);
      *(.eh_frame)
      *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))
      
      This means the start of rodata will no longer be 16 bytes aligned.
      However, the boundary between text and rodata/eh_frame is still aligned to
      16 bytes, which is what I think the real purpose of the ALIGN call is.
      Signed-off-by: default avatarTrent Piepho <xyzzy@speakeasy.org>
      f62fb999
  23. 20 Dec, 2008 1 commit
  24. 04 Dec, 2008 1 commit
    • Anatolij Gustschin's avatar
      85xx: socrates: fix DDR SDRAM tlb entry configuration · dd332e18
      Anatolij Gustschin authored
      since commit be0bd823
      tlb entry for socrates DDR SDRAM will be reconfigured
      by setup_ddr_tlbs() from initdram() causing an
      inconsistency with previously configured DDR SDRAM tlb
      entry from tlb_table:
      
      socrates>l2cam 7 9
      IDX  PID      EPN  SIZE V TS           RPN U0-U3 WIMGE UUUSSS
        7 : 00 00000000 256MB V  0 -> 0_00000000  0000 -I-G- ---RWX
        8 : 00 00000000 256MB V  0 -> 0_00000000  0000 ----- ---RWX
        9 : 00 10000000 256MB V  0 -> 0_10000000  0000 ----- ---RWX
      
      This patch makes the presence of the DDR SDRAM tlb entry in
      the tlb_table dependent on CONFIG_SPD_EEPROM to avoid this
      inconsistency.
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      Acked-by: default avatarAndy Fleming <afleming@freescale.com>
      dd332e18
  25. 18 Nov, 2008 1 commit
  26. 18 Oct, 2008 2 commits
  27. 22 Sep, 2008 1 commit
  28. 13 Sep, 2008 1 commit
  29. 10 Sep, 2008 1 commit
  30. 09 Sep, 2008 4 commits
  31. 27 Aug, 2008 1 commit