2018-04-12 7:02 GMT+02:00 Bin Meng :
> At present two environment variables 'e820data'/'e820info' are required
> to boot a VxWorks x86 kernel, but this is superfluous. The offset of
> these two tables are actually at a fixed offset from the kernel memory
> base address and we can provide the kernel
2018-04-12 7:02 GMT+02:00 Bin Meng :
> This changes 'struct e820info' to 'struct e820_info' to conform
> with the coding style.
>
> Signed-off-by: Bin Meng
Reviewed-by: Christian Gmeiner
> ---
>
> Changes in v2: None
>
> cmd/elf.c | 6 +++---
> include/vxworks.h | 2 +-
> 2 files chang
2018-04-12 7:02 GMT+02:00 Bin Meng :
> This fixes the following checkpatch warning:
>
> warning: Prefer 'unsigned int' to bare use of 'unsigned'
>
> Signed-off-by: Bin Meng
Reviewed-by: Christian Gmeiner
> ---
>
> Changes in v2: None
>
> arch/x86/cpu/coreboot/sdram.c | 7 ---
> arch/x86/
2018-04-12 7:02 GMT+02:00 Bin Meng :
> This changes 'struct e820entry' to 'struct e820_entry' to conform
> with the coding style.
>
> Signed-off-by: Bin Meng
Reviewed-by: Christian Gmeiner
> ---
>
> Changes in v2: None
>
> arch/x86/cpu/coreboot/sdram.c| 2 +-
> arch/x86/cpu/qemu/e820.c
2018-04-12 7:02 GMT+02:00 Bin Meng :
> Fix various style violations in elf.h
> - use correct comment format if the comment fits in just one line
> - remove the ending period for the one-line comment
> - use tab for the indention instead of space
> - put the opening brace at the same line of a typed
We enabled CONFIG_ISO_PARTITION by default for distro boot, so that U-Boot
could load distro images that usually get shipped as iso images. These images
usually come with a board agnostic boot environment.
However, there is very little point in having ISO support enabled (for anyone
really) in SPL
On 11.04.18 16:43, Dinh Nguyen wrote:
> On Wed, Apr 11, 2018 at 7:55 AM, Alexander Graf wrote:
>> On 04/11/2018 02:37 PM, Marek Vasut wrote:
>>>
>>> On 04/11/2018 02:26 PM, Tom Rini wrote:
On Wed, Apr 11, 2018 at 10:12:42AM +0200, Marek Vasut wrote:
>
> On 04/11/2018 04:52 AM,
In the commit "reset: Add get/assert/deassert/release for bulk of reset signals"
the disabled reset_release_bulk() and reset_get_bulk() used the wrong
struct clk_bulk instead of struct reset_ctl_bulk.
Fixes: 0c28233903b5 ("reset: Add get/assert/deassert/release for bulk of reset
signals")
Reporte
Hi Jean-Jacques,
On 11/04/2018 18:17, Jean-Jacques Hiblot wrote:
>
>
> On 11/04/2018 17:08, Neil Armstrong wrote:
>> This is a port of the dwc3-of-simple driver from Linux to enable/deassert
>> clock and resets of a simple DWC3 Controller HW glue.
>>
>> Signed-off-by: Neil Armstrong
>> ---
>>
On 12/04/18 09:05, Neil Armstrong wrote:
Hi Jean-Jacques,
On 11/04/2018 18:17, Jean-Jacques Hiblot wrote:
On 11/04/2018 17:08, Neil Armstrong wrote:
This is a port of the dwc3-of-simple driver from Linux to enable/deassert
clock and resets of a simple DWC3 Controller HW glue.
Signed-off-by:
Fixes performance related issue when running vxWorks 5/7 images.
The overall memory performance (L1, L2 cache and ram) was measured
with Bandwidth [0].
Without this patch we get following numbers:
- sequential 128-bit reads: ~5.2 GB/s
- sequential 128-bit copy: ~2.1 GB/s
- random 32-bit writ
Signed-off-by: Christian Gmeiner
---
arch/x86/dts/crownbay.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/dts/crownbay.dts b/arch/x86/dts/crownbay.dts
index 78a1ef415c..bb39a895f6 100644
--- a/arch/x86/dts/crownbay.dts
+++ b/arch/x86/dts/crownbay.dts
@@ -32,1
On 12/04/2018 10:07, Ben Dooks wrote:
> On 12/04/18 09:05, Neil Armstrong wrote:
>> Hi Jean-Jacques,
>>
>> On 11/04/2018 18:17, Jean-Jacques Hiblot wrote:
>>>
>>>
>>> On 11/04/2018 17:08, Neil Armstrong wrote:
This is a port of the dwc3-of-simple driver from Linux to enable/deassert
clock
The disabled clk API returns -ENOSYS unlike the reset API returning -ENOTSUPP.
Fixes: ca7fdc8b1267 ("usb: host: Add simple of glue driver for DWC3 USB
Controllers integration")
Reported-by: Jean-Jacques Hiblot
Signed-off-by: Neil Armstrong
---
drivers/usb/host/dwc3-of-simple.c | 2 +-
1 file c
Le 11/04/2018 à 18:06, Fabio Estevam a écrit :
On Wed, Apr 11, 2018 at 12:52 PM, Guillaume Gardet
wrote:
So, how to handle dtb filenames? Update with wrong soc definition ? Or drop
this patch and define a FDTFILE for each flavor?
You can take a look at how we handle this for wandboard, cubo
On 11/04/2018 17:49, Jean-Jacques Hiblot wrote:
> Hi Neil,
>
> while trying to test your patches on dwc3, I ran into a compilation issue.
>
> On 03/04/2018 11:40, Neil Armstrong wrote:
>> This patch adds a "bulk" API to the reset API in order to get/deassert/
>> assert/release a group of reset si
On 12.04.2018 06:37, sdrb wrote:
Hi Marcin,
Marcin Niestroj wrote:
Hi Witold,
On 11.04.2018 08:18, sdrb wrote:
Hi,
I use Grinn's chiliSOM and very old U-boot 2014.07 on it.
Unfortunately the newest u-boot doesn't run SPL properly - so I'm
forced to use 2014.07 version.
What are your pr
This simple glue layer does not require CONFIG_MISC, but it does require
CONFIG_DM_USB.
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/usb/host/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/ho
Add the compatibility with "ti,dwc3" and enable it by default if DM_USB
is enabled.
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/usb/host/Kconfig | 1 +
drivers/usb/host/dwc3-of-simple.c | 1 +
2 files changed, 2 insertions
From: Vignesh R
Add support to handle USB3 PHYs present on AM57xx/DRA7xx SoCs. This is
needed to move AM57xx to DM_USB.
Signed-off-by: Vignesh R
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- Add USB3 support to ti-pipe3-phy driver
drivers/p
From: Vignesh R
Enable USB clocks in late init stage to support ports under DM_USB.
Signed-off-by: Vignesh R
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- am57xx boards: when DM_USB is used, turn on the required USB clocks
board/ti/am57xx/b
On all the EVMs featuring a SOC of the DRA7 family, the USB1 port is used
as a device for DFU. This port is managed by the platform code and must not
be advertised to the DWC3 DM driver.
This will be changed when/if support for the device mode is added to the
dwc3-omap driver.
Signed-off-by: Jean-
syscon_regmap_lookup_by_phandle() can be used to get the regmap of a syscon
device from a reference in the DTS. It operates similarly to the linux
version of the namesake function.
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4:
- Fix word missing in commit log
Changes in v3:
- in syscon
Enable DM_USB for AM57xx based boards.
Signed-off-by: Vignesh R
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4:
- Remove dependency on MISC
Changes in v3: None
Changes in v2:
- Enable DM_USB in am57xx_evm_defconfig. USB3 (super speed) is supported.
configs/am57xx_evm_defconfig | 4 +++
This is required when DM_USB is used, to bind the USB phys.
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- split dts changes in 2 commits: one for binding the children of
ocp2scp@4a08, and one to disable USB1 on all DRA7 EVMs
arch/arm/dt
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4:
- Remove dependency on MISC
- Renamed the commit (DM_USB is already enabled, the only missing option
is for the USB2 phy driver)
Changes in v3: None
Changes in v2: None
configs/dra7xx_evm_defconfig| 1 +
configs/dra7xx_hs_evm_defconf
This drivers supports the USB2 PHY found on omap5 and dra7 SOCs.
Signed-off-by: Jean-Jacques Hiblot
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- omap-usb2-phy: Implement power_on and power_off callbacks
drivers/phy/Kconfig | 8 ++
drivers/phy/Makefile| 1 +
For USB ports that use the Driver Model, turn on the clocks during the
late init stage.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Tom Rini
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
board/ti/dra7xx/evm.c | 19 +++
1 file changed, 19 insertions(+)
di
On 04/12/2018 10:01 AM, Alexander Graf wrote:
>
>
> On 11.04.18 16:43, Dinh Nguyen wrote:
>> On Wed, Apr 11, 2018 at 7:55 AM, Alexander Graf wrote:
>>> On 04/11/2018 02:37 PM, Marek Vasut wrote:
On 04/11/2018 02:26 PM, Tom Rini wrote:
>
> On Wed, Apr 11, 2018 at 10:12:42AM +020
On 04/12/2018 10:41 AM, Jean-Jacques Hiblot wrote:
> This simple glue layer does not require CONFIG_MISC, but it does require
> CONFIG_DM_USB.
>
> Signed-off-by: Jean-Jacques Hiblot
> ---
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> drivers/usb/host/Kconfig | 2 +-
>
On 04/12/2018 10:13 AM, Neil Armstrong wrote:
> The disabled clk API returns -ENOSYS unlike the reset API returning -ENOTSUPP.
>
> Fixes: ca7fdc8b1267 ("usb: host: Add simple of glue driver for DWC3 USB
> Controllers integration")
> Reported-by: Jean-Jacques Hiblot
> Signed-off-by: Neil Armstron
On 04/12/2018 10:41 AM, Jean-Jacques Hiblot wrote:
> Add the compatibility with "ti,dwc3" and enable it by default if DM_USB
> is enabled.
>
> Signed-off-by: Jean-Jacques Hiblot
> ---
>
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
> drivers/usb/host/Kconfig | 1
Marcin Niestrój wrote:
On 12.04.2018 06:37, sdrb wrote:
Hi Marcin,
Marcin Niestroj wrote:
Hi Witold,
On 11.04.2018 08:18, sdrb wrote:
Hi,
I use Grinn's chiliSOM and very old U-boot 2014.07 on it.
Unfortunately the newest u-boot doesn't run SPL properly - so I'm
forced to use 2014.07 ver
> Am 12.04.2018 um 10:37 schrieb Marek Vasut :
>
>> On 04/12/2018 10:01 AM, Alexander Graf wrote:
>>
>>
>>> On 11.04.18 16:43, Dinh Nguyen wrote:
On Wed, Apr 11, 2018 at 7:55 AM, Alexander Graf wrote:
> On 04/11/2018 02:37 PM, Marek Vasut wrote:
>
>> On 04/11/2018 02:26 PM,
On 04/12/2018 11:15 AM, Alexander Graf wrote:
>
>
>> Am 12.04.2018 um 10:37 schrieb Marek Vasut :
>>
>>> On 04/12/2018 10:01 AM, Alexander Graf wrote:
>>>
>>>
On 11.04.18 16:43, Dinh Nguyen wrote:
> On Wed, Apr 11, 2018 at 7:55 AM, Alexander Graf wrote:
>> On 04/11/2018 02:37 PM, Ma
Okay, i see. The change is the replacement of the dependency of ARM64 to
ARM_SMCCC in Kconfig.
If you think it's necessary to issue a v4 and document the changes
properly please let me know and I'll do so.
Michalis
On 04/11/2018 03:36 PM, Simon Glass wrote:
On 9 April 2018 at 09:17, Michali
On 04/12/2018 11:17 AM, Marek Vasut wrote:
On 04/12/2018 11:15 AM, Alexander Graf wrote:
Am 12.04.2018 um 10:37 schrieb Marek Vasut :
On 04/12/2018 10:01 AM, Alexander Graf wrote:
On 11.04.18 16:43, Dinh Nguyen wrote:
On Wed, Apr 11, 2018 at 7:55 AM, Alexander Graf wrote:
On 04/11/2018
On 04/12/2018 11:42 AM, Alexander Graf wrote:
[...]
>>> None of it is enabled in SPL :). The „efi partition“ option is a
>>> misnomer - it really just enables GPT partition table support which
>>> are widely in use with Android for example.
>> I suspect we can disable that, since SoCFPGA boots from
Hi Matt,
(added Joe as network custodian to Cc)
On 27.03.2018 19:18, Matt Pelland wrote:
mvneta already supports setting the MAC address but this was only done
internally when some other part of U-Boot tries to actually use the
interface. This commit exposes this functionality to the ethernet c
From: Siva Durga Prasad Paladugu
Add support to use max-speed property from dt for
determining the supported speed. Use 1000Mbps as
default.
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
drivers/net/zynq_gem.c | 9 +
1 file changed, 9 insertions(+)
diff -
Hi Matt,
On 27.03.2018 19:53, Matt Pelland wrote:
The mv_sdhci driver was not zeroing the sdhci_host structure it
allocates causing random access violations in parts of the mmc core
where the "ops" member pointers are checked and called if not NULL.
Signed-off-by: Matt Pelland
---
drivers/mm
From: Siva Durga Prasad Paladugu
Relocate env drivers if manual relocation is enabled. This
patch fixes the issue of u-boot hang incase if env is
present in any of the flash devices.
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
env/common.c | 1 +
env/e
From: Siva Durga Prasad Paladugu
This patch enables support zc1275 revB board. It has
SD added compared to revA. The same configuration will
work for RevC boards aswell.
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
arch/arm/dts/Makefile |
From: Siva Durga Prasad Paladugu
This patch removes UBI support from defconfig and it can
be enabled from menuconfig as per need.
Signed-off-by: Siva Durga Prasad Paladugu
Signed-off-by: Michal Simek
---
configs/microblaze-generic_defconfig | 4
1 file changed, 4 deletions(-)
diff --gi
Disable NFS/MII because this board has no ethernet enabled.
Signed-off-by: Michal Simek
---
configs/zynq_zc770_xm011_defconfig | 2 ++
configs/zynq_zc770_xm011_x16_defconfig | 2 ++
2 files changed, 4 insertions(+)
diff --git a/configs/zynq_zc770_xm011_defconfig
b/configs/zynq_zc770_xm011
x8 and x16 configurations should be in sync.
Signed-off-by: Michal Simek
---
configs/zynq_zc770_xm011_x16_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/zynq_zc770_xm011_x16_defconfig
b/configs/zynq_zc770_xm011_x16_defconfig
index ae6029a71e7d..756200a9ae
JR3 was getting removed from device tree only if random number generation
was successful. However, if SEC firmware is present,JR3 should be removed
from device tree node irrespective of the random seed generation as
SEC firmware reserves it for it's use. Not removing it in case of random
number gen
On 12.04.2018 11:09, sdrb wrote:
Marcin Niestrój wrote:
>>
Could you describe what is you BOOT[4:0] configuration? And you want to
boot from MMC1, right?
If I read the BOOT[4:0] properly it is: 0011.
I want to boot from SD card.
Please provide these 5 pins (including 4 and 0) configur
On Thu, Apr 12, 2018 at 5:13 AM, Guillaume Gardet
wrote:
script that picks the correct dtb.
>>
> Ok. So, how would you like to proceed?
> Remove the generic mx6 'soc' definition and use a board sepcific 'board_rev'
> (or maybe a static definition if one configuration match a single dtb) to
> defin
Hi Liam,
We already have a patch for IO mode that we just verified internally. We got it
for our tree from NGC guy John Moon. I will be sending that patch soon may be
with v3 which I am planning to send once I got response from Jagan on my v2
queries.
Regards,
Siva
From: Liam Beguin [mailto:l
Hi Jaehoon,
Ping!
Thanks,
Siva
> -Original Message-
> From: Siva Durga Prasad Paladugu
> Sent: Tuesday, April 10, 2018 12:02 PM
> To: Jaehoon Chung ; u-boot@lists.denx.de
> Subject: RE: [PATCH v2 0/7] Add support of SD3.0 UHS modes for ZynqMP
>
> Hi Jaehoon,
>
> I would like to send v3
Marcin Niestroj wrote:
On 12.04.2018 11:09, sdrb wrote:
Marcin Niestrój wrote:
>>
Could you describe what is you BOOT[4:0] configuration? And you want to
boot from MMC1, right?
If I read the BOOT[4:0] properly it is: 0011.
I want to boot from SD card.
Please provide these 5 pins (in
Good day all
I am currently faced with a task of having to run new software on ageing
hardware. We have currently about 1000 units in the field of a machine that
runs Windows CE using the Samsung S3C6410.
Because these are considerable assets its not a simple case of replacing
them with new, more
Supporting DM USB is required to support DM_ETH and USB network adapters
with the same binary.
This series adds support for DM_USB for the DRA7/AM57 families. As a bonus
it adds support for USB3.
This series applies on the usb tree with the following fixes:
-[PATCH] reset: fix bulk API when DM_RES
On 04/12/2018 10:41 AM, Jean-Jacques Hiblot wrote:
> Supporting DM USB is required to support DM_ETH and USB network adapters
> with the same binary.
> This series adds support for DM_USB for the DRA7/AM57 families. As a bonus
> it adds support for USB3.
>
> This series applies on the usb tree wit
Hi Fabio, Guillaume
On Thu, Apr 12, 2018 at 08:14:51AM -0300, Fabio Estevam wrote:
> On Thu, Apr 12, 2018 at 5:13 AM, Guillaume Gardet
> wrote:
> script that picks the correct dtb.
> >>
> > Ok. So, how would you like to proceed?
> > Remove the generic mx6 'soc' definition and use a board sepcific
Le 12/04/2018 à 14:36, Gary Bisson a écrit :
Hi Fabio, Guillaume
On Thu, Apr 12, 2018 at 08:14:51AM -0300, Fabio Estevam wrote:
On Thu, Apr 12, 2018 at 5:13 AM, Guillaume Gardet
wrote:
script that picks the correct dtb.
Ok. So, how would you like to proceed?
Remove the generic mx6 'soc' def
Hi Siva,
I wasn't able to find it on the Xilinx github. Is it in that tree already?
Thanks,
Liam
On Thu, 12 Apr 2018 at 07:18 Siva Durga Prasad Paladugu
wrote:
> Hi Liam,
>
>
>
> We already have a patch for IO mode that we just verified internally. We
> got it for our tree from NGC guy John Mo
Hi Guillaume,
On Thu, Apr 12, 2018 at 02:48:07PM +0200, Guillaume Gardet wrote:
>
>
> Le 12/04/2018 à 14:36, Gary Bisson a écrit :
> > Hi Fabio, Guillaume
> >
> > On Thu, Apr 12, 2018 at 08:14:51AM -0300, Fabio Estevam wrote:
> > > On Thu, Apr 12, 2018 at 5:13 AM, Guillaume Gardet
> > > wrote:
Hi Jagan,
Maybe you have any comments or remarks about this patch? And if you don't could
you please apply it.
Thanks!
On Tue, 2018-04-10 at 14:40 +0300, Eugeniy Paltsev wrote:
> sst26wf flash series block protection implementation differs
> from other SST series, so add specific implementation
Le 12/04/2018 à 14:58, Gary Bisson a écrit :
Hi Guillaume,
On Thu, Apr 12, 2018 at 02:48:07PM +0200, Guillaume Gardet wrote:
Le 12/04/2018 à 14:36, Gary Bisson a écrit :
Hi Fabio, Guillaume
On Thu, Apr 12, 2018 at 08:14:51AM -0300, Fabio Estevam wrote:
On Thu, Apr 12, 2018 at 5:13 AM, Gui
Dear Sir/Madam,
Hello,
We have developed an i.mx6dl board which is based on "MX6 Dual Lite SABRE AI
CPU2 Card with AVB". I am using version u-boot-2018.01 with SPL.
I am downloading SPL and u-boot.img with USB loader; downloaded kernel and
device tree files and run them in nfs tftp search over
Hi Mehmet,
On Thu, Apr 12, 2018 at 10:17 AM, Mehmet Ali İPİN
wrote:
> Dear Sir/Madam,
>
> Hello,
>
> We have developed an i.mx6dl board which is based on "MX6 Dual Lite SABRE AI
> CPU2 Card with AVB". I am using version u-boot-2018.01 with SPL.
> I am downloading SPL and u-boot.img with USB load
This patch serie updates sabrelite and nitrogen6x boards to use distro boot
support.
Sabrelite has been boot tested with boot.scr script and EFI/Grub2 on mmc0 and
mmc1 slots.
Nitrogen6* boards have been build tested only.
Currently, only the Sabrelite has fdtfile defined.
Signed-off-by: Guillau
Boot tested with boot.scr script and EFI/Grub2 on mmc0 and mmc1 slots on
sabrelite board.
Signed-off-by: Guillaume GARDET
Cc: Troy Kisky
Cc: Stefano Babic
Cc: Fabio Estevam
Cc: Gary Bisson
---
configs/mx6qsabrelite_defconfig | 15 +--
1 file changed, 5 insertions(+), 10 deletio
Boot tested on sabrelite board.
Signed-off-by: Guillaume GARDET
Cc: Troy Kisky
Cc: Stefano Babic
Cc: Fabio Estevam
Cc: Gary Bisson
---
include/configs/nitrogen6x.h | 180 +--
1 file changed, 54 insertions(+), 126 deletions(-)
diff --git a/include/con
Dear Fabio,
Thank you very much. I will check and inform you.
Best regards.
-Original Message-
From: Fabio Estevam [mailto:feste...@gmail.com]
Sent: Thursday, April 12, 2018 4:28 PM
To: Mehmet Ali İPİN
Cc: u-boot@lists.denx.de
Subject: Re: [U-Boot] u-boot 2018 SPI SPL
Hi Mehmet,
On
On 04/12/2018 04:43 AM, Marek Vasut wrote:
> On 04/12/2018 11:42 AM, Alexander Graf wrote:
> [...]
None of it is enabled in SPL :). The „efi partition“ option is a
misnomer - it really just enables GPT partition table support which
are widely in use with Android for example.
>>> I
A good chunk of the booting chain of ZynqMP based systems is open source
(depending on your definition of it), except for the image generation flow.
This patch set aims to change that, with read and write support for boot.bin
partitions which allows us to create boot.bin files using only open sour
The zynqmp image format has support for inline partitions which are
used by FSBL to describe payloads that are loaded by FSBL itself.
While we can't create images that contain partitions (yet), we should
still at least be able to examine them and show the user what's inside
when we analyze an imag
We will add support for ZynqMP bif input files later, so let's move
all structure definitions into a header file that can be used by that
one as well.
Signed-off-by: Alexander Graf
---
tools/zynqmpimage.c | 115 +
tools/zynqmpimage.h | 132
The officially described way to generate boot.bin files for ZynqMP is to
describe the contents of the target binary using a file of the "bif" format.
This file then links to other files that all get packed into a bootable image.
This patch adds support to read such a .bif file and generate a respe
We will add support for ZynqMP bif input files later, so let's move
all structure definitions into a header file that can be used by that
one as well.
Signed-off-by: Alexander Graf
---
tools/zynqmpimage.c | 115 +
tools/zynqmpimage.h | 132
The officially described way to generate boot.bin files for ZynqMP is to
describe the contents of the target binary using a file of the "bif" format.
This file then links to other files that all get packed into a bootable image.
This patch adds support to read such a .bif file and generate a respe
The zynqmp image format has support for inline partitions which are
used by FSBL to describe payloads that are loaded by FSBL itself.
While we can't create images that contain partitions (yet), we should
still at least be able to examine them and show the user what's inside
when we analyze an imag
A good chunk of the booting chain of ZynqMP based systems is open source
(depending on your definition of it), except for the image generation flow.
This patch set aims to change that, with read and write support for boot.bin
partitions which allows us to create boot.bin files using only open sour
On Wed, Apr 11, 2018 at 11:13:05PM +0800, Jun Nie wrote:
> It may be unnecessary to check signature on unlocked board.
> Get the hint from platform specific code to support secure boot
> and non-secure boot with the same binary, so that boot is not
> blocked if board is not locked and has no key f
On Wed, Apr 11, 2018 at 09:23:19PM +0200, Sjoerd Simons wrote:
> To make it simpler to enable the debug uart on boneblack add debug
> uart configuration as an example in the defconfig but with
> CONFIG_DEBUG_UART disabled. Which allows a user to simple enable it when
> needing easily without figur
On Thu, Apr 12, 2018 at 09:04:20AM +0200, Jason Mitchell wrote:
> Good day all
>
> I am currently faced with a task of having to run new software on ageing
> hardware. We have currently about 1000 units in the field of a machine that
> runs Windows CE using the Samsung S3C6410.
>
> Because these
None of the SoCFPGA platforms will support EFI/ISO partition types that
is needed for DISTRO_DEFAULTS. SoCFPGA bootroom will only support 0xa2
partition type.
This is needed to help limit the size of the SPL to within the 64k limit
that is required for SoCFPGA.
Signed-off-by: Dinh Nguyen
---
co
On 04/12/2018 04:03 PM, Dinh Nguyen wrote:
> None of the SoCFPGA platforms will support EFI/ISO partition types that
> is needed for DISTRO_DEFAULTS. SoCFPGA bootroom will only support 0xa2
> partition type.
>
> This is needed to help limit the size of the SPL to within the 64k limit
> that is req
On Wed, 2018-04-11 at 16:58 -0400, Tom Rini wrote:
> On Wed, Apr 11, 2018 at 09:26:40PM +0200, Sjoerd Simons wrote:
>
> > Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC
> > flag") omap GPIO gets bound before relocation. Unfortunately due
> > to
> > this, on at least the beagle
On Thu, Apr 12, 2018 at 05:21:27PM +0200, Sjoerd Simons wrote:
> On Wed, 2018-04-11 at 16:58 -0400, Tom Rini wrote:
> > On Wed, Apr 11, 2018 at 09:26:40PM +0200, Sjoerd Simons wrote:
> >
> > > Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC
> > > flag") omap GPIO gets bound befo
On 04/11/2018 03:58 PM, Tom Rini wrote:
> On Wed, Apr 11, 2018 at 09:26:40PM +0200, Sjoerd Simons wrote:
>
>> Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC
>> flag") omap GPIO gets bound before relocation. Unfortunately due to
>> this, on at least the beaglebone black, the pr
Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC
flag") omap GPIO gets bound before relocation. Unfortunately due to
this, on at least the beaglebone black, the pre-relocation memory pool
gets exhausted before probing the serial port. This then causes u-boot
to panic as CONFIG_RE
Hi Mario,
On 11 April 2018 at 01:15, Mario Six wrote:
> Hi Simon,
>
> On Fri, Mar 30, 2018 at 10:41 AM, Simon Glass wrote:
>> Hi Mario,
>>
>> On 28 March 2018 at 20:38, Mario Six wrote:
>>> A lot of times one wants to cycle through the devices in a uclass, but
>>> only certain ones, especially
On Tue, Mar 27, 2018 at 12:18 PM, Matt Pelland wrote:
> mvneta already supports setting the MAC address but this was only done
> internally when some other part of U-Boot tries to actually use the
> interface. This commit exposes this functionality to the ethernet core
> code so that the MAC addre
On Thu, Apr 12, 2018 at 5:20 AM, Stefan Roese wrote:
> Hi Matt,
>
> (added Joe as network custodian to Cc)
>
>
> On 27.03.2018 19:18, Matt Pelland wrote:
>>
>> mvneta already supports setting the MAC address but this was only done
>> internally when some other part of U-Boot tries to actually use
Hi Mario,
On 11 April 2018 at 00:35, Mario Six wrote:
> Hi Simon,
>
> On Fri, Mar 30, 2018 at 10:41 AM, Simon Glass wrote:
>> Hi Mario,
>>
>> On 28 March 2018 at 20:40, Mario Six wrote:
>>> Add a power_on function to the display uclass to allow devices to be
>>> probed and powered-on separately
Hi Mario,
On 11 April 2018 at 00:39, Mario Six wrote:
> Hi Simon,
>
> On Fri, Mar 30, 2018 at 10:41 AM, Simon Glass wrote:
>> Hi,
>>
>> On 28 March 2018 at 20:38, Mario Six wrote:
>>> Add a cpu_print_info function to the CPU uclass to emulate the behavior
>>> of some current non-DM drivers (e.g
Hi Mario,
On 11 April 2018 at 01:27, Mario Six wrote:
> Hi Simon,
>
> On Fri, Mar 30, 2018 at 10:41 AM, Simon Glass wrote:
>> Hi Mario,
>>
>> On 28 March 2018 at 20:40, Mario Six wrote:
>>> Add a driver for the Xilinx LogiCORE DisplayPort IP core.
>>>
>>> Signed-off-by: Mario Six
>>> ---
>>>
On 12 April 2018 at 02:03, Neil Armstrong wrote:
> In the commit "reset: Add get/assert/deassert/release for bulk of reset
> signals"
> the disabled reset_release_bulk() and reset_get_bulk() used the wrong
> struct clk_bulk instead of struct reset_ctl_bulk.
>
> Fixes: 0c28233903b5 ("reset: Add ge
Hi,
On 12 April 2018 at 03:20, Michalis Pappas wrote:
> Okay, i see. The change is the replacement of the dependency of ARM64 to
> ARM_SMCCC in Kconfig.
>
> If you think it's necessary to issue a v4 and document the changes properly
> please let me know and I'll do so.
Yes please.
>
> Michalis
On 11 April 2018 at 23:02, Bin Meng wrote:
> If video initialization fails, the "Video:" output message will be
> mixed with the next console log. Change to print out such message
> only when everything is OK, which improves the boot log readability.
>
> Signed-off-by: Bin Meng
> ---
>
> Changes
On 11 April 2018 at 23:02, Bin Meng wrote:
> This changes the default FRAMEBUFFER_VESA_MODE to use 32-bit pixel
> format for better VxWorks compatibility.
>
> Signed-off-by: Bin Meng
> ---
>
> Changes in v2: None
>
> drivers/video/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
R
Hi Mario,
On 10 April 2018 at 05:23, Mario Six wrote:
> Hi Simon,
>
> On Fri, Mar 30, 2018 at 12:43 AM, Simon Glass wrote:
>> Hi Mario,
>>
>> On 28 March 2018 at 20:37, Mario Six wrote:
>>> Implement a set of functions to manipulate properties in a live device
>>> tree:
>>>
>>> * ofnode_set_pro
On 11 April 2018 at 23:02, Bin Meng wrote:
> This adds ELF header, program header and section header structure
> defines for the 64-bit ELF image.
>
> Signed-off-by: Bin Meng
> ---
>
> Changes in v2: None
>
> include/elf.h | 43 +++
> 1 file changed, 43 in
On 11 April 2018 at 23:02, Bin Meng wrote:
> VxWorks bootloader stores its size at a pre-defined offset @ 0x5004.
> Later when VxWorks kernel boots up and system memory information is
> retrieved from the E820 table, the bootloader size will be subtracted
> from the total system memory size to cal
On 11 April 2018 at 23:02, Bin Meng wrote:
> This changes some boards' default FRAMEBUFFER_VESA_MODE to use 32-bit
> pixel format for better VxWorks compatibility.
>
> Signed-off-by: Bin Meng
> ---
>
> Changes in v2: None
>
> configs/bayleybay_defconfig | 2 +-
> configs/minnowmax_d
On 11 April 2018 at 23:02, Bin Meng wrote:
> When booting from EFI BIOS, VxWorks bootloader stores the EFI GOP
> framebuffer info at a pre-defined offset @ 0x6100. When VxWorks
> kernel boots up, its EFI console driver tries to find such a block
> and if the signature matches, the framebuffer info
1 - 100 of 131 matches
Mail list logo
