23 Jul, 2015

2 commits


11 Jul, 2015

1 commit

  • Commit 2b42c9317db ("ahci: support LBA48 data reads for 2+TB drives")
    introduced conditional code which triggers a warning when compiled
    with DEBUG enabled:

    In file included from common/cmd_scsi.c:12:0:
    common/cmd_scsi.c: In function 'scsi_read':
    include/common.h:109:4: warning: 'smallblks' may be used uninitialized in this function [-Wmaybe-uninitialized]
    ...

    Since this is for debug only, take the easy way and initialize the
    variable explicitly on declaration to avoid the warning.
    (Fix a nearby whitespace error on the way.)

    Tested-by: Bin Meng
    Signed-off-by: Andre Przywara

    Andre Przywara
     

01 Jul, 2015

1 commit


30 Jun, 2015

4 commits

  • If flash pointer is used free it, before probing a new
    flash and storing it in flash.

    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • With this patch, it is possible to get the offset and size information
    from the mtdpartiton setting in "mtdparts", similiar to the
    "nand" commandos.

    => sf
    sf - SPI flash sub-system

    Usage:
    sf probe [[bus:]cs] [hz] [mode] - init flash device on given SPI bus
    and chip select
    sf read addr offset|partition len - read `len' bytes starting at
    `offset' to memory at `addr'
    sf write addr offset|partition len - write `len' bytes from memory
    at `addr' to flash at `offset'
    sf erase offset|partition [+]len - erase `len' bytes from `offset'
    `+len' round up `len' to block size
    sf update addr offset|partition len - erase and write `len' bytes from memory
    at `addr' to flash at `offset'
    =>
    for example "env" is defined in mtdparts:

    => sf read 13000000 env
    device 0 offset 0xd0000, size 0x10000
    SF: 65536 bytes @ 0xd0000 Read: OK

    zynq-uboot> mtdparts add nor0 0x10000@0x0 env
    zynq-uboot> sf erase env 0x10000
    SF: 65536 bytes @ 0x0 Erased: OK

    zynq-uboot> sf write 0x100 env
    device 0 offset 0x0, size 0x10000
    SF: 65536 bytes @ 0x0 Written: OK

    zynq-uboot> sf read 0x40000 env
    device 0 offset 0x0, size 0x10000
    SF: 65536 bytes @ 0x0 Read: OK

    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • Move common functions from cmd_nand.c (for calculating offset
    and size from cmdline paramter) to common place, so they could
    used from other commands which use mtd partitions.

    For onenand the arg_off_size() is left in common/cmd_onenand.c.
    It should use now the common arg_off() function, but as I could
    not test onenand I let it there ...

    Signed-off-by: Heiko Schocher
    Acked-by: Scott Wood
    Reviewed-by: Jagannadh Teki

    Heiko Schocher
     
  • Add MTD layer driver for spi, original patch from:
    http://git.denx.de/?p=u-boot/u-boot-mips.git;a=commitdiff;h=bb246819cdc90493dd7089eaa51b9e639765cced

    Changes from Heiko Schocher against this patch:
    - Remove compile error if not defining CONFIG_SPI_FLASH_MTD:

    LD drivers/mtd/spi/built-in.o
    drivers/mtd/spi/sf_probe.o: In function `spi_flash_mtd_unregister':
    /home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: multiple definition of `spi_flash_mtd_unregister'
    drivers/mtd/spi/sf_params.o:/home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: first defined here
    drivers/mtd/spi/sf_ops.o: In function `spi_flash_mtd_unregister':
    /home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: multiple definition of `spi_flash_mtd_unregister'
    drivers/mtd/spi/sf_params.o:/home/hs/abb/imx6/u-boot/drivers/mtd/spi/sf_internal.h:168: first defined here
    make[1]: *** [drivers/mtd/spi/built-in.o] Fehler 1
    make: *** [drivers/mtd/spi] Fehler 2

    - Add a README entry.
    - Add correct writebufsize, to fit with Linux v3.14
    MTD, UBI/UBIFS sync.

    Note (From Jagan): For testing raw mtd parition erase/read/write operations
    using cmd_sf, sf_mtd should be required to register the spi flash device to
    MTD layer but the sf_mtd_info ops were not required until and unless if we
    use any flash filesystem layer say for example UBI. Due to this the foot-print
    got increased ~290bytes in non-UBI case here that should be acceptible.

    Signed-off-by: Daniel Schwierzeck
    Signed-off-by: Heiko Schocher
    Tested-by: Jagannadh Teki
    Reviewed-by: Jagannadh Teki

    Daniel Schwierzeck
     

26 Jun, 2015

3 commits


20 Jun, 2015

3 commits


19 Jun, 2015

3 commits


13 Jun, 2015

2 commits


12 Jun, 2015

1 commit


11 Jun, 2015

4 commits


09 Jun, 2015

2 commits

  • This patch adds the feature to only stop the autobooting, and therefor
    boot into the U-Boot prompt, when the input string / password matches
    a values that is encypted via a SHA256 hash and saved in the environment.

    This feature is enabled by defined these config options:
    CONFIG_AUTOBOOT_KEYED
    CONFIG_AUTOBOOT_STOP_STR_SHA256

    Signed-off-by: Stefan Roese
    Reviewed-by: Simon Glass

    Stefan Roese
     
  • This patch moves the following config options to Kconfig:

    CONFIG_AUTOBOOT_KEYED
    CONFIG_AUTOBOOT_PROMPT
    CONFIG_AUTOBOOT_DELAY_STR
    CONFIG_AUTOBOOT_STOP_STR
    AUTOBOOT_KEYED_CTRLC

    Signed-off-by: Stefan Roese
    Reviewed-by: Simon Glass
    [trini: Drop ip04 and pm9263 configs/ additions, those boards previously
    set CONFIG_AUTOBOOT_PROMPT but never used it, re-run savedefconfig over
    all boards that did change. Make digsy_mtc_* string include seconds to
    match others and not warn. ]
    Signed-off-by: Tom Rini
    Cc: Masahiro Yamada

    Stefan Roese
     

08 Jun, 2015

1 commit

  • These defines for a 2nd autoboot stop and delay string are nearly unused. Only
    sc3 defines CONFIG_AUTOBOOT_DELAY_STR2. And a patch to remove this most likely
    unmaintained board is also posted to the list.

    By removing these defines the code will become cleaner and moving the remaining
    compile options to Kconfig will get easier.

    Signed-off-by: Stefan Roese
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass
    Cc: Wolfgang Denk
    Cc: Heiko Schocher

    Stefan Roese
     

06 Jun, 2015

2 commits


05 Jun, 2015

1 commit

  • Before device-tree, the device serial number used to be passed to the kernel
    using ATAGs (on ARM). This is now deprecated and all the handover to the kernel
    should now be done using device-tree. Thus, this passes the serial-number
    property to the kernel using the serial-number property of the root node, as
    expected by the kernel.

    The serial number is a string that somewhat represents the device's serial
    number. It might come from some form of storage (e.g. an eeprom) and be
    programmed at factory-time by the manufacturer or come from identification
    bits available in e.g. the SoC.

    Signed-off-by: Paul Kocialkowski
    Reviewed-by: Simon Glass

    Paul Kocialkowski
     

04 Jun, 2015

1 commit


02 Jun, 2015

1 commit


01 Jun, 2015

2 commits


29 May, 2015

2 commits

  • The usb-kbd key repeat code assumes that reports get repeated every 40 ms,
    this is never true when using CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP, and
    does not always works for CONFIG_SYS_USB_EVENT_POLL and
    CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE since not all usb keyboards honor
    the usb_set_idle() command.

    For CONFIG_SYS_USB_EVENT_POLL we must use usb_set_idle() since we do a
    blocking wait for the hid report, so if we do not tell the keyboard to send
    a hid report every 40ms even if nothing changes then we will block u-boot
    for 1s (the default u-boot usb interrupt packet timeout). Note that in this
    case on keyboards which do not support usb_set_idle() we loose and we actually
    get 1s latencies on other u-boot activities.

    For the other poll-methods this commit stops using usb_set_idle() and instead
    repeats the last received hid-report every 40 ms as long as no new hid-report
    is received. This fixes key-repeat not working at all with
    CONFIG_SYS_USB_EVENT_POLL_VIA_CONTROL_EP and fixes it not working with
    keyboards which do not implement usb_set_idle() when using
    CONFIG_SYS_USB_EVENT_POLL_VIA_INT_QUEUE.

    Signed-off-by: Hans de Goede

    Hans de Goede
     
  • The compiler did not catch this as it was marked __maybe_unused.

    Signed-off-by: Hans de Goede

    Hans de Goede
     

28 May, 2015

4 commits