Hi Simon,
Sorry for late answer.
> -Original Message-
> From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
> Sent: 2017年7月5日 3:33
> To: Wenyou Yang - A41535
> Cc: U-Boot Mailing List ; Jaehoon Chung
> ; Wenyou Yang - A41535
> ; Andreas Bießmann ;
> Tom Rini ; Stephen
On 3.7.2017 13:41, Alexander Graf wrote:
> I got myself an amazing new toy: A MYIR Z-Turn board.
>
> Since the only sane way to boot distributions on such a device is obviously
> U-Boot with grub and openSUSE, I stumbled over a few shortcomings in the
> current
> upstream state of affairs.
>
> T
On Mon, Jul 10, 2017 at 4:24 PM, Fabio Estevam wrote:
> On Mon, Jul 10, 2017 at 6:14 PM, Robert Nelson
> wrote:
>
>> How do you guys want to do the revd1'?
>>
>> imx6<>-wandboard-revd1.dtb ?
>>
>> https://github.com/wandboard-org/linux/commit/e093a1186879eef78d91f22f1e47089565bde8e9
>
> Looking
Am 09.07.2017 um 22:52 schrieb Simon Glass:
> This converts the following to Kconfig:
>CONFIG_ENV_IS_IN_FLASH
>
> Signed-off-by: Simon Glass
> ---
>
...
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 579371e8ee..3046d90b4d 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/
On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> Currently the rootfs location is passed via mmcblk number and the
> problem with this approach is that the mmcblk number for the eMMC
> changes depending on the kernel version.
>
> In order to avoid such issue, use U
On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> Currently the rootfs location is passed via mmcblk number and the
> problem with this approach is that the mmcblk number for the eMMC
> changes depending on the kernel version.
>
> In order to avoid such issue, use U
On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> Currently the rootfs location is passed via mmcblk number and the
> problem with this approach is that the mmcblk number for the eMMC
> changes depending on the kernel version.
>
> In order to avoid such issue, use U
On Mon, Jul 10, 2017 at 6:14 PM, Robert Nelson wrote:
> How do you guys want to do the revd1'?
>
> imx6<>-wandboard-revd1.dtb ?
>
> https://github.com/wandboard-org/linux/commit/e093a1186879eef78d91f22f1e47089565bde8e9
Looking at this dts it seems we only need to add a imx6qp variant.
The other
On Mon, Jul 10, 2017 at 3:30 PM, Otavio Salvador
wrote:
> On Mon, Jul 10, 2017 at 5:14 PM, Fabio Estevam wrote:
>> On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
>> wrote:
>>> From: Fabio Berton
>>>
>>> New kernel linux-wandboard version 4.1.15_1.1.0_ga changed device tree
>>> name adding boa
From: Suji Velupillai
move to Kconfig:
CONFIG_BCM_SF2_ETH
CONFIG_BCM_SF2_ETH_DEFAULT_PORT
CONFIG_BCM_SF2_ETH_GMAC
Also modified defconfigs of all platforms that use these configs.
Signed-off-by: Suji Velupillai
Tested-by: Suji Velupillai
Reviewed-by: JD Zheng
Reviewed
It is annoying to have to set up and maintain two sets of toolchains, one
for buildman and one for moveconfig.
Adjust moveconfig to make use to buildman's toolchains. This should make
things easier.
One missing feature is the ability to specify the toolchain on the command
line with a special env
Add an option to specify 'all' to enable all flags. Also print an error
if an unrecognised flag is used. At present it just prints usage
information which is not very helpful.
Signed-off-by: Simon Glass
---
tools/moveconfig.py | 23 +++
1 file changed, 15 insertions(+), 8 de
On Mon, Jul 10, 2017 at 5:14 PM, Fabio Estevam wrote:
> On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
> wrote:
>> From: Fabio Berton
>>
>> New kernel linux-wandboard version 4.1.15_1.1.0_ga changed device tree
>> name adding board revision on file name. The new names are:
>>
>> - imx6dl-wand
On Mon, Jul 10, 2017 at 5:04 PM, Otavio Salvador
wrote:
> From: Fabio Berton
>
> New kernel linux-wandboard version 4.1.15_1.1.0_ga changed device tree
> name adding board revision on file name. The new names are:
>
> - imx6dl-wandboard-revb1
> - imx6dl-wandboard-revc1
> - imx6q-wandboard-revb
From: Fabio Berton
Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.
In order to avoid such issue, use UUID method to specify the rootfs
location.
Also add CONFIG_BOOTCOMMA
From: Fabio Berton
Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.
In order to avoid such issue, use UUID method to specify the rootfs
location.
This change was made base
From: Fabio Berton
New kernel linux-wandboard version 4.1.15_1.1.0_ga changed device tree
name adding board revision on file name. The new names are:
- imx6dl-wandboard-revb1
- imx6dl-wandboard-revc1
- imx6q-wandboard-revb1
- imx6q-wandboard-revc1
This fixes the Wandboard C1 revision device
From: Fabio Berton
Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.
In order to avoid such issue, use UUID method to specify the rootfs
location.
This change was made base
On 07/10/2017 02:45 PM, Andrew F. Davis wrote:
> Hello all,
>
> This series brings our firewall and OP-TEE support from DRA7xx/AM57xx
> family devices to the AM43xx class devices. We do this by factoring
> out code common code from omap5/ into common mach-omap2/ sources. Then
> add the hooks for t
Hello all,
This series brings our firewall and OP-TEE support from DRA7xx/AM57xx
family devices to the AM43xx class devices. We do this by factoring
out code common code from omap5/ into common mach-omap2/ sources. Then
add the hooks for the AM43xx boards.
Thanks,
Andrew
Changes from v1:
- Stop
TEE loading and firewall setup are common to all omap2 devices, move
these function out of omap5 and into mach-omap2. This allows us
to use these functions from other omap class devices.
Signed-off-by: Andrew F. Davis
---
arch/arm/mach-omap2/Kconfig | 26
arch/arm/mach-omap2/omap5
On 06/17/2017 02:35 AM, Lokesh Vutla wrote:
>
>
> On Saturday 17 June 2017 12:57 AM, Andrew F. Davis wrote:
>> Add support for loading a TEE and setting up firewalled regions to
>> AM43xx HS boards.
>>
>> Signed-off-by: Andrew F. Davis
>> ---
>> board/ti/am43xx/board.c | 7 +++
>> c
Disable RNG and add TEE to FDT used on HS devices.
Signed-off-by: Andrew F. Davis
---
board/ti/am43xx/board.c | 9 +
configs/am43xx_hs_evm_defconfig | 1 +
2 files changed, 10 insertions(+)
diff --git a/board/ti/am43xx/board.c b/board/ti/am43xx/board.c
index 96032215a6..933596d5
Some of the fixups currently done for OMAP5 class boards are common to
other OMAP family devices, move these to fdt-common.c.
Signed-off-by: Andrew F. Davis
---
arch/arm/include/asm/omap_common.h | 5 ++
arch/arm/include/asm/omap_sec_common.h | 6 ++
arch/arm/mach-omap2/Makefile
If a firmware node is already present in the FDT we will fail to create
one and so fail to add our OP-TEE node, make this fixup first check for
a firmware node and then only try to add one if it is not found.
Signed-off-by: Andrew F. Davis
---
arch/arm/mach-omap2/fdt-common.c | 20 ++
Add support for loading a TEE and setting up firewalled regions to
AM43xx HS boards.
Signed-off-by: Andrew F. Davis
---
board/ti/am43xx/board.c | 7 +++
configs/am43xx_hs_evm_defconfig | 3 +++
2 files changed, 10 insertions(+)
diff --git a/board/ti/am43xx/board.c b/board/ti/am43xx/
Similar to what is done with OMAP5 class boards we need to
perform fixups common to this SoC class, add support for this here
and add HS fixups.
Signed-off-by: Andrew F. Davis
---
arch/arm/mach-omap2/am33xx/Makefile | 1 +
arch/arm/mach-omap2/am33xx/fdt.c| 43 +++
On Fri, Jul 07, 2017 at 05:00:50PM +0200, Jean-Jacques Hiblot wrote:
>
>
> On 07/07/2017 16:30, Tom Rini wrote:
> >On Fri, Jul 07, 2017 at 01:44:39PM +0200, Jean-Jacques Hiblot wrote:
> >
> >>u-boot can be embedded within a FIT image with multiple DTBs. It then
> >>selects at run-time which one
From: Fabio Estevam
mx6sabre boards can run different kernel versions, such as NXP 4.1 or
mainline.
Currently the rootfs location is passed via mmcblk number and the
problem with this approach is that the mmcblk number for the eMMC
changes depending on the kernel version.
In order to avoid such
From: Fabio Estevam
WEIM cannot be used when I2C3 is enabled due to pin conflict, so keep
WEIM disabled by default.
I2C3 controls GPIO I2C expander (USB host and OTG have VBUS controlled by
the GPIO I2C expander), magnetometer, accelerometer.
Not disabling WEIM in U-Boot causes I2C3 to behave b
Thanks Simon,
> -Original Message-
> From: Simon Glass [mailto:s...@google.com] On Behalf Of Simon Glass
> Sent: Saturday, July 01, 2017 10:06 AM
> To: U-Boot Mailing List
> Cc: Simon Glass ; Albert Aribaud
> ; Toshifumi NISHINAGA
> ; Vikas MANOCHA
> Subject: [PATCH] stm32: Correct posi
Hey all,
I've released v2017.07 and it's now live on git and FTP and ACD (along
with PGP sig file).
With this release we've removed a number of PowerPC architectures due to
lack of active support. We've also dropped AVR32 support with this
release. Of note here, we have a new and active PowerPC
On Mon, Jul 10, 2017 at 09:46:23AM +0200, Holger Brunck wrote:
> Cc: Wolfgang Denk
> Cc: Heiko Schocher
> Signed-off-by: Holger Brunck
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: Digital signature
___
U-Boot mailing list
U
On Mon, Jul 10, 2017 at 08:44:24AM +0200, Lothar Waßmann wrote:
> If the value of either "nand options" or "bbt options" has a zero in
> the most significant nibble, the '0x' prefix will be isolated from the
> value like shown below:
> |Device 0: nand0, sector size 128 KiB
> | Page size 204
On Sun, Jul 09, 2017 at 09:30:17PM -0600, Simon Glass wrote:
> This error code has not been upstreamed and is not really needed since it
> is unlikely to be triggered. Drop it to maintain compatability with
> upstream.
>
> Reported-by: Peter Robinson
>
> Signed-off-by: Simon Glass
> Tested-by:
On 10 July 2017 at 02:26, Peter Robinson wrote:
> On Mon, Jul 10, 2017 at 4:31 AM, Simon Glass wrote:
>> Hi Tom,
>>
>> On 9 July 2017 at 16:36, Tom Rini wrote:
>>> On Sun, Jul 09, 2017 at 12:38:19PM -0600, Simon Glass wrote:
Hi,
On 9 July 2017 at 06:49, Tom Rini wrote:
> On
Hi Oliver,
On 10 July 2017 at 07:54, Oliver Westermann wrote:
> Hello,
>
> I've got multiple ARM boards with similar but not quite the same
> configurations.
> For example different IO configurations for peripheral reset lines of
> hardware used in the u-boot phase.
>
> Currently I have multiple
Hi Christophe,
On 10 July 2017 at 02:10, Christophe LEROY wrote:
> Simon,
>
> Le 09/07/2017 à 22:52, Simon Glass a écrit :
>>
>> The environment code is ripe for improvement in various ways. It has lots
>> of duplication and inconsistencies between how things work with different
>> environment lo
On 07/07/2017 10:00 AM, Jean-Jacques Hiblot wrote:
>
>
> On 07/07/2017 16:30, Tom Rini wrote:
>> On Fri, Jul 07, 2017 at 01:44:39PM +0200, Jean-Jacques Hiblot wrote:
>>
>>> u-boot can be embedded within a FIT image with multiple DTBs. It then
>>> selects at run-time which one is best suited fo
This patch adds support of non-jedec MRAM devices mr25hx from Everspin.
This flash devices do not have jedec device ID and hence support for
name matching is also added as part of this series.
This patch streamlined the update of SPI flash probing function API
changes and included the following up
Hi Marek,
On Thu, Jun 22, 2017 at 3:13 PM, Bin Meng wrote:
> Currently U-Boot xHCI driver does not work on Intel BayTrail SoC based
> boards that have USB 3.0 ports. Trying to do a 'usb start' simply hangs
> the board. This series fixes a bunch of xHCI driver issues to make it
> work on Intel's p
On Mon, Jul 10, 2017 at 2:54 PM, Oliver Westermann
wrote:
> Hello,
>
> I've got multiple ARM boards with similar but not quite the same
> configurations.
> For example different IO configurations for peripheral reset lines of
> hardware used in the u-boot phase.
>
> Currently I have multiple u-Boo
Hello,
I've got multiple ARM boards with similar but not quite the same
configurations.
For example different IO configurations for peripheral reset lines of
hardware used in the u-boot phase.
Currently I have multiple u-Boot configurations using multiple .dts files
creating multiple u-boot.img a
Ping,
any reason this hasn't been merged yet? :)
Olliver
On 12-05-17 18:52, Maxime Ripard wrote:
On Fri, May 12, 2017 at 11:38:52AM +0200, Olliver Schinagl wrote:
This patch series adds support for the Olimex OLinuXino Lime2 eMMC. This
assembly variant uses eMMC flash instead of NAND (or no f
On 7/8/2017 8:50 AM, Sergey Manucharian wrote:
> (sorry for top posting, sending from a phone)
>
> I would agree it's intentional at the first stage: we don't want to power
> external devices which we may not need, however, the "usb start" command must
> enable it, otherwise it's useless...
R
On Mon, Jul 10, 2017 at 4:30 AM, Simon Glass wrote:
> This error code has not been upstreamed and is not really needed since it
> is unlikely to be triggered. Drop it to maintain compatability with
> upstream.
>
> Reported-by: Peter Robinson
Tested-by: Peter Robinson
> Signed-off-by: Simon Glass
On Sun, Jul 09, 2017 at 05:06:17AM +0200, BOULAMAIL Nihad wrote:
> Hello,
>
> I wishb to run this RTOS: https://github.com/trampolinertos/trampoline, on
> Zedboard having these files on SD card.
>
> SD_ROOT/
> boot.bin
> devicetree.dtb
> uImage
> uramdisk.image.gz
>
> How can I build u-boot
Hi,
On Mon, 10 Jul 2017 11:39:22 +0200 patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> This allow to check if a PHY has been correctly
> initialised and avoid to get access to phy struct.
>
> Signed-off-by: Patrice Chotard
> Reviewed-by: Marek Vasut
> Reviewed-by: Simon Glass
> ---
On Mon, Jul 10, 2017 at 5:39 PM, wrote:
> From: Patrice Chotard
>
> Add Driver Model support with use of generic DT
> compatible string "snps,dwc3"
>
> Signed-off-by: Patrice Chotard
> ---
>
> v6: _ remove useless struct xhci_dwc3
> v5: _ replace dev_get_addr() by devfdt_get_addr()
> v4
From: Patrice Chotard
Add Driver Model support with use of generic DT
compatible string "snps,dwc3"
Signed-off-by: Patrice Chotard
---
v6: _ remove useless struct xhci_dwc3
v5: _ replace dev_get_addr() by devfdt_get_addr()
v4: _ none
v3: _ none
v2: _ use dev_get_addr() and
From: Patrice Chotard
Add support of generic PHY framework support
Signed-off-by: Patrice Chotard
Reviewed-by: Marek Vasut
Reviewed-by: Simon Glass
---
v6: _ none
v5: _ none
v4: _ none
v3: _ use generic_phy_valid() method
v2: _ none
drivers/usb/host/xhci-dwc3.c | 32 +
From: Patrice Chotard
DWC3 dual role mode is selected using DT "dr_mode"
property. If not found, DWC3 controller is configured
in HOST mode by default
Signed-off-by: Patrice Chotard
Reviewed-by: Marek Vasut
Reviewed-by: Simon Glass
---
Reviewed-by: Marek Vasut
Reviewed-by: Simon Glass
---
From: Patrice Chotard
phy->dev need to be set to NULL in case of generic_phy_get_by_index()
fails. Then phy->dev can be used to check if the phy is valid
Reported-by: Jean-Jacques Hiblot
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass
Reviewed-by: Jean-Jacques Hiblot
---
v6: _ no
From: Patrice Chotard
This allow to check if a PHY has been correctly
initialised and avoid to get access to phy struct.
Signed-off-by: Patrice Chotard
Reviewed-by: Marek Vasut
Reviewed-by: Simon Glass
---
v6: _ none
v5: _ none
v4: _ none
drivers/phy/phy-uclass.c | 5 +
in
From: Patrice Chotard
This series extend xhci-dwc3.c drivers by :
_ converting it to DM model,
_ adding dual role mode support from DT
_ adding new generic_phy_valid() method in PHY framework
_ adding support of generic PHY framework
v6: _ remove useless struc
Hi Alan,
On 07/09/2017 04:58 AM, Alan Ott wrote:
> Previously this driver appeared to have been half-way converted to the new
> driver model and did not work at all.
>
> Complete the transition to the driver model, adding the necessary
> connections.
Thanks for resending v2. This patch will pick
On Mon, Jul 10, 2017 at 4:31 AM, Simon Glass wrote:
> Hi Tom,
>
> On 9 July 2017 at 16:36, Tom Rini wrote:
>> On Sun, Jul 09, 2017 at 12:38:19PM -0600, Simon Glass wrote:
>>> Hi,
>>>
>>> On 9 July 2017 at 06:49, Tom Rini wrote:
>>> > On Sun, Jul 09, 2017 at 10:45:52AM +0100, Peter Robinson wrote
Simon,
Le 09/07/2017 à 22:52, Simon Glass a écrit :
The environment code is ripe for improvement in various ways. It has lots
of duplication and inconsistencies between how things work with different
environment locations. It does not properly use Kconfig. Error checking
and handling is patchy.
Cc: Wolfgang Denk
Cc: Heiko Schocher
Signed-off-by: Holger Brunck
---
board/keymile/common/common.h | 9 -
1 file changed, 9 deletions(-)
diff --git a/board/keymile/common/common.h b/board/keymile/common/common.h
index c74f569a61..81a0af0c3c 100644
--- a/board/keymile/common/common.h
+
On 29.6.2017 19:38, Moritz Fischer wrote:
> Hi Michal,
>
> can you / did you send this to the kernel ML, too?
We need to send fpga manager driver first but yes we will do it.
>
> On Thu, Jun 29, 2017 at 3:14 AM, Michal Simek wrote:
>> This will simplify dt overlay structure for the whole PL.
>
G'day Joe,
On 8/07/2017 03:46, Joe Hermaszewski wrote:
The uboot binary generated with `make socfpga_arria10_config` is too large
for Intel's `mkpimage` tool to consume.
u-boot.bin weighs in at 242508 bytes.
The maximum binary size supported by the `mkpimage` tool (distributed with
Intel's SoC
61 matches
Mail list logo
