1. 19 2月, 2014 2 次提交
  2. 04 2月, 2014 2 次提交
  3. 22 1月, 2014 1 次提交
  4. 13 1月, 2014 1 次提交
  5. 03 1月, 2014 2 次提交
    • P
      powerpc/mpc85xx: Add support for single source clocking · b135991a
      Priyanka Jain 提交于
      Single-source clocking is new feature introduced in T1040.
      In this mode, a single differential clock is supplied to the
      DIFF_SYSCLK_P/N inputs to the processor, which in turn is
      used to supply clocks to the sysclock, ddrclock and usbclock.
      
      So, both ddrclock and syclock are driven by same differential
      sysclock in single-source clocking mode whereas in normal clocking
      mode, generally separate DDRCLK and SYSCLK pins provides
      reference clock for sysclock and ddrclock
      
      DDR_REFCLK_SEL rcw bit is used to determine DDR clock source
      -If DDR_REFCLK_SEL rcw bit is 0, then DDR PLLs are driven in
       normal clocking mode by DDR_Reference clock
      
      -If DDR_REFCLK_SEL rcw bit is 1, then DDR PLLs are driven in
       single source clocking mode by DIFF_SYSCLK
      
      Add code to determine ddrclock based on DDR_REFCLK_SEL rcw bit.
      Signed-off-by: NPoonam Aggrwal <poonam.aggrwal@freescale.com>
      Signed-off-by: NPriyanka Jain <Priyanka.Jain@freescale.com>
      b135991a
    • P
      board/freescale:Remove use of CONFIG_SPL_NAND_MINIMAL · fbe76ae4
      Prabhakar Kushwaha 提交于
      CONFIG_SPL_NAND_MINIMAL should not be used as it was defined for temporary
      review purpose.
      
      So, use CONFIG_SPL_NAND_BOOT config.
      Signed-off-by: NPrabhakar Kushwaha <prabhakar@freescale.com>
      fbe76ae4
  6. 13 12月, 2013 1 次提交
    • G
      Add dumpimage, a tool to extract data from U-Boot images · a804b5ce
      Guilherme Maciel Ferreira 提交于
      Given a multi-file image created through the mkimage's -d option:
      
        $ mkimage -A x86 -O linux -T multi -n x86 -d vmlinuz:initrd.img:System.map \
        multi.img
      
        Image Name:   x86
        Created:      Thu Jul 25 10:29:13 2013
        Image Type:   Intel x86 Linux Multi-File Image (gzip compressed)
        Data Size:    13722956 Bytes = 13401.32 kB = 13.09 MB
        Load Address: 00000000
        Entry Point:  00000000
        Contents:
           Image 0: 4040128 Bytes = 3945.44 kB = 3.85 MB
           Image 1: 7991719 Bytes = 7804.41 kB = 7.62 MB
           Image 2: 1691092 Bytes = 1651.46 kB = 1.61 MB
      
      It is possible to perform the innverse operation -- extracting any file from
      the image -- by using the dumpimage's -i option:
      
        $ dumpimage -i multi.img -p 2 System.map
      
      Although it's feasible to retrieve "data files" from image through scripting,
      the requirement to embed tools such 'dd', 'awk' and 'sed' for this sole purpose
      is cumbersome and unreliable -- once you must keep track of file sizes inside
      the image. Furthermore, extracting data files using "dumpimage" tool is faster
      than through scripting.
      Signed-off-by: NGuilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      a804b5ce
  7. 06 12月, 2013 1 次提交
  8. 26 11月, 2013 2 次提交
  9. 25 11月, 2013 2 次提交
  10. 13 11月, 2013 3 次提交
  11. 12 11月, 2013 2 次提交
    • H
      arm, am33x: make RTC32K OSC enable configurable · 16678eb4
      Heiko Schocher 提交于
      As
      http://www.denx.de/wiki/view/U-Boot/DesignPrinciples#2_Keep_it_Fast
      states:
      "Initialize devices only when they are needed within U-Boot"
      
      enable the RTC32K OSC only, if CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC is
      enabled. Enable this in ti_am335x_common.h, so all boards in mainline
      should work as before.
      Signed-off-by: NHeiko Schocher <hs@denx.de>
      Cc: Tom Rini <trini@ti.com>
      16678eb4
    • H
      bootcount: store bootcount var in environment · eda0ba38
      Heiko Schocher 提交于
      If no softreset save registers are found on the hardware
      "bootcount" is stored in the environment. To prevent a
      saveenv on all reboots, the environment variable
      "upgrade_available" is introduced. If "upgrade_available" is
      0, "bootcount" is always 0 therefore no need to save the
      environment on u-boot boot, if "upgrade_available" is 1 "bootcount"
      is incremented in the environment and environment gets written
      on u-boot start.
      So the Userspace Applikation must set the "upgrade_available"
      and "bootcount" variable to 0 (for example with fw_setenv),
      if a boot was successfully.
      Signed-off-by: NHeiko Schocher <hs@denx.de>
      eda0ba38
  12. 09 11月, 2013 1 次提交
  13. 08 11月, 2013 2 次提交
    • I
      README: remove wrong config name · 39d9abfa
      Igor Grinberg 提交于
      There is no CONFIG_PCA953X_INFO symbol.
      U-Boot uses CONFIG_CMD_PCA953X_INFO instead, which is described in
      "Monitor Functions" section and thus no need to be repeated in the
      "GPIO Support" section.
      Remove the whole line.
      Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
      39d9abfa
    • A
      cmd_nvedit.c: Add env exists command · 88733e2c
      Andrew Ruder 提交于
      env exists is a way to test (in hush) if an environment variable
      exists.  A workaround existed using printenv but this new command
      doesn't require all the stdout/stderr redirection to prevent
      printing information to the screen.
      
      Example:
      $ set testexists 1
      $ env exists testexists && echo "yes"
      yes
      $ env exists testexists || echo "no"
      $ set testexists
      $ env exists testexists && echo "yes"
      $ env exists testexists || echo "no"
      no
      $
      Signed-off-by: NAndrew Ruder <andrew.ruder@elecsyscorp.com>
      88733e2c
  14. 30 10月, 2013 1 次提交
  15. 17 10月, 2013 3 次提交
  16. 15 10月, 2013 1 次提交
  17. 08 10月, 2013 1 次提交
  18. 24 9月, 2013 2 次提交
    • A
      dfu: ram support · a9479f04
      Afzal Mohammed 提交于
      DFU spec mentions it as a method to upgrade firmware (software stored
      in writable non-volatile memory). It also says other potential uses of
      DFU is beyond scope of the spec.
      
      Here such a beyond the scope use is being attempted - directly pumping
      binary images from host via USB to RAM. This facility is a developer
      centric one in that it gives advantage over upgrading non-volatile
      memory for testing new images every time during development and/or
      testing.
      
      Directly putting image onto RAM would speed up upgrade process. This and
      convenience was the initial thoughts that led to doing this, speed
      improvement over MMC was only 1 second though - 6 sec on RAM as opposed
      to 7 sec on MMC in beagle bone, perhaps enabling cache and/or optimizing
      DFU framework to avoid multiple copy for ram (if worth) may help, and
      on other platforms and other boot media like NAND maybe improvement
      would be higher.
      
      And for a platform that doesn't yet have proper DFU suppport for
      non-volatile media's, DFU to RAM can be used.
      
      Another minor advantage would be to increase life of mmc/nand as it
      would be less used during development/testing.
      
      usage: <image name> ram <start address> <size>
      eg. kernel ram 0x81000000 0x1000000
      
      Downloading images to RAM using DFU is not something new, this is
      acheived in openmoko also.
      
      DFU on RAM can be used for extracting RAM contents to host using dfu
      upload. Perhaps this can be extended to io for squeezing out register
      dump through usb, if it is worth.
      Signed-off-by: NAfzal Mohammed <afzal.mohd.ma@gmail.com>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Lukasz Majewski <l.majewski@samsung.com>
      Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
      Cc: Gerhard Sittig <gsi@denx.de>
      Acked-by: NMarek Vasut <marex@denx.de>
      Acked-by: NLukasz Majewski <l.majewski@samsung.com>
      Acked-by: NHeiko Schocher <hs@denx.de>
      a9479f04
    • J
      README: update ARM register usage · 12eba1b4
      Jeroen Hofstee 提交于
      Besides the change of this patchset it also updates the
      README to reflect that GOT-generated relocations are no
      longer supported on ARM.
      
      cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
      Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
      12eba1b4
  19. 20 9月, 2013 2 次提交
  20. 19 9月, 2013 1 次提交
  21. 12 9月, 2013 1 次提交
  22. 04 9月, 2013 1 次提交
  23. 21 8月, 2013 3 次提交
  24. 17 8月, 2013 1 次提交
    • S
      RFC: bootm: Add silent_linux environment variable · 8d51aacd
      Simon Glass 提交于
      At present the console for linux is silent if the U-Boot console is silent,
      unless CONFIG_SILENT_U_BOOT_ONLY is set. I wonder if a better way would be
      to have an environment variable to control this? Then we can control the
      verbosity from scripts, and set the variable to 'no' for those boards that
      want Linux to boot with console output.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      8d51aacd
  25. 10 8月, 2013 1 次提交