MAINTAINERS: Add missing boards and config entriesAs part of my usual round of build testing, output about missingMAINTAINERS information was not logged, and thus often overlooked.Correct that mi
MAINTAINERS: Add missing boards and config entriesAs part of my usual round of build testing, output about missingMAINTAINERS information was not logged, and thus often overlooked.Correct that mistake by ensuring that I log the output ofgenboardscfg.py every time. As part of that, address a number ofmissing MAINTAINERS entires. In the case of a missing file, I have putthe original submitter down. In the rest of the cases I have added theconfig (and sometimes relevant header file) to the existing set of fileglobs.Change-Id: Ic4524445489daba323d638470c369ad914d5bfefSigned-off-by: Tom Rini <trini@konsulko.com>Signed-off-by: Kever Yang <kever.yang@rock-chips.com>(cherry picked from commit 79df00fdb40b4584919c8bcef42d323a8d38d0f1)
show more ...
env: Rename setenv() to env_set()We are now using an env_ prefix for environment functions. Rename setenv()for consistency. Also add function comments in common.h.Suggested-by: Wolfgang Denk <wd
env: Rename setenv() to env_set()We are now using an env_ prefix for environment functions. Rename setenv()for consistency. Also add function comments in common.h.Suggested-by: Wolfgang Denk <wd@denx.de>Signed-off-by: Simon Glass <sjg@chromium.org>
mvebu: ds414: Move cmd_syno into ds414 directoryWhen we switch to including all linker lists in SPL it is important tonot include commands as that may lead to link errors due to other thingswe ha
mvebu: ds414: Move cmd_syno into ds414 directoryWhen we switch to including all linker lists in SPL it is important tonot include commands as that may lead to link errors due to other thingswe have already discarded. In this case as we don't have other commoncode nor other Synology borads, move the cmd_syno.c file (which claimsto be ds414 specific anyways!) into the ds414 directory and only buildit for non-SPL builds.Signed-off-by: Tom Rini <trini@konsulko.com>
mvebu: Support Synology DS414This adds support for the MV78230 based DS414 NAS by Synology. Therelevant bits have been extracted from the 'synogpl-5004-armadaxp'package Synology kindly published,
mvebu: Support Synology DS414This adds support for the MV78230 based DS414 NAS by Synology. Therelevant bits have been extracted from the 'synogpl-5004-armadaxp'package Synology kindly published, garnished with a fair amount oftrial-and-error.Sadly, support is far from perfect. The major parts I have failed inare SATA and XHCI support. Details about these and some other thingsfollow:Device Tree-----------The device tree file armada-xp-synology-ds414.dts has been copied fromLinux and enhanced by recent U-Boot specific changes toarmada-xp-gp.dts.SATA Support------------There is a Marvell 88SX7042 controller attached to PCIe which issupported 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 theeffort at all. Porting sata_mv from Linux exceeded my brain'scapacities. :(XHCI Support------------There is an EtronTech EJ168A XHCI controller attached to PCIe whichdrives the two rear USB3 ports. After a bit of playing around I managedto get it recognized by xhci-pci, but never was able to access anydevices attached to it. Enabling it in ds414 board config shows that itdoes not respond to commands for whatever reason. The (somewhat) brightside to it is that it is not even supported in Synology's customizedU-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 USBstorage devices, and IIRC reading from them was OK. OTOH Linux fails toregister 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 hangPCI 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 likethis is meant to be customized in mainline U-Boot at all. OTOH I haveno 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 andmax_serdes_lines is set to 7. Not changing this seems to not have animpact, although I'm not entirely sure it does not cause issues I am notaware of.Static Environment------------------This allows to boot stock Synology firmware at least. In order to be alittle more flexible when it comes to booting custom kernels, do notonly load zImage partition, but also rd.gz into memory. This way it ispossible to use about 7MB for kernel with piggyback initramfs.Signed-off-by: Phil Sutter <phil@nwl.cc>Acked-by: Stefan Roese <sr@denx.de>Reviewed-by: Tom Rini <trini@konsulko.com>