Eric Lee / smarc-uboot

16 May, 2017

1 commit

14 Mar, 2017

1 commit

28 Jan, 2017

1 commit

30 Dec, 2016

1 commit

  • c27269953   mmc: complete unfinished move of CONFIG_MMC ... Browse Code »
    26

    Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("sunxi: Use Kconfig CONFIG_MMC") moved
    instances only for SUNXI.

    We generally do not like such partial moves. This kind of work
    is automated by tools/moveconfig.py, so it is pretty easy to
    complete this move.

    I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
    This shortens the configs and will ease new board porting.

    This commit was created as follows:

    [1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

    [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

28 Oct, 2016

1 commit

12 Oct, 2016

1 commit

27 Sep, 2016

1 commit

20 Sep, 2016

1 commit

  • 9b1b6d422   Revert "Increase default of CONFIG_SYS_MALLOC_F_LEN for SPL_OF_CONTROL" ... Browse Code »

    This reverts commit 90c08d9e08c7a108ab904f3bbdeb558081757892.

    I took a closer look at this after the commit was applied, and found
    CONFIG_SYS_MALLOC_F_LEN=0x2000 was too much. 8KB memory for SPL is
    actually too big for some boards. Perhaps 0x800 is enough, but the
    situation varies board by board.

    Let's postpone our decision until we come up with a better idea.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Simon Glass

    Masahiro Yamada
     

17 Sep, 2016

7 commits

10 Sep, 2016

1 commit

07 Sep, 2016

1 commit

10 Jun, 2016

1 commit

26 Apr, 2016

2 commits

14 Jan, 2016

1 commit

  • aefb8f4c3   mvebu: Support Synology DS414 ... Browse Code »

    This adds support for the MV78230 based DS414 NAS by Synology. The
    relevant bits have been extracted from the 'synogpl-5004-armadaxp'
    package Synology kindly published, garnished with a fair amount of
    trial-and-error.

    Sadly, support is far from perfect. The major parts I have failed in
    are SATA and XHCI support. Details about these and some other things
    follow:

    Device Tree
    -----------

    The device tree file armada-xp-synology-ds414.dts has been copied from
    Linux and enhanced by recent U-Boot specific changes to
    armada-xp-gp.dts.

    SATA Support
    ------------

    There is a Marvell 88SX7042 controller attached to PCIe which is
    supported by Linux's sata_mv driver but sadly not U-Boot's sata_mv.
    I'm not sure if extending the latter to support PCI devices is worth the
    effort at all. Porting sata_mv from Linux exceeded my brain's
    capacities. :(

    XHCI Support
    ------------

    There is an EtronTech EJ168A XHCI controller attached to PCIe which
    drives the two rear USB3 ports. After a bit of playing around I managed
    to get it recognized by xhci-pci, but never was able to access any
    devices attached to it. Enabling it in ds414 board config shows that it
    does not respond to commands for whatever reason. The (somewhat) bright
    side to it is that it is not even supported in Synology's customized
    U-Boot, but that also means nowhere to steal the relevant bits from.

    EHCI Support
    ------------

    This seems functional after issuing 'usb start'. At least it detects USB
    storage devices, and IIRC reading from them was OK. OTOH Linux fails to
    register the controller if 'usb start' wasn't given before in U-Boot.

    According to Synology sources, this board seems to support USB device
    (gadget?) mode. Though I didn't play around with it.

    PCIe Support
    ------------

    This is fine, but trying to gate the clocks of unused lanes will hang
    PCI enum. In addition to that, pci_mvebu seems not to support DM_PCI.

    DDR3 Training
    -------------

    Marvell/Synology uses eight PUPs instead of four. Does not look like
    this is meant to be customized in mainline U-Boot at all. OTOH I have
    no idea what a "PUP" actually is.

    PEX Init
    --------

    Synology uses different values than mainline U-Boot with this patch:
    pex_max_unit_get returns 2, pex_max_if_get returns 7 and
    max_serdes_lines is set to 7. Not changing this seems to not have an
    impact, although I'm not entirely sure it does not cause issues I am not
    aware of.

    Static Environment
    ------------------

    This allows to boot stock Synology firmware at least. In order to be a
    little more flexible when it comes to booting custom kernels, do not
    only load zImage partition, but also rd.gz into memory. This way it is
    possible to use about 7MB for kernel with piggyback initramfs.

    Signed-off-by: Phil Sutter
    Acked-by: Stefan Roese
    Reviewed-by: Tom Rini

    Phil Sutter