summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | net: nfs: don't fail when nfs_read_reply returns -NFS_RPC_DROPVasily Khoruzhick2018-06-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | That can happen if duplicate UDP packet arrived, and that's not uncommon. Anyway, we ignore packets with rpc_id lower than last we sent for other requests, so it makes sense to do that for read request as well. Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: cpsw: ti: Reap completed packets before stopping interfaceAlex Kiernan2018-06-131-8/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you send a final packet just before stopping the interface (e.g. a final ACK as part of the UDP fastboot protocol), then that packet isn't reliably delivered onto the wire. Reap packets prior to stopping the interface to ensure any which are in-flight make it out. Also remove buffer and len from the call to cpdma_process() as we weren't using them on their return. Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: Protect net_state from reentrant net_loop()Leonid Iziumtsev2018-06-131-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Global variable "net_state" is used in net_loop() state-machine. But it happens that some times the net_loop() can be called multiple times in the same call stack. For example when the netconsole is enabled and we print the message while some other net protocol is in action. Netconsole will overwrite the "net_state" and that will break the logic for earlier started protocol. To protect the state save and restore "net_state" variable each time when we enter and exit net_loop(). Signed-off-by: Leonid Iziumtsev <leonid.iziumtsev@se.atlascopco.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net/phy/cortina: Add support for CS4223 PHYVicentiu Galanopulo2018-06-133-1/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for Cortina CS4223 10G PHY - As per the CS4223 specs, an EEPROM module is connected to the PHY. At startup the PHY reads the firmware line and tries to load the firmware into the internal memory. - This driver reads the EEPROM status and checks if firmware has been loaded Signed-off-by: Vicentiu Galanopulo <vicentiu.galanopulo@nxp.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: sunxi: Correct MAC address register orderJoe Hershberger2018-06-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Put the enetaddr data in the same order as it was before the change in commit ace1520cb5fc ("net: sunxi-emac: Write HW address via function") Reported-by: Udo Maslo <u.maslo@web.de> Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: Express LINK_LOCAL dependency on LIB_RANDJoe Hershberger2018-06-131-0/+1
| | | | | | | | | | | | | | | | Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | tsec: Fix reading phy registers from DTMario Six2018-06-131-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bus translations should be applied when reading the address of the sgmii phy registers from the DT. Use ofnode_get_addr_index instead of the plain ofnode_read_u32_default to fix this. Signed-off-by: Mario Six <mario.six@gdsys.cc> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: Initialize as many ethernet devices as possibleMario Six2018-06-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On devices that have their first network interface provided by a FPGA, the initialization of further interfaces will fail if the FPGA is not yet programmed. This leads to problems during factory setup when the data is supposed to be loaded over secondary netowork interfaces. To avoid this, use the uclass_{first,next}_device_check functions to initialize as many ethernet devices as possible. Signed-off-by: Mario Six <mario.six@gdsys.cc> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
| * | | net: Always align tx packetsMario Six2018-06-132-2/+4
| |/ / | | | | | | | | | | | | | | | | | | Make sure that TX packets are always cache-aligned. Signed-off-by: Mario Six <mario.six@gdsys.cc> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
* | | Merge git://git.denx.de/u-boot-x86Tom Rini2018-06-1332-211/+357
|\ \ \ | |/ / |/| |
| * | x86: cougarcanyon2: Add missing chipset interrupt informationBin Meng2018-06-132-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | Add Panther Point chipset interrupt pin/PIRQ information, and enable the generation of PIRQ routing table and MP table. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: irq: Support discrete PIRQ routing registers via device treeBin Meng2018-06-133-33/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently both pirq_reg_to_linkno() and pirq_linkno_to_reg() assume consecutive PIRQ routing control registers. But this is not always the case on some platforms. Introduce a new device tree property intel,pirq-regmap to describe how the PIRQ routing register offset is mapped to the link number and adjust the irq router driver to utilize the mapping. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: irq: Parse number of PIRQ links from device treeBin Meng2018-06-132-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "intel,pirq-link" property in Intel IRQ router's dt bindings has two cells, where the second one represents the number of PIRQ links on the platform. However current driver does not parse this information from device tree. This adds the codes to do the parse and save it for future use. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: efi: payload: Minor clean up on error message outputBin Meng2018-06-131-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | If GetMemoryMap() fails, we really want to know EFI_BITS_PER_LONG instead of BITS_PER_LONG. A space and LF are added in places where error message is output to improve readability. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | dm: pci: Use a 1:1 mapping for bus <-> phy addressesChristian Gmeiner2018-06-131-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If U-Boot gets used as coreboot payload all pci resources got assigned by coreboot. If a dts without any pci ranges gets used the dm is not able to access pci device memory. To get things working make use of a 1:1 mapping for bus <-> phy addresses. This change makes it possible to get the e1000 U-Boot driver working on a sandybridge device where U-Boot is used as coreboot payload. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> [bmeng: fixed 'u-boot' in the commit message] Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | dm: pci: Make ranges dt property optionalChristian Gmeiner2018-06-131-13/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we use U-Boot as coreboot payload with a generic dts without any ranges specified we fail in pci pre_probe and our pci bus is not usable. So convert decode_regions(..) into a void function and do the simple error handling there. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> [bmeng: fixed 'u-boot' in the commit message and checkpatch warning] Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: efi: payload: Enforce toolchain to generate 64-bit EFI payload stub codesBin Meng2018-06-133-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempting to use a toolchain that is preconfigured to generate code for the 32-bit architecture (i386), for example, the i386-linux-gcc toolchain on kernel.org, to compile the 64-bit EFI payload does not build. This updates the makefile fragments to ensure '-m64' is passed to toolchain when building the 64-bit EFI payload stub codes. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: efi: app: Fix broken EFI applicationBin Meng2018-06-131-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The EFI application does not boot currently. It's due to the call to syscon_get_by_driver_data() in cpu_init_r() maps to nowhere as CONFIG_SYSCON is not included in the configuration. EFI application is built as a shared library, so GCC won't complain during the build process if some symbols are not found. GCC will simply put these symbols into the .plt section and expect dynamic loader to fix these up. While we are here, remove some commands and drivers that are not needed at present. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: Conditionally build the pinctrl_ich6 driverBin Meng2018-06-134-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | The pinctrl_ich6 driver is currently unconditionally built for all x86 boards. Let's use a Kconfig option to control the build. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: irq: Change LINK_V2N and LINK_N2V to inline functionsBin Meng2018-06-132-10/+34
| | | | | | | | | | | | | | | | | | | | | | | | LINK_V2N and LINK_N2V are currently defines, so they cannot handle complex logics. Change to inline functions for future extension. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: irq: Remove chipset specific irq router driversBin Meng2018-06-1310-129/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At present there are 3 irq router drivers. One is the common one and the other two are chipset specific for queensbay and quark. However these are really the same drivers as the core logic is the same. The two chipset specific drivers configure some registers that are outside the irq router block which should really be part of the chipset initialization. Now we remove these specific drivers and make all x86 boards use the common one. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: cougarcanyon2: Enable CPU driver and SMP supportBin Meng2018-06-132-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | This enables the 206ax cpu driver on Intel Cougar Canyon 2 board, so that SMP can be supported too. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: chromebook_link: Remove dm-pre-reloc property in the cpu nodesBin Meng2018-06-131-5/+0
| | | | | | | | | | | | | | | | | | | | | The 206ax cpu driver does not require pre-relocation flag to work. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: ivybridge: Drop CONFIG_USBDEBUGBin Meng2018-06-133-21/+0
| | | | | | | | | | | | | | | | | | | | | This is not used anywhere. Clean this up. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: ivybridge: Enable 206ax cpu driver for FSP buildBin Meng2018-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | At present this 206ax cpu driver is only built when FSP is not used. This updates the Makefile to enable the build for both cases. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: cougarcanyon2: Remove CONFIG_HAVE_INTEL_MEBin Meng2018-06-132-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As README.x86 already mentions, there are two SPI flashes mounted on Intel Cougar Canyon 2 board, called SPI-0 and SPI-1 respectively. SPI-0 stores the flash descriptor and the ME firmware. SPI-1 stores the actual BIOS image which is U-Boot. Building a single image with both ME firmware and U-Boot does not make sense. This also describes the exact flash location where the u-boot.rom should be programmed in the documentation. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: cougarcanyon2: Update dts for SPI lock downBin Meng2018-06-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turns out that like Braswell, Intel FSP for IvyBridge requires SPI controller settings to be locked down, as the U-Boot ICH SPI driver fails with the following message on Cougar Canyon 2 board: "ICH SPI: Opcode 9f not found" Update the SPI node property to indicate this fact. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: ivybridge: Imply USB_XHCI_HCDBin Meng2018-06-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | The Panther Point chipset connected to Ivybridge has xHC integrated, imply it. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | usb: xhci-pci: Fix compiler warningBin Meng2018-06-131-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the following compiler warning: "warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]" Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: baytrail: Correct the comment of IACORE_VIDS bit rangesBin Meng2018-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The guaranteed vid bit ranges in IACORE_VIDS MSR is actually [22:16]. This corrects the comment for it. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | x86: acpi: Adopt new version of iASL compilerAndy Shevchenko2018-06-131-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The commit f9a88a4c1cd0 ("iASL: Enhance the -tc option (create AML hex file in C)") in ACPICA project changed a template of the variable that is used in the generated C-file. Now, instead of hard coded "AmlCode" the "%s_aml_code" is in use, where the prefix is a lowered case base name of the output file. In our case it will be "dsdt" producing a name as "dsdt_aml_code". The quick solution is to call sed which replaces new name by the old one to keep compatibility with old version of iASL. The long term solution would be to modify code to use the new name because it is more scalable. Cc: Robert Moore <robert.moore@intel.com> Cc: Sami Mujawar <sami.mujawar@arm.com> Cc: Evan Lloyd <evan.lloyd@arm.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> [bmeng: fixed two sentences in the commit message] Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
| * | x86: tsc: add support for reading CPU freq from cpuidChristian Gmeiner2018-06-131-5/+24
| |/ | | | | | | | | | | | | | | | | | | | | | | Starting with cpuid level 0x16 (Skylake-based processors) it is possible to get CPU base freq via cpuid. This fixes booting on a skylake based system. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> [bmeng: fixed wrong indention of labels] Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
* | ARM: DTS: resync a3517.dtsi with Linux 4.17Adam Ford2018-06-131-6/+2
| | | | | | | | | | | | | | Linux 4.17 was just released with some minor changes to the am3517.dtsi. This patch re-syncs the file. Signed-off-by: Adam Ford <aford173@gmail.com>
* | ARM: am3517_evm: Enable SPL_OF_CONTROL and SPL_OF_PLATDATAAdam Ford2018-06-132-14/+3
| | | | | | | | | | | | | | | | | | | | The SPL doesn't have much room, so in order to support OF_CONTROL in SPL, we need the extra functionality of SPL_OF_PLATDATA. Adding these features allows us to remove a small part of code without losing the serial port during SPL. Signed-off-by: Adam Ford <aford173@gmail.com>
* | dra76: fix HDMI HPD pinmuxTomi Valkeinen2018-06-131-1/+1
| | | | | | | | | | | | | | The pin used for HDMI HPD should be set to GPIO mode on DRA76, similarly to all the other DRA7 and AM5 SoCs. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
* | dra7/am5: remove CEC pin pull-upTomi Valkeinen2018-06-132-7/+7
| | | | | | | | | | | | HDMI CEC pins are set to pull-up, but CEC requires no pull. Fix this. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
* | env: Add !ENV_IS_IN_EXT4 dependency to ENV_IS_NOWHEREAlex Kiernan2018-06-131-0/+1
| | | | | | | | | | | | | | | | If ENV_IS_IN_EXT4 is set you shouldn't be able to select ENV_IS_NOWHERE. Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Petr Vorel <petr.vorel@gmail.com>
* | u-boot: Fix several typosShyam Saini2018-06-137-10/+10
| | | | | | | | | | | | | | 's/environemnt/environment/' and 's/Environemnt/Environment/' Signed-off-by: Shyam Saini <shyam@amarulasolutions.com>
* | tools: env: Use getline rather than fgets when reading config/scriptAlex Kiernan2018-06-131-19/+21
| | | | | | | | | | | | | | | | | | | | When reading the config file, or a script file, use getline rather than fgets so line lengths aren't limited by the size of a compiled in buffer (128 characters for config, 1024 for scripts). Rename 'dump' to 'line' so it's clear we're working with a line of text. Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
* | AM3517_EVM: Fix Environmental locationAdam Ford2018-06-131-0/+1
| | | | | | | | | | | | | | | | | | | | The am3517-evm boards stores the environment in NAND, but after merging various configs, the board was trying to load environment variables from FAT which would ultimately fail and cause some chatter. This patch removes the ENV_IS_IN_FAT flag to eliminate the noise. Signed-off-by: Adam Ford <aford173@gmail.com>
* | lib: Add hexdumpAlexey Brodkin2018-06-1315-29/+369
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Often during debugging session it's very interesting to see what data we were dealing with. For example what we write or read to/from memory or peripherals. This change introduces functions that allow to dump binary data with one simple function invocation like: ------------------->8---------------- print_hex_dump_bytes("", DUMP_PREFIX_OFFSET, buf, len); ------------------->8---------------- which gives us the following: ------------------->8---------------- 00000000: f2 b7 c9 88 62 61 75 64 72 61 74 65 3d 31 31 35 ....baudrate=115 00000010: 32 30 30 00 62 6f 6f 74 61 72 67 73 3d 63 6f 6e 200.bootargs=con 00000020: 73 6f 6c 65 3d 74 74 79 53 33 2c 31 31 35 32 30 sole=ttyS3,11520 00000030: 30 6e 38 00 62 6f 6f 74 64 65 6c 61 79 3d 33 00 0n8.bootdelay=3. 00000040: 62 6f 6f 74 66 69 6c 65 3d 75 49 6d 61 67 65 00 bootfile=uImage. 00000050: 66 64 74 63 6f 6e 74 72 6f 6c 61 64 64 72 3d 39 fdtcontroladdr=9 00000060: 66 66 62 31 62 61 30 00 6c 6f 61 64 61 64 64 72 ffb1ba0.loadaddr 00000070: 3d 30 78 38 32 30 30 30 30 30 30 00 73 74 64 65 =0x82000000.stde 00000080: 72 72 3d 73 65 72 69 61 6c 30 40 65 30 30 32 32 rr=serial0@e0022 00000090: 30 30 30 00 73 74 64 69 6e 3d 73 65 72 69 61 6c 000.stdin=serial 000000a0: 30 40 65 30 30 32 32 30 30 30 00 73 74 64 6f 75 0@e0022000.stdou 000000b0: 74 3d 73 65 72 69 61 6c 30 40 65 30 30 32 32 30 t=serial0@e00220 000000c0: 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.............. ... ------------------->8---------------- Source of hexdump.c was copied from Linux kernel v4.7-rc2. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Anatolij Gustschin <agust@denx.de> Cc: Mario Six <mario.six@gdsys.cc> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@konsulko.com> Cc: Stefan Roese <sr@denx.de>
* | fs: btrfs: Fix not all CHUNK_ITEMs being read from CHUNK_TREEYevgeny Popovych2018-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This causes errors when translating logical addresses to physical: btrfs_map_logical_to_physical: Cannot map logical address <addr> to physical btrfs_file_read: Error reading extent The behavior of btrfs_map_logical_to_physical() is to stop traversing CHUNK_TREE when it encounters first non-CHUNK_ITEM, which makes only some portion of CHUNK_ITEMs being read. Change it to skip over non-chunk items. Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com> Cc: Marek Behun <marek.behun@nic.cz> Cc: Sergey Struzh <sergeys@pointgrab.com> Reviewed-by: Marek Behun <marek.behun@nic.cz>
* | ARM64: meson: Sync DT with Linux 4.17Neil Armstrong2018-06-1310-237/+103
| | | | | | | | | | | | | | | | | | Synchronize the Linux Device Tree for Amlogic Meson GX boards from Linux 4.17.0 This will enable USB on Amlogic Meson GXL Boards like Khadas VIM, P212 or LibreTech-CC. Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
* | fs: fat: fix wrong casting to unsigned value of sect_to_cluster()Seung-Woo Kim2018-06-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | After the commit 265edc03d5a1 ("fs/fat: Clean up open-coded sector <-> cluster conversions"), it is hung up writing new file to FAT16 disk with more than 19 files in armv7. It is because result value of sect_to_cluster() is not proper by casting from signed value to unsigned value. Fix the wrong casting of sect_to_cluster(). Reported-by: Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by: Seung-Woo Kim <sw0312.kim@samsung.com> Reviewed-by: Lukasz Majewski <lukma@denx.de>
* | include/linux/byteorder: Sync to latest Linux definitionsRamon Fried2018-06-121-40/+67
| | | | | | | | | | | | | | | | | | | | generic.h has changed in Linux and new addtionals functions were added. This commit takes the latest and greatest from Linux (v4.17-rc5) to aid with porting drivers that utilize these functions. Signed-off-by: Ramon Fried <ramon.fried@gmail.com>
* | doc: cmd: bubt: drop duplicated textBaruch Siach2018-06-121-9/+0
| | | | | | | | | | | | | | | | This commit removes text that is exact duplicated of the text above. Cc: Konstantin Porotchkin <kostap@marvell.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: Stefan Roese <sr@denx.de>
* | configs: pcm051: Use am335x-wega-rdk.dtb as fdtfileMatwey V. Kornilov2018-06-121-1/+1
| | | | | | | | | | | | | | In upstream Linux kernel, the fdtfile for this specific board is called am335x-wega-rdk.dtb Signed-off-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
* | configs: pcm051: Use DEFAULT_LINUX_BOOT_ENV instead of hardcoded valuesMatwey V. Kornilov2018-06-121-3/+1
| | | | | | | | | | | | It appears that DEFAULT_LINUX_BOOT_ENV can be used to boot pcm051 board. Signed-off-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
* | configs: pcm051: Use DEFAULT_MMC_TI_ARGS instead of hardcoded duplicatesMatwey V. Kornilov2018-06-121-8/+5
| | | | | | | | Signed-off-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
* | configs: pcm051: Support distro bootcmdsMatwey V. Kornilov2018-06-121-20/+29
|/ | | | | | Add support for distro bootcmds. Signed-off-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
View Lorry Controller Status