23 Nov, 2014

5 commits

  • When enumerating devices, honour the pci_skip_dev() function. This can
    be used by PCI controller drivers to restrict which devices will be
    probed.

    This is required by the NVIDIA Tegra PCIe controller driver, which will
    fail with a data abort exception if an access is attempted to a device
    number larger than 0 outside of bus 0. pci_skip_dev() is therefore
    implemented to prevent any such accesses.

    Signed-off-by: Thierry Reding
    Signed-off-by: Simon Glass

    Thierry Reding
     
  • When listing the devices on a PCI bus, the current code will blindly try
    to access all devices. Internally this causes pci_bus_to_hose() to be
    repeatedly called and output an error message every time. Prevent this
    by calling pci_bus_to_hose() once and abort early if no bus was found.

    Signed-off-by: Thierry Reding
    Signed-off-by: Simon Glass

    Thierry Reding
     
  • Some filesystems have a UUID stored in its superblock. To
    allow using root=UUID=... for the kernel command line we
    need a way to read-out the filesystem UUID.

    changes rfc -> v1:
    - make the environment variable an option parameter. If not
    given, the UUID is printed out. If given, it is stored in the env
    variable.
    - corrected typos
    - return error codes

    changes v1 -> v2:
    - fix return code of do_fs_uuid(..)
    - document do_fs_uuid(..)
    - implement fs_uuid_unsuported(..) be more consistent with the
    way other optional functionality works

    changes v2 -> v3:
    - change ext4fs_uuid(..) to make use of #if .. #else .. #endif
    construct to get rid of unreachable code

    Hit any key to stop autoboot: 0
    => fsuuid
    fsuuid - Look up a filesystem UUID

    Usage:
    fsuuid :
    - print filesystem UUID
    fsuuid :
    - set environment variable to filesystem UUID

    => fsuuid mmc 0:1
    d9f9fc05-45ae-4a36-a616-fccce0e4f887
    => fsuuid mmc 0:2
    eb3db83c-7b28-499f-95ce-9e0bb21cda81
    => fsuuid mmc 0:1 uuid1
    => fsuuid mmc 0:2 uuid2
    => printenv uuid1
    uuid1=d9f9fc05-45ae-4a36-a616-fccce0e4f887
    => printenv uuid2
    uuid2=eb3db83c-7b28-499f-95ce-9e0bb21cda81
    =>

    Signed-off-by: Christian Gmeiner
    Acked-by: Stephen Warren

    Christian Gmeiner
     
  • We had the problem on an AM33xx platform, that SPL detected an
    unsupported boot-device. But since this message is a debug message
    it took a bit of time to really know, where the hangup in SPL
    resulted from. So let's change this debug message to a printf
    and also print the detected boot-device that is not supported.
    This makes debugging of such cases much easier.

    Signed-off-by: Stefan Roese
    Cc: Wolfgang Denk
    Cc: Tom Rini
    Acked-by: Heiko Schocher

    Stefan Roese
     
  • U-Boot has never cared about the type when we get max/min of two
    values, but Linux Kernel does. This commit gets min, max, min3, max3
    macros synced with the kernel introducing type checks.

    Many of references of those macros must be fixed to suppress warnings.
    We have two options:
    - Use min, max, min3, max3 only when the arguments have the same type
    (or add casts to the arguments)
    - Use min_t/max_t instead with the appropriate type for the first
    argument

    Signed-off-by: Masahiro Yamada
    Acked-by: Pavel Machek
    Acked-by: Lukasz Majewski
    Tested-by: Lukasz Majewski
    [trini: Fixup arch/blackfin/lib/string.c]
    Signed-off-by: Tom Rini

    Masahiro Yamada
     

19 Nov, 2014

1 commit


17 Nov, 2014

1 commit


13 Nov, 2014

2 commits


12 Nov, 2014

2 commits


08 Nov, 2014

7 commits

  • Skip enclosure service devices when probing for usb storage devices.

    This avoids long timeouts when probing for external usb harddisks
    which provide "Enclosure Services".

    Signed-off-by: Soeren Moch
    --

    This is a new version of the patch
    "usb_storage: skip all unknown devices when probing"
    http://http://lists.denx.de/pipermail/u-boot/2014-November/194622.html

    Cc: Marek Vasut
    Cc: Tom Rini

    Soeren Moch
     
  • This file got corrupted by the automatic editin of commit 1a45966 "Add
    GPL-2.0+ SPDX-License-Identifier to source files"; restore the
    opiginal content and manually insert the SPDX ID.

    The bug was detected by running cppcheck, which reported:
    [common/cmd_fitupd.c:8]: (error) Invalid number of character ({) when
    these macros are defined: 'CONFIG_UPDATE_TFTP'.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • run_command() returns success even if the command had a syntax error;
    correct this behaviour.

    Signed-off-by: Rabin Vincent
    Acked-by: Simon Glass <sjg@chromium.org)

    Rabin Vincent
     
  • Hush segfaults if it sees a syntax error while attempting to parse a
    command:

    $ ./u-boot -c "'"
    ...
    syntax error
    Segmentation fault (core dumped)

    This is due to a NULL pointer dereference of in_str->p in static_peek().
    The problem is that the exit condition for the loop in
    parse_stream_outer() checks for rcode not being -1, but rcode is only
    ever 0 or 1.

    Signed-off-by: Rabin Vincent
    Acked-by: Simon Glass <sjg@chromium.org)

    Rabin Vincent
     
  • Attempting to run:
    - an empty string
    - a string with just spaces

    returns different error codes, 1 for the empty string and 0
    for the string with just spaces. Make both of them return
    0 for consistency.

    Signed-off-by: Rabin Vincent
    Acked-by: Simon Glass <sjg@chromium.org)

    Rabin Vincent
     
  • Attempting to run the sandbox leads to a segfault, because some dynamic
    libraries (outside of u-boot) attempt to use malloc() to allocate memory
    before u-boot's gd variable is initialized.

    Check for gd not being NULL in the SYS_MALLOC_F_LEN handling, so that
    malloc() doesn't crash when called at this point.

    $ gdb -q --args ./u-boot
    (gdb) r
    Program received signal SIGSEGV, Segmentation fault.
    0x0000000000412b9b in malloc (bytes=bytes@entry=37) at common/dlmalloc.c:2184
    2184 if (!(gd->flags & GD_FLG_RELOC)) {
    (gdb) p gd
    $1 = (gd_t *) 0x0
    (gdb) bt
    #0 0x0000000000412b9b in malloc (bytes=bytes@entry=37) at common/dlmalloc.c:2184
    #1 0x00007ffff75bf8e1 in set_binding_values (domainname=0x7ffff11f4f12 "libgpg-error", dirnamep=0x7fffffffe168, codesetp=0x0)
    at bindtextdom.c:228
    #2 0x00007ffff75bfb4c in set_binding_values (codesetp=0x0, dirnamep=0x7fffffffe168, domainname=) at bindtextdom.c:350
    #3 __bindtextdomain (domainname=, dirname=0x7ffff11f4f00 "/usr/share/locale") at bindtextdom.c:348
    #4 0x00007ffff11eca17 in ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0
    #5 0x00007ffff7dea9fa in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffffffe208,
    env=env@entry=0x7fffffffe218) at dl-init.c:78
    #6 0x00007ffff7deaae3 in call_init (env=0x7fffffffe218, argv=0x7fffffffe208, argc=1, l=) at dl-init.c:36
    #7 _dl_init (main_map=0x7ffff7ffe1a8, argc=1, argv=0x7fffffffe208, env=0x7fffffffe218) at dl-init.c:126
    #8 0x00007ffff7ddd1ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2

    Signed-off-by: Rabin Vincent
    Acked-by: Simon Glass

    Rabin Vincent
     
  • I believe that when no DTB is around we should return 1.
    This why I fixed such scenarious to not return zero anymore.
    Else kernel might get NULL pointer to DTB which doesn't exists.

    Signed-off-by: Noam Camus

    Noam Camus
     

04 Nov, 2014

7 commits


30 Oct, 2014

1 commit


29 Oct, 2014

2 commits

  • This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     
  • This is a bit odd in that we are permitted to boot images for either, even
    though they are separate architectures.

    Signed-off-by: Simon Glass

    Simon Glass
     

28 Oct, 2014

8 commits


27 Oct, 2014

4 commits