Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • stable
  • extraversion
  • early-display
  • variant-emmc-nvme-boot
  • 2024-07-19
  • 2024-06-30
  • 2023-10-18
  • 2023-10-10
  • 2023-07-04
  • 2023-01-25
  • v3
  • variant-emmc-nvme-boot
  • 2020-06-01
14 results
Search by author
  • Any Author
  • bnys bnys brendannystedt
  • buckket buckket buckket
  • Chris Hofstaedtler Chris Hofstaedtler zeha
  • Johannes Schauer Marin Rodrigues Johannes Schauer Marin Rodrigues josch
  • J W J W JulianWgs
  • minute minute mntmn
  • Nano Nano NanoCodeBug
  • neauoire neauoire hundredrabbits
  • plom plom heller
9 authors
  1. Jan 14, 2017
    • Tom Rini's avatar
      arm: Remove unregister MACH_TYPE_xxx uses · 70b26cd0
      Tom Rini authored 
      
Before we can sync with the latest mach-types.h file from the Linux
Kernel we need to remove some instances of MACH_TYPE_xxx from our
sources.  As these values have been removed from the canonical upstream
source we should not be using them either, so drop.

Cc: Tom Warren <twarren@nvidia.com>
Cc: Lucas Stach <dev@lynxeye.de>
Cc: Luka Perkov <luka@openwrt.org>
Cc: Stephen Warren <swarren@wwwdotorg.org>
Cc: Heiko Schocher <hs@denx.de>
Cc: Thomas Weber <weber@corscience.de>
Cc: Lucile Quirion <lucile.quirion@savoirfairelinux.com>
Cc: Matthias Weisser <weisserm@arcor.de>
Cc: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: Bo Shen <voice.shen@atmel.com>
Cc: Nick Thompson <nick.thompson@gefanuc.com>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Erik van Luijk <evanluijk@interact.nl>
Cc: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      70b26cd0
    • Tom Rini's avatar
      omap3_igep00x0: Rework MACH_TYPE and status LED logic slightly · d5324e2f
      Tom Rini authored 
      
The MACH_TYPE for IGEP0032 was never officially used and has been
removed from upstream, so we must not use it.  In order to remove this
we need to rework the status LED logic.

Cc: Enric Balletbo i Serra <eballetbo@gmail.com>
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
Acked-by: default avatarEnric Balletbo i Serra <eballetbo@gmail.com>
      d5324e2f
    • Tom Rini's avatar
      omap3_logic: Rework MACH_TYPE and fdtfile logic · c63d270d
      Tom Rini authored 
      
The MACH_TYPE values for the omap37xx based platforms are no longer
officially valid, so we must not set and pass them.  In order to not
reference them but still be able to set the default fdtfile based on the
board detection logic we need to combine the two steps into one.

Cc: Adam Ford <aford173@gmail.com>
Signed-off-by: default avatarTom Rini <trini@konsulko.com>
Acked-by: default avatarAdam Ford <aford173@gmail.com>
      c63d270d
    • Tom Rini's avatar
      Merge git://git.denx.de/u-boot-fdt · b7127e3c
      Tom Rini authored
      b7127e3c
    • Andreas Färber's avatar
      cmd/fdt: Make fdt get value endian-safe for single-cell properties · b05bf6c7
      Andreas Färber authored 
      
On a Raspberry Pi 2 disagreements on cell endianness can be observed:

  U-Boot> fdt print /soc/gpio@7e200000 phandle
  phandle = <0x0000000d>
  U-Boot> fdt get value myvar /soc/gpio@7e200000 phandle; printenv myvar
  myvar=0x0D000000

Fix this by always treating the pointer as BE and converting it in
fdt_value_setenv(), like its counterpart fdt_parse_prop() already does.

Consistently use fdt32_t, fdt32_to_cpu() and cpu_to_fdt32().

Fixes: bc80295b ("fdt: Add get commands to fdt")
Cc: Joe Hershberger <joe.hershberger@ni.com>
Cc: Gerald Van Baren <gvb@unssw.com>
Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
Acked-by: default avatarSimon Glass <sjg@chromium.org>
      b05bf6c7
    • Stefan Agner's avatar
      cmd: fdt: Print error message when fdt application fails · 082b1414
      Stefan Agner authored 
      
There are lots of reason why a FDT application might fail, the
error code might give an indication. Let the error code translate
in a error string so users can try to understand what went wrong.

Signed-off-by: default avatarStefan Agner <stefan.agner@toradex.com>
Acked-by: default avatarMaxime Ripard <maxime.ripard@free-electrons.com>
Acked-by: default avatarSimon Glass <sjg@chromium.org>
      082b1414
    • David Gibson's avatar
      libfdt: Correct fdt handling of overlays without fixups and base trees without symbols · 46743c41
      David Gibson authored 
      
The fdt_overlay_apply() function purports to support the edge cases where
an overlay has no fixups to be applied, or a base tree which has no
symbols (the latter can only work if the former is also true).  However it
gets it wrong in a couple of small ways:

  * In the no fixups case, it doesn't fail immediately, but will attempt
    fdt_for_each_property_offset() giving -FDT_ERR_NOTFOUND as the node
    offset, which will fail.  Instead it should succeed immediately, since
    there's nothing to do.
  * In the case of no symbols, it again doesn't fail immediately.  However
    if there is an actual fixup it will fail with an unexpected error,
    because -FDT_ERR_NOTFOUND is passed to fdt_getprop() when attempting to
    look up the symbols.  We should instead return -FDT_ERR_NOTFOUND
    directly.

Both of these errors lead to the code returning misleading error codes in
failing cases.

[ DTC commit: 7d8ef6e1db9794f72805a0855f4f7f12fadd03d3 ]

Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
Signed-off-by: default avatarStefan Agner <stefan.agner@toradex.com>
Acked-by: default avatarSimon Glass <sjg@chromium.org>
      46743c41
  3. Jan 13, 2017
  5. Jan 12, 2017
  7. Jan 11, 2017