[U-Boot] [PATCH 3/6] net: phy: realtek: Use generic genphy_parse_link() for RTL8211E

The problem with current implementation is that SPDDONE bit is 1 but link bit is zero. That's why phydev->link is setup to 0 which ending up in driver failure that link is not up. Log: Zynq> dhcp ethernet@e000b000 Waiting for PHY auto negotiation to complete... done ethernet@e000b000: No

[U-Boot] [PATCH 1/6] net: gem: Add support for reading MAC from I2C EEPROM

Add support for reading MAC address from I2C EEPROM. Signed-off-by: Michal Simek --- drivers/net/zynq_gem.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/net/zynq_gem.c b/drivers/net/zynq_gem.c index b3821c31a91d..ace60c901cb5 100644 ---

[U-Boot] [PATCH 2/6] ARM: zynq: zybo: Enabling reading MAC address from EEPROM

Zybo has on board I2C EEPROM which contains preprogrammed MAC address. Signed-off-by: Michal Simek --- include/configs/zynq_zybo.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/include/configs/zynq_zybo.h b/include/configs/zynq_zybo.h index

[U-Boot] [PATCH 4/6] ARM: zynq: Enable Realtek phys by default

This phy is available at Zybo board. Signed-off-by: Michal Simek --- include/configs/zynq-common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/configs/zynq-common.h b/include/configs/zynq-common.h index e8c3ef0c3872..7b42a00b9e75 100644 ---

[U-Boot] [PATCH 6/6] ARM: zynq: Enable EDID for zybo

Zybo contains on board HDMI that's why enable EDID. Doing it via config because zynq i2c driver hasn't been moved to DM yet and enabling via Kconfig requires DM_I2C. This will be moved that driver is moved to DM. Signed-off-by: Michal Simek --- Currently the biggest problem is

[U-Boot] [PATCH 5/6] ARM: zynq: Add reset-gpio property for USB on Zybo

DTS syncup with Linux kernel. Add missing reset-gpio property. Signed-off-by: Michal Simek --- This patch is in queue to next kernel version --- arch/arm/dts/zynq-zybo.dts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/dts/zynq-zybo.dts

[U-Boot] [PATCH] ARM: zynq: Wire-up saving environment to QSPI

Extend options for saving variables to QSPI. Signed-off-by: Michal Simek --- include/configs/zynq-common.h | 4 1 file changed, 4 insertions(+) diff --git a/include/configs/zynq-common.h b/include/configs/zynq-common.h index 73b7f2072bc6..1eee8a0667dc 100644 ---

[U-Boot] oddity(?) in selection of FCC Ethernet index in 2014 version of u-boot

at the moment, i'm trying to get a minimal u-boot running on an MPC8280-based target board (please, no jokes), and for the sake of expediency, i just used git to check out a version of u-boot just before it removed the definition of a target board (MPC8260ads) that seems moderately close

[U-Boot] Compilation errors after enabling the flash support

Dell - Internal Use - Confidential Hi, I am developing U-Boot for ARM CPU and enabled FLASH support. During the compilation getting the following error - arch/arm/lib/libarm.o: In function `board_init_r':

[U-Boot] [RFC PATCH v4 2/3] common: Convert ulong to phys_addr_t for image addresses

When dealing with image addresses, ulong has been used. Some files are used by both host and target. It is OK for the target, but not always enough for host tools including mkimage. This patch replaces "ulong" with "phys_addr_t" to make sure addresses are correct for both the target and the host.

[U-Boot] How to boot bare board binary from U-Boot>

Hello, How can we boot independent bare board binary(not standalone binary which runs using U-Boot environment and not linux kernel) from U-Boot. My requirement is to reinitialize the board and drivers using my binary... I can replace the U-Boot in the boot medium(here NOR Flash) with my binary

[U-Boot] [RFC PATCH v4 0/3] Enable FIT image to be loaded beyond 32-bit space

Please comment on these changes. Don't apply yet. I think there may be compiling warnings on some platforms. Want to get some feedback before going too far on this path. This set fixes compiling warnings for sandbox on 32-bit host (Ubuntu), convert ulong to phys_addr_t for image handling. The

Re: [U-Boot] How to boot bare board binary from U-Boot>

Hi you can either run the binary directly from memory or you can build a uboot image from your raw binary using the mkimage command. Michael On Fri, Feb 12, 2016 at 10:32 AM, veerendranathj wrote: > Hello, > > How can we boot independent bare board binary(not standalone

Re: [U-Boot] [PATCH] sunxi: H3: Add support for the host usb-phys

Hi, On Wed, Feb 10, 2016 at 5:25 PM, Hans de Goede wrote: > From: Jelle van der Waa > > Add support for phy 1-3. > > Signed-off-by: Jelle van der Waa > [hdego...@redhat.com: use setclrbits_le32 instead of read-modify-write] > Signed-off-by:

Re: [U-Boot] [PATCH 1/6] net: gem: Add support for reading MAC from I2C EEPROM

Hi Michal, On Sat, Feb 13, 2016 at 6:39 PM, Michal Simek wrote: > Add support for reading MAC address from I2C EEPROM. > Is this a feature provided by the GEM MAC IP? > Signed-off-by: Michal Simek > --- > > drivers/net/zynq_gem.c | 16 > 1

Re: [U-Boot] [RFC PATCH v1 2/2] arm: ls1021aqds: Enable driver model lpuart serial driver

Hi York, On Tue, Feb 9, 2016 at 8:57 AM, York Sun wrote: > Convert ls1021aqds_nor_lpuart and ls1021aqds_ddr4_nor_lpuart > to driver model suport. Enable lpuart port driver. > > Signed-off-by: York Sun > CC: Alison Wang > CC: Bin Meng

Re: [U-Boot] [PATCH] x86: fix memalign() parameter order

Hi Stephen, On Sat, Feb 13, 2016 at 5:27 AM, Stephen Warren wrote: > From: Stephen Warren > > Purely by code inspection, it looks like the parameter order to memalign() > is swapped; its parameters are (align, size). 4096 is a likely desired >

Re: [U-Boot] [PATCH] x86: fix memalign() parameter order

On 12 February 2016 at 14:27, Stephen Warren wrote: > From: Stephen Warren > > Purely by code inspection, it looks like the parameter order to memalign() > is swapped; its parameters are (align, size). 4096 is a likely desired > alignment, and a

Re: [U-Boot] [PATCH v2 5/5] x86: Add Intel Cougar Canyon 2 board

Hi Simon, On Wed, Feb 10, 2016 at 6:23 AM, Simon Glass wrote: > Hi Bin, > > On 5 February 2016 at 23:08, Bin Meng wrote: >> This adds basic support to Intel Cougar Canyon 2 board, a board >> based on Chief River platform with an Ivy Bridge processor and >>