On Wed, Oct 12, 2016 at 3:40 AM, Jörg Krause
wrote:
> On Sa, 2016-10-08 at 18:00 +0530, Jagan Teki wrote:
>> From: Jagan Teki
>>
>> Added kconfig for NAND_MXS driver.
>>
>> Cc: Scott Wood
>> Cc: Simon Glass
>> Cc: Fabio Estevam
>> Cc: Stefano Babic
>> Cc: Peng Fan
>> Cc: Matteo Lisi
>> Cc:
On Tuesday 11 October 2016 05:49 AM, Simon Glass wrote:
Hi Keerthy,
On 15 September 2016 at 05:16, Keerthy wrote:
On Thursday 15 September 2016 04:38 PM, Keerthy wrote:
On Thursday 15 September 2016 04:26 PM, Przemyslaw Marczak wrote:
Hello Keerthy,
On 09/15/2016 10:54 AM, Keerthy w
AT91 PIO controller is a combined gpio-controller, pin-mux and
pin-config module. The peripheral's pins are assigned through
per-pin based muxing logic.
Each soc will have to describe the SoC limitation and pin
configuration via DT. This will allow to do not need to touch
the C code when adding ne
The intention of this patch is the preparation to introduce
the pinctrl driver for AT91 PIO.
Use "union" to make the PIO3 and PIO2's registers be together
and make their offset aligned.
Signed-off-by: Wenyou Yang
---
arch/arm/mach-at91/include/mach/at91_pio.h | 61
arch/arm/mach
The purpose of this patch set is to add the pinctrl driver for AT91
PIO controller.
Wenyou Yang (2):
gpio: at91_gpio: Remove CPU_HAS_PIO3 macro
pinctrl: pinctrl-at91: Add pinctrl driver
arch/arm/mach-at91/include/mach/at91_pio.h | 67 ++--
arch/arm/mach-at91/include/mach/at91sam9x5.h
Hi
On 10/11/2016 11:08 PM, Oscar Gomez Fuente wrote:
> Hi everyone,
>
> I've just compiled u-boot for a picoZed platform with
> the zynq_picozed_defconfig, and I've realised that the NET and SD Card
> aren't recognised. In the init I see these messages:
>
> I boot from the SD Card and I see thes
Fix the divider calculation logic to choose a value so that the
resulting baudrate is either equal to or closest possible baudrate less
than the requested value.
Signed-off-by: Vignesh R
---
drivers/spi/ti_qspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/t
Update the spi-max-frequency property of m25p80 flash slave to match
that of TI QSPI controller node, so that QSPI operations happen at
maximum supported frequency of 76.8MHz.
Signed-off-by: Vignesh R
---
arch/arm/dts/dra7-evm.dts | 2 +-
arch/arm/dts/dra72-evm-common.dtsi | 2 +-
2 fil
On 10/11/2016 08:00 PM, Yao Yuan wrote:
>>
>> Yuan Yao,
>>
>> I think the procedure can be applied to many of our boards with QSPI, right?
>> It
>> may be better to move this information out of ls2080aqds.
>>
>
> Hi York,
>
> Yes, but a little difference for "CCSR write" for different boards.
> B
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> Legacy video driver macros are not needed. Clean them up.
>>
>> Signed-off-by: Bin Meng
>>
>> ---
>>
>> include/configs/cougarcanyon2.h | 4
>> include/configs/efi-x86.h| 2 --
>>
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> This converts coreboot to use DM framebuffer driver.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> arch/x86/cpu/coreboot/Kconfig | 4
>> arch/x86/dts/bayleybay.dts | 1 +
>> arc
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> Now that all x86 boards have been converted to DM video, drop the
>> legacy drivers.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/video/coreboot_fb.c | 108
>>
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> With DM VESA driver on x86 boards, plat->base/size/align are all
>> zeroes and starting address passed to alloc_fb() happens to be 1MB
>> aligned, so this routine does not trigger any issue. On QE
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> vbe_setup_video_priv() might be useful to other drivers.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/pci/pci_rom.c | 6 +++---
>> include/vbe.h | 4
>> 2 files changed, 7 ins
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> This adds a DM driver for coreboot framebuffer device.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/video/Kconfig| 9 ++
>> drivers/video/coreboot.c | 79
>> +
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> For some unknown reason, coreboot framebuffer driver never works on
>> QEMU since day 1. It seems the driver only works on real hardware.
>> Document this issue.
>>
>> Signed-off-by: Bin Meng
>>
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> This adds a DM driver for VESA compatible device.
>
> nit: VESA-compatible
Fixed nits, and
>
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/video/vesa.c | 34 ++
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> At present only chromebook boards are converted to DM video. Other
>> x86 boards are still using the legacy cfb_console driver. This
>> switches to use DM version drivers.
>>
>> Signed-off-by: Bin
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> With DM conversion, information like "Video: 1024x768x16" is not
>> shown anymore. Now add these verbose output back.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> drivers/pci/pci_rom.c | 9 +++
On Wed, Oct 12, 2016 at 8:06 AM, Simon Glass wrote:
> On 9 October 2016 at 05:14, Bin Meng wrote:
>> The kernel load address for zboot should be 0x100.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> doc/README.x86 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Simon G
Hi Tom,
The following changes since commit f5fd45ff64e28a73499548358e3d1ceda0de7daf:
Merge branch 'master' of git://www.denx.de/git/u-boot-imx
(2016-10-08 09:33:37 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-x86.git master
for you to fetch changes up to 00bcaedd
Hi everyone,
I've just compiled u-boot for a picoZed platform with
the zynq_picozed_defconfig, and I've realised that the NET and SD Card
aren't recognised. In the init I see these messages:
I boot from the SD Card and I see these messages from my uart terminal:
-
U-Boot 2016
Hi all
> -Original Message-
> From: Masahiro Yamada [mailto:yamada.masah...@socionext.com]
> Sent: 05 October 2016 04:19
> Hi.
>
> Recently I implemented ARM Trusted Firmware BL31 for my SoCs.
>
> But, I am wondering how the boot-flow should be.
>
I'm no U-Boot expert but as ARM Trusted Fi
Originally dram clock was set to 480MHz, but this behaves
unstable. To improve stability the clock is reduced to 384MHz
Signed-off-by: Stefan Mavrodiev
---
configs/A20-OLinuXino-Lime2_defconfig | 2 +-
configs/A20-OLinuXino-Lime_defconfig | 2 +-
configs/A20-Olimex-SOM-EVB_defconfig | 2 +-
3
Getting the current NAND device is already done once as part
of nand command. Therefore, repeating this step as part of
the sub-commands is unnecessary.
Signed-off-by: Ahmed Samir Khalil
---
cmd/nand.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/cmd/nand.c b/cmd/nand.c
index ec7f1
While dealing with large chips (e.g. page: 4KB, OOB:224),
we found it helpful to get these additional NAND info by
enabling the DEBUG macro instead of full tracing every time
and consuming time. Especially about the currently in use
scheme for testing & development.
Signed-off-by: Ahmed Samir
OK, thanks.
Regards,
Xiaoliang Yang
-Original Message-
From: york sun
Sent: Sunday, October 09, 2016 1:16 AM
To: Xiaoliang Yang; u-boot@lists.denx.de
Subject: Re: [PATCH] armv7: LS1021a: enable i-cache in start.S
On 09/13/2016 08:48 PM, Xiaoliang Yang wrote:
> Delete CONFIG_SKIP_LOWLEV
On Sa, 2016-10-08 at 18:00 +0530, Jagan Teki wrote:
> From: Jagan Teki
>
> Added kconfig for NAND_MXS driver.
>
> Cc: Scott Wood
> Cc: Simon Glass
> Cc: Fabio Estevam
> Cc: Stefano Babic
> Cc: Peng Fan
> Cc: Matteo Lisi
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
> ---
> drivers
Hi Stephen,
On Mon, Oct 10, 2016 at 6:07 PM, Stephen Warren wrote:
> On 09/23/2016 11:43 AM, Joe Hershberger wrote:
>>
>> On Fri, Sep 23, 2016 at 11:31 AM, Stephen Warren
>> wrote:
>>>
>>> On 09/15/2016 01:20 PM, Joe Hershberger wrote:
On Thu, Sep 15, 2016 at 1:53 PM, Stephen Warr
On 9 October 2016 at 05:14, Bin Meng wrote:
> Legacy video driver macros are not needed. Clean them up.
>
> Signed-off-by: Bin Meng
>
> ---
>
> include/configs/cougarcanyon2.h | 4
> include/configs/efi-x86.h| 2 --
> include/configs/galileo.h| 4
> include/configs/
On 9 October 2016 at 05:14, Bin Meng wrote:
> Now that all x86 boards have been converted to DM video, drop the
> legacy drivers.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/video/coreboot_fb.c | 108
>
> drivers/video/vesa_fb.c | 63 -
On 9 October 2016 at 05:14, Bin Meng wrote:
> This converts coreboot to use DM framebuffer driver.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/coreboot/Kconfig | 4
> arch/x86/dts/bayleybay.dts | 1 +
> arch/x86/dts/broadwell_som-6896.dts | 1 +
> arch/x86/dts/chromebo
On 9 October 2016 at 05:14, Bin Meng wrote:
> vbe_setup_video_priv() might be useful to other drivers.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/pci/pci_rom.c | 6 +++---
> include/vbe.h | 4
> 2 files changed, 7 insertions(+), 3 deletions(-)
Reviewed-by: Simon Glass
_
On 9 October 2016 at 05:14, Bin Meng wrote:
> With DM VESA driver on x86 boards, plat->base/size/align are all
> zeroes and starting address passed to alloc_fb() happens to be 1MB
> aligned, so this routine does not trigger any issue. On QEMU with
> U-Boot as coreboot payload, the starting address
On 9 October 2016 at 05:14, Bin Meng wrote:
> This adds a DM driver for coreboot framebuffer device.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/video/Kconfig| 9 ++
> drivers/video/coreboot.c | 79
>
> 2 files changed, 88 insertions(+
On 9 October 2016 at 05:14, Bin Meng wrote:
> At present only chromebook boards are converted to DM video. Other
> x86 boards are still using the legacy cfb_console driver. This
> switches to use DM version drivers.
>
> Signed-off-by: Bin Meng
> ---
>
> configs/bayleybay_defconfig
On 9 October 2016 at 05:14, Bin Meng wrote:
> The kernel load address for zboot should be 0x100.
>
> Signed-off-by: Bin Meng
> ---
>
> doc/README.x86 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass
___
U-Boot mail
On 9 October 2016 at 05:14, Bin Meng wrote:
> With DM conversion, information like "Video: 1024x768x16" is not
> shown anymore. Now add these verbose output back.
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/pci/pci_rom.c | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
Reviewed
On 9 October 2016 at 05:14, Bin Meng wrote:
> This adds a DM driver for VESA compatible device.
nit: VESA-compatible
>
> Signed-off-by: Bin Meng
> ---
>
> drivers/video/vesa.c | 34 ++
> 1 file changed, 34 insertions(+)
> create mode 100644 drivers/video/vesa.c
On 9 October 2016 at 05:14, Bin Meng wrote:
> For some unknown reason, coreboot framebuffer driver never works on
> QEMU since day 1. It seems the driver only works on real hardware.
> Document this issue.
>
> Signed-off-by: Bin Meng
> ---
>
> doc/README.x86 | 3 +++
> 1 file changed, 3 insertio
On 10/10/2016 11:04 PM, Yuan Yao wrote:
> From: Yuan Yao
>
> Signed-off-by: Yuan Yao
> ---
> board/freescale/ls2080aqds/README | 35 +++
> 1 file changed, 35 insertions(+)
>
> diff --git a/board/freescale/ls2080aqds/README
> b/board/freescale/ls2080aqds/README
>
On Tue, Oct 4, 2016 at 12:45 AM, Stephen Warren wrote:
> From: Stephen Warren
>
> This driver supports the Synopsys Designware Ethernet QoS (Quality of
> Service) a/k/a eqos IP block, which is a different design than the HW
> supported by the existing designware.c driver. The IP supports many
> o
Hi Stephen,
On Tue, Sep 27, 2016 at 12:02 AM, Stephen Warren wrote:
> On 09/23/2016 03:49 PM, Joe Hershberger wrote:
>>
>> Hi Stephen,
>>
>> Thanks for sending this! I have some comments below.
>>
>> Cheers,
>> -Joe
>>
>> On Mon, Sep 12, 2016 at 12:48 PM, Stephen Warren
>> wrote:
>>>
>>> From: S
On Tue, Oct 4, 2016 at 12:13 AM, Stephen Warren wrote:
> On 09/23/2016 03:49 PM, Joe Hershberger wrote:
>>
>> Hi Stephen,
>>
>> Thanks for sending this! I have some comments below.
>>
>> Cheers,
>> -Joe
>>
>> On Mon, Sep 12, 2016 at 12:48 PM, Stephen Warren
>> wrote:
>>>
>>> From: Stephen Warren
On Tue, Oct 11, 2016 at 3:15 PM, Otavio Salvador
wrote:
> On Tue, Oct 11, 2016 at 11:09 AM, Diego Dorta wrote:
>> Add a README to explain the steps for booting mx6sabresd in different ways:
>> 1. Booting via Normal U-Boot (u-boot.imx)
>> 2. Booting via SPL (SPL and u-boot.img)
>> 3. B
On Wed, 12 Oct 2016, Jörg Krause wrote:
On Sa, 2016-10-08 at 18:00 +0530, Jagan Teki wrote:
From: Jagan Teki
Added kconfig for NAND_MXS driver.
Cc: Scott Wood
Cc: Simon Glass
Cc: Fabio Estevam
Cc: Stefano Babic
Cc: Peng Fan
Cc: Matteo Lisi
Cc: Michael Trimarchi
Signed-off-by: Jagan Te
Hi Otavio,
On Tue, Oct 11, 2016 at 3:16 PM, Otavio Salvador
wrote:
> I would prefer if it booted on falcon by default and vol-up could make
> it load the U-Boot.img as a recovery option.
In this case we would break existing SPL users of mx6sabresd.
All of a sudden SPL will no longer boot, whic
On Wed, Aug 24, 2016 at 2:35 PM, Roger Quadros wrote:
> Ethernet ports might be used in the kernel even if CPSW driver
> is disabled at u-boot. So always set ethaddr and eth1addr
> environment variable from efuse.
>
> Retain usbnet_devaddr as it is required for SPL USB eth boot.
>
> Signed-off-by:
On Wed, Aug 24, 2016 at 2:35 PM, Roger Quadros wrote:
> Both ethernet ports can be used as CPSW ethernet (RMII mode)
> or PRU ethernet (MII mode) by setting the jumper near the port.
> Read the jumper value and set the pinmux, external mux and
> PHY clock accordingly.
>
> As jumper line is overrid
>
> How much improvement do you get by using "quiet"?
We see around 3-4 seconds being saved on ls1012
You didn't mention lpj
> in the commit message. Did you get the number from kernel log? LS1012A is
> a single core SoC. How much time do you save by setting lpj?
Yes, we got the number from kern
Hi Jagan,
On 9 October 2016 at 08:51, Jagan Teki wrote:
>
> Hi Simon,
>
> On Thu, Oct 6, 2016 at 4:25 PM, Jagan Teki wrote:
> > From: Jagan Teki
> >
> > This patch add driver model support for fec_mxc driver.
> >
> > Cc: Simon Glass
> > Cc: Joe Hershberger
> > Cc: Peng Fan
> > Cc: Stefano Ba
On Thu, Oct 6, 2016 at 12:55 PM, Jagan Teki wrote:
> From: Jagan Teki
>
> Add FEC dts support for Engicam i.CoreM6 dql modules.
>
> Cc: Joe Hershberger
> Cc: Stefano Babic
> Cc: Matteo Lisi
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
Acked-by: Joe Hershberger
__
On Thu, Oct 6, 2016 at 12:55 PM, Jagan Teki wrote:
> From: Jagan Teki
>
> - Remove exctra space
> - Add space
> - Add tab space
> - Fix single line comments quotes
> - Fix 'CHECK: Avoid CamelCase'
> - Fix 'CHECK: Alignment should match open parenthesis'
> - Fix 'WARNING: line over 80 characters'
On Thu, Oct 6, 2016 at 12:55 PM, Jagan Teki wrote:
> fec_get_hwaddr never used eth_device argument, hence removed.
>
> Cc: Simon Glass
> Cc: Joe Hershberger
> Cc: Peng Fan
> Cc: Stefano Babic
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
Acked-by: Joe Hershberger
On Thu, Oct 6, 2016 at 2:14 AM, Tom Rini wrote:
> On Wed, Sep 14, 2016 at 03:49:22AM +, Peter Chubb wrote:
>
>> After any operation that downloads a file (e.g., pxe get, or dhcp), the
>> buffer containing the downloaded data is flushed. This is unnecessary
>> and annoying. Unnecessary, becau
On Thu, Oct 6, 2016 at 12:55 PM, Jagan Teki wrote:
> From: Jagan Teki
>
> Use CONFIG_DM_ETH and remove board_eth_init code
> from board files.
>
> Cc: Joe Hershberger
> Cc: Peng Fan
> Cc: Stefano Babic
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
Your SoB line should be first.
Acked
On Thu, Oct 6, 2016 at 12:55 PM, Jagan Teki wrote:
> From: Jagan Teki
>
> This patch add driver model support for fec_mxc driver.
>
> Cc: Simon Glass
> Cc: Joe Hershberger
> Cc: Peng Fan
> Cc: Stefano Babic
> Cc: Michael Trimarchi
> Signed-off-by: Jagan Teki
> ---
> drivers/net/fec_mxc.c |
Hi Tom,
This is mostly syncing up with upstream. I have a few more things to do
also (some small, some large).
The following changes since commit f5fd45ff64e28a73499548358e3d1ceda0de7daf:
Merge branch 'master' of git://www.denx.de/git/u-boot-imx (2016-10-08
09:33:37 -0400)
are available in t
On Mon, Oct 10, 2016 at 2:57 PM, Mugunthan V N wrote:
> cpsw driver supports only selection of phy mode in control module
> but control module has more setting like RGMII ID mode selection,
> RMII clock source selection. So ported to cpsw-phy-sel driver
> from kernel to u-boot.
>
> Signed-off-by:
On Mon, Oct 10, 2016 at 2:57 PM, Mugunthan V N wrote:
> In AM335x GP EVM, Atheros 8031 phy is used, enable the driver as
> AM335x SoC RGMII delay mode has to be enabled in phy as mentioned
> in the silicon errata Advisory 1.0.10
>
> Signed-off-by: Mugunthan V N
Acked-by: Joe Hershberger
___
On Mon, Oct 10, 2016 at 2:57 PM, Mugunthan V N wrote:
> In the current driver implementation, config() callback is common
> for AR8035 and AR8031 phy. In config() callback, driver tries to
> configure MMD Access Control Register and MMD Access Address Data
> Register unconditionally for both phy v
Okay, but I could use a little clarity; do you want the u-boot dts to
look just like my (proposed) kernel dts? Or do I start with kernel
dts and remove the gmac/axp209 stuff?
If we can merge all of this feedback into a single list of changes,
then I can take a whack at it later this week (after a
On Tue, Oct 11, 2016 at 11:09 AM, Diego Dorta wrote:
> Allow i.MX6Q Sabre SD to load the kernel and dtb via SPL in Falcon mode.
>
> Based on the Falcon mode code for MX6 Gateworks Ventana board.
>
> Signed-off-by: Diego Dorta
> ---
> board/freescale/mx6sabresd/mx6sabresd.c | 12
> i
On Tue, Oct 11, 2016 at 11:09 AM, Diego Dorta wrote:
> Add a README to explain the steps for booting mx6sabresd in different ways:
> 1. Booting via Normal U-Boot (u-boot.imx)
> 2. Booting via SPL (SPL and u-boot.img)
> 3. Booting via Falcon mode (SPL launches the kernel directly)
>
> S
Add a README to explain the steps for booting mx6sabresd in different ways:
1. Booting via Normal U-Boot (u-boot.imx)
2. Booting via SPL (SPL and u-boot.img)
3. Booting via Falcon mode (SPL launches the kernel directly)
Signed-off-by: Diego Dorta
---
board/freescale/mx6sabresd/README
Current logic for query of revision, board_name, config returns
NULL. Users of these functions do a direct strncmp to compare.
Unfortunately, as per conventions require two valid strings to compare
against and the current implementation causes a crash when compared
with NULL.
We'd still like to ma
config should have been initialized along with others as defaults.
Signed-off-by: Nishanth Menon
---
board/ti/common/board_detect.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/board/ti/common/board_detect.c b/board/ti/common/board_detect.c
index 7c552d20656a..13aac2f03037 100644
--- a/
We should have used TI_DEAD_EEPROM_MAGIC in the first place.
Fixes: d3b98a9eb941 ("ti: common: dra7: Add standard access for board
description EEPROM")
Signed-off-by: Nishanth Menon
---
board/ti/common/board_detect.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/board/ti/c
In some cases where eeprom has not been programmed, Brad reported
issues of crash at strcmp against NULL, this series was triggered
thanks to issue in manufacturing flow where the mandatory eeprom
programming was missed.
Nishanth Menon (3):
ti: common: board_detect: Replace hardcoded value with
Hi Tom,
This includes lp873x PMIC support, moving patman to work with Python 3
(mostly), buildman improvements, cros_ec flashinfo support and sandbox
filesystem test fixes. It also includes the MMC patches I've been
holding off for months. I still worry that it might cause problems
with some board
Allow i.MX6Q Sabre SD to load the kernel and dtb via SPL in Falcon mode.
Based on the Falcon mode code for MX6 Gateworks Ventana board.
Signed-off-by: Diego Dorta
---
board/freescale/mx6sabresd/mx6sabresd.c | 12
include/configs/mx6sabresd.h| 12
2 files ch
On Tue, Oct 11, 2016 at 11:09 AM, Diego Dorta wrote:
> Add a README to explain the steps for booting mx6sabresd in different ways:
> 1. Booting via Normal U-Boot (u-boot.imx)
> 2. Booting via SPL (SPL and u-boot.img)
> 3. Booting via Falcon mode (SPL launches the kernel directly)
>
> S
On Tue, Oct 11, 2016 at 11:09 AM, Diego Dorta wrote:
> Allow i.MX6Q Sabre SD to load the kernel and dtb via SPL in Falcon mode.
>
> Based on the Falcon mode code for MX6 Gateworks Ventana board.
>
> Signed-off-by: Diego Dorta
Reviewed-by: Fabio Estevam
__
Hi Bin,
Thanks for your suggestion.
Please see my comments inline.
Thanks,
Minghuan
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Monday, October 10, 2016 7:49 PM
> To: M.H. Lian ; Simon Glass
> Cc: U-Boot Mailing List ; Mingkai Hu
> ; Leo Li
> Subject: Re:
Hi Bin,
Please see my comments inline.
Thanks,
Minghuan
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Tuesday, October 11, 2016 3:43 PM
> To: M.H. Lian
> Cc: Simon Glass ; U-Boot Mailing List b...@lists.denx.de>; Mingkai Hu ; Leo Li
>
> Subject: Re: [U-Boot
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Tuesday, October 11, 2016 11:44 AM
> To: Ding, ChiX
> Cc: Simon Glass ; u-boot@lists.denx.de
> Subject: Re: [U-Boot] build error with CONFIG_DM_PCI disabled in menuconfig
>
> Hi Chi,
>
> On Tue, Oct 11, 2016 at 6:
Hi Bin,
I noticed Sandbox architecture has added PCI menu to the arch/sandbox/Kconfig
Could I move this PCI menu to the driver/pci/kconfig?
So I could add all PCI related config to defconfig files.
Please see my comments inline.
Thanks,
Minghuan
> -Original Message-
> From: Bin Meng [m
Hi Bin,
Please see my comments inline.
Thanks,
Minghuan
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Monday, October 10, 2016 7:55 PM
> To: M.H. Lian ; Simon Glass
> Cc: U-Boot Mailing List ; Mingkai Hu
> ; Leo Li
> Subject: Re: [U-Boot] [PATCH 2/9] dm: pci
Hi Chi,
On Tue, Oct 11, 2016 at 6:01 PM, Ding, ChiX wrote:
> Hi Bin
> Thanks for the reply. I'm working on Intel Denvernton Board. As you
> suggested I'm debugging it
> using DM PCI now. In the device tree file, I define PCI as this, but I don't
> know what is missing so
> that AHCI isn't prob
Hi Minghuan,
On Tue, Oct 11, 2016 at 5:36 PM, M.H. Lian wrote:
> Hi Bin,
>
> Please see my comments inline.
>
> Thanks,
> Minghuan
>
>> -Original Message-
>> From: Bin Meng [mailto:bmeng...@gmail.com]
>> Sent: Tuesday, October 11, 2016 3:43 PM
>> To: M.H. Lian
>> Cc: Simon Glass ; U-Boot
Hi Bin
Thanks for the reply. I'm working on Intel Denvernton Board. As you suggested
I'm debugging it
using DM PCI now. In the device tree file, I define PCI as this, but I don't
know what is missing so
that AHCI isn't probed
pci {
compatible = "pci-x86";
Hi Bin,
Please see my comment inline.
Thanks,
Minghuan
> -Original Message-
> From: Bin Meng [mailto:bmeng...@gmail.com]
> Sent: Monday, October 10, 2016 7:42 PM
> To: M.H. Lian
> Cc: U-Boot Mailing List ; Mingkai Hu
> ; Leo Li
> Subject: Re: [U-Boot] [PATCH 9/9] armv8: ls1046a: Enable
Hi,
On 10/11/2016 10:44 AM, Stefan Mavrodiev wrote:
Originally dram clock was set to 480MHz, but this behaves
unstable. To improve stability the clock is reduced to 384MHz
Signed-off-by: Stefan Mavrodiev
The exact same change is already in u-boot-sunxi/next, and I've already
send out a pullr
Hi Bin,
With the patches our Layerscape PCIe driver has been fully based on DM.
Ethernet driver E1000 needs to define "CONFIG_DM_ETH" to use PCIe DM API
instead of legacy PCI API.
But our other Ethernet driver FM(drivers/net/fm/eth.c) is still not support DM.
So we cannot define "CONFIG_DM_ETH"
Hi Minghuan,
On Tue, Oct 11, 2016 at 3:12 PM, M.H. Lian wrote:
> Hi Bin,
>
> With the patches our Layerscape PCIe driver has been fully based on DM.
> Ethernet driver E1000 needs to define "CONFIG_DM_ETH" to use PCIe DM API
> instead of legacy PCI API.
> But our other Ethernet driver FM(drivers/
From: Yuan Yao
Signed-off-by: Yuan Yao
---
board/freescale/ls2080aqds/README | 35 +++
1 file changed, 35 insertions(+)
diff --git a/board/freescale/ls2080aqds/README
b/board/freescale/ls2080aqds/README
index f288750..0f7446a 100644
--- a/board/freescale/ls2080
Hi Minghuan,
On Tue, Oct 11, 2016 at 3:21 PM, M.H. Lian wrote:
> Hi Bin,
>
> Thanks for your suggestion.
> Please see my comments inline.
>
> Thanks,
> Minghuan
>
>> -Original Message-
>> From: Bin Meng [mailto:bmeng...@gmail.com]
>> Sent: Monday, October 10, 2016 7:49 PM
>> To: M.H. Lian
In device tree, there is vmmc-supply property for SD/MMC.
Introduce mmc_power_init function to handle vmmc-supply.
mmc_power_init will first invoke board_mmc_power_init to
avoid break boards which already implement board_mmc_power_init.
If DM_MMC and DM_REGULATOR is defined, the regulator
will be
88 matches
Mail list logo
