20 Jun, 2015

2 commits

  • This introduces the part start and part size sub-commands. The purpose of these
    is to store the start block and size of a partition in a variable, given the
    device and partition number.

    This allows reading raw data that fits a single partition more easily.
    For instance, this could be used to figure out the start block and size of a
    kernel partition when a partition table is present, given the partition number.

    Signed-off-by: Paul Kocialkowski
    Acked-by: Stephen Warren
    [trini: Change "%lx" to LBAF]
    Signed-off-by: Tom Rini

    Paul Kocialkowski
     
  • This fixes a misaligned declaration.

    Signed-off-by: Paul Kocialkowski

    Paul Kocialkowski
     

19 Jun, 2015

2 commits

  • This allows using only one of either raw or fs mode for SPL mmc boot, without
    the need to have provisions for the other. In particular, a device may have
    U-Boot installed on a file system on the mmc, without ever needing to read
    U-Boot from raw memory. Thus, there is no reason to provide a sector or
    partition for raw mode. This allows this behaviour and still provides a robust
    fallback mechanism in case provisions for both modes are defined.

    Signed-off-by: Paul Kocialkowski

    Paul Kocialkowski
     
  • This switches some printf calls to puts and avoids a test repetition.

    Signed-off-by: Paul Kocialkowski

    Paul Kocialkowski
     

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

9 commits


26 May, 2015

2 commits


21 May, 2015

5 commits


20 May, 2015

1 commit

  • On my A10 OlinuxIno Lime I noticed a huge (5+ seconds) delay coming from
    console_init_r. This turns out to be caused by the preconsole buffer flushing
    to the cfb_console. The Lime only has a 16 bit memory bus and that is already
    heavy used to scan out the 1920x1080 framebuffer.

    The problem is that print_pre_console_buffer() was printing the buffer once
    character at a time and the cfb_console code then ends up doing a cache-flush
    for touched display lines for each character.

    This commit fixes this by first building a 0 terminated buffer and then
    printing it in one puts() call, avoiding unnecessary cache flushes.

    This changes the time for the flush from 5+ seconds to not noticable.

    The downside of this approach is that the pre-console buffer needs to fit
    on the stack, this is not that much to ask since we are talking about plain
    text here. This commit also adjusts the sunxi CONFIG_PRE_CON_BUF_SZ to
    actually fit on the stack. Sunxi currently is the only user of the pre-console
    code so no other boards need to be adjusted.

    Signed-off-by: Hans de Goede
    Reviewed-by: Tom Rini

    Hans de Goede