When building without FASTBOOT_FLASH we don't include the intermediate
update callback to keep the client alive, so ensure we don't try setting
it here.
Signed-off-by: Alex Kiernan
---
net/fastboot.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/fastboot.c b/net/fastboot.c
index
Typically init_scsi() does not output anything. So initr_scsi() should
provide a \n or we may see borked output like
SCSI: Net: No ethernet found.
as observed with sandbox_defconfig.
Signed-off-by: Heinrich Schuchardt
---
common/board_r.c | 1 +
1 file changed, 1 insertion(+)
diff
On 06/14/2018 11:42 PM, Tom Rini wrote:
> On Thu, Jun 14, 2018 at 10:58:22PM +0200, Marek Vasut wrote:
>> On 06/14/2018 03:07 PM, Tom Rini wrote:
>>> On Thu, Jun 14, 2018 at 01:35:05PM +0200, Marek Vasut wrote:
On 06/14/2018 01:19 PM, Tom Rini wrote:
> On Wed, Jun 13, 2018 at 06:05:08AM
Sync the PFC tables with Linux v4.17.
Signed-off-by: Marek Vasut
Cc: Nobuhiro Iwamatsu
---
V2: Fix build errors
drivers/pinctrl/renesas/pfc-r8a7790.c | 8 +-
drivers/pinctrl/renesas/pfc-r8a7791.c | 84 -
drivers/pinctrl/renesas/pfc-r8a7794.c | 473 ++
3 files
The following generated files should be ignored by git:
efi_miniapp_file_image_exit.h
efi_miniapp_file_image_return.h
*.so files are normally deleted during the build but should be
ignored too.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_selftest/.gitignore | 4 +++-
1 file changed, 3
On 06/14/2018 10:50 PM, Mark Kettenis wrote:
>> From: Heinrich Schuchardt
>> Date: Thu, 14 Jun 2018 19:55:51 +0200
>>
>> On 06/14/2018 12:41 AM, Mark Kettenis wrote:
>>> This series makes it possible to run EFI applications in non-secure
>>> mode. It allows me to run OpenBSD on the Technexion
So far we've always had a split address space situation with
"U-Boot addresses" (a number space starting from 0) and "host
virtual addresses" (128MB mapped randomly in address space).
This meant that we had to make sure all code is properly aware that
addresses and pointers are not the same
On 14.06.18 23:35, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 13:51, Alexander Graf wrote:
>>
>>
>> On 14.06.18 21:01, Simon Glass wrote:
>>> On 14 June 2018 at 12:22, Alexander Graf wrote:
The fs_read() function wants to get an address rather than the
pointer to a buffer.
On Thu, Jun 14, 2018 at 10:58:22PM +0200, Marek Vasut wrote:
> On 06/14/2018 03:07 PM, Tom Rini wrote:
> > On Thu, Jun 14, 2018 at 01:35:05PM +0200, Marek Vasut wrote:
> >> On 06/14/2018 01:19 PM, Tom Rini wrote:
> >>> On Wed, Jun 13, 2018 at 06:05:08AM +0200, Marek Vasut wrote:
> >>>
> The
Signed-off-by: Alexey Brodkin
---
board/synopsys/hsdk/README | 121 +
1 file changed, 121 insertions(+)
create mode 100644 board/synopsys/hsdk/README
diff --git a/board/synopsys/hsdk/README b/board/synopsys/hsdk/README
new file mode 100644
index
Hi Alex,
On 14 June 2018 at 13:15, Alexander Graf wrote:
>
>
> On 14.06.18 21:02, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> With efi_loader we do not control payload applications, so we can not
>>> teach them about the difference between virtual
Some legacy boards use RAW image for SPL boot. Add Kconfig option
SPL_PAYLOAD to set alternative image.
Signed-off-by: York Sun
---
Makefile | 4 ++--
common/spl/Kconfig | 10 ++
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index
Hi Heinrich,
On 14 June 2018 at 13:21, Heinrich Schuchardt wrote:
> On 06/14/2018 09:02 PM, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> With efi_loader we do not control payload applications, so we can not
>>> teach them about the difference between
Hi Alex,
On 14 June 2018 at 13:51, Alexander Graf wrote:
>
>
> On 14.06.18 21:01, Simon Glass wrote:
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> The fs_read() function wants to get an address rather than the
>>> pointer to a buffer.
>>>
>>> So let's convert the passed buffer from
On 9 June 2018 at 09:45, Teddy Reed wrote:
> The hashed-strings signature property includes two uint32_t values.
> The first is unneeded as there should never be a start offset into the
> strings region. The second, the size, is needed because the added
> signature node appends to this region.
>
On 14 June 2018 at 12:08, Manivannan Sadhasivam
wrote:
> This commit adds Actions Semi OWL family base clock and S900 SoC specific
> clock support. For S900 peripheral clock support, only UART clock has been
> added for now.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
> Changes in v3:
>
> *
On 14 June 2018 at 12:08, Manivannan Sadhasivam
wrote:
> This commit adds Actions Semi OWL family UART support. This driver
> relies on baudrate configured by primary bootloaders.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
> Changes in v3:
>
> * Moved the change log from cover letter
>
>
On 14 June 2018 at 12:08, Manivannan Sadhasivam
wrote:
> This commit adds Actions Semi S900 CMU register definitions to clock
> bindings.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
>
> Changes in v3:
>
> * Moved the change log from cover letter
>
> Changes in v2:
>
> * Added missing
Some environments require providing the '--smtp-server' argument to
'git send-email'. Add support for this.
Signed-off-by: Simon Glass
---
tools/patman/README | 1 +
tools/patman/gitutil.py | 6 +-
tools/patman/patman.py | 5 -
3 files changed, 10 insertions(+), 2 deletions(-)
For SoCs with PBL, u-boot-with-spl-pbl.bin is the final image for
SPL boot. Drop unused u-boot-with-spl.bin.
Signed-off-by: York Sun
CC: Ashish Kumar
CC: Ruchika Gupta
CC: Priyanka Jain
CC: Shengzhou Liu
---
include/configs/B4860QDS.h | 1 -
include/configs/T102xQDS.h | 1 -
For SPL boot with PBL, u-boot-with-spl-pbl.bin is the final image.
Drop unused u-boot-with-spl.bin.
Signed-off-by: York Sun
CC: Mingkai Hu
CC: Ruchika Gupta
CC: Prabhakar Kushwaha
CC: Udit Agarwal
CC: Sumit Garg
CC: Priyanka Jain
---
include/configs/ls1043a_common.h | 2 --
Signed-off-by: Simon Glass
---
tools/patman/gitutil.py | 3 +++
tools/patman/settings.py | 7 +++
2 files changed, 10 insertions(+)
diff --git a/tools/patman/gitutil.py b/tools/patman/gitutil.py
index 64ac0c8d3d..c383af1cb3 100644
--- a/tools/patman/gitutil.py
+++
On 06/14/2018 03:07 PM, Tom Rini wrote:
> On Thu, Jun 14, 2018 at 01:35:05PM +0200, Marek Vasut wrote:
>> On 06/14/2018 01:19 PM, Tom Rini wrote:
>>> On Wed, Jun 13, 2018 at 06:05:08AM +0200, Marek Vasut wrote:
>>>
The following changes since commit
> From: Marc Zyngier
> Date: Thu, 14 Jun 2018 12:54:53 +0100
>
> On 13/06/18 23:41, Mark Kettenis wrote:
> > If desired (and possible) switch into HYP mode or non-secure SVC mode
> > before calling the entry point of an EFI application. This allows
> > U-Boot to provide a usable PSCI
> From: Heinrich Schuchardt
> Date: Thu, 14 Jun 2018 19:55:51 +0200
>
> On 06/14/2018 12:41 AM, Mark Kettenis wrote:
> > This series makes it possible to run EFI applications in non-secure
> > mode. It allows me to run OpenBSD on the Technexion PICO-PI-IMX7 and
> > Banana Pi boards using the
As used on some distro, such as openSUSE.
Signed-off-by: Guillaume GARDET
Cc: Tom Rini
---
include/config_distro_bootcmd.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/config_distro_bootcmd.h b/include/config_distro_bootcmd.h
index d672e8ebe6..ad4c7a78f1 100644
Needed to boot with EFI distro boot.
Signed-off-by: Guillaume GARDET
Cc: Akshay Saraswat
Cc: Tom Rini
---
include/configs/snow.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/configs/snow.h b/include/configs/snow.h
index 3b0db32ece..c546a5a6d0 100644
---
On 14.06.18 21:01, Simon Glass wrote:
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> The fs_read() function wants to get an address rather than the
>> pointer to a buffer.
>>
>> So let's convert the passed buffer from pointer back a the address
>> to make efi_loader on sandbox happier.
>>
On 14.06.18 21:26, Heinrich Schuchardt wrote:
> On 06/14/2018 09:13 PM, Alexander Graf wrote:
>>
>>
>> On 14.06.18 21:01, Simon Glass wrote:
>>> Hi Alex,
>>>
>>> On 14 June 2018 at 12:22, Alexander Graf wrote:
We try hard to make sure that SMBIOS tables live in the lower 32bit.
On 14.06.18 21:02, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:05, Alexander Graf wrote:
>>
>>
>>
>> On 14.06.18 19:15, Simon Glass wrote:
>>> Hi Alex,
>>>
>>> On 14 June 2018 at 11:08, Alexander Graf wrote:
On 06/14/2018 06:55 PM, Simon Glass wrote:
>
> Hi Alex,
On 06/14/2018 09:13 PM, Alexander Graf wrote:
>
>
> On 14.06.18 21:01, Simon Glass wrote:
>> Hi Alex,
>>
>> On 14 June 2018 at 12:22, Alexander Graf wrote:
>>> We try hard to make sure that SMBIOS tables live in the lower 32bit.
>>> However, when we can not find any space at all there, we
Hi Dennis,
On Thu, Jun 14, 2018 at 02:10:31PM -0500, Dennis Gilmore wrote:
> running sf probe on one of my clearfogs with this set of patches
> applied I got
>
> SF: unrecognized JEDEC id bytes: ff, ff, ff
> Failed to initialize SPI flash at 1:0 (error -2)
Do you use the clearfog_defconfig?
On 06/14/2018 09:02 PM, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> With efi_loader we do not control payload applications, so we can not
>> teach them about the difference between virtual and physical addresses.
>>
>> Instead, let's just always map host
On 14.06.18 21:02, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> With efi_loader we do not control payload applications, so we can not
>> teach them about the difference between virtual and physical addresses.
>>
>> Instead, let's just always map host
On 14.06.18 21:01, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 12:22, Alexander Graf wrote:
>> We try hard to make sure that SMBIOS tables live in the lower 32bit.
>> However, when we can not find any space at all there, we should not
>> error out but instead just fall back to map
running sf probe on one of my clearfogs with this set of patches
applied I got
SF: unrecognized JEDEC id bytes: ff, ff, ff
Failed to initialize SPI flash at 1:0 (error -2)
Dennis
On Thu, 2018-06-14 at 18:17 +0300, Baruch Siach wrote:
> Add the "spi-flash" compatible string so that the
Reviewed-by: Dennis Gilmore
Tested-by: Dennis Gilmore
On Thu, 2018-06-14 at 18:17 +0300, Baruch Siach wrote:
> Use hardware description from the recently introduced microsom .dtsi
> file to reduce duplication.
>
> Signed-off-by: Baruch Siach
> ---
> arch/arm/dts/armada-388-clearfog.dts | 63
Reviewed-by: Dennis Gilmore
Tested-by: Dennis Gilmore
On Thu, 2018-06-14 at 18:17 +0300, Baruch Siach wrote:
> From: Jon Nettleton
>
> This makes changes so the u-boot dts file is structured more
> similar to the mainline linux dtsi file. It provides a minimal
> common dts that can work for
Reviewed-by: Dennis Gilmore
Tested-by: Dennis Gilmore
On Thu, 2018-06-14 at 18:17 +0300, Baruch Siach wrote:
> The same pinctrl node appears in the solidrun-microsom dtsi. Use that
> instead.
>
> Cc: Dennis Gilmore
> Signed-off-by: Baruch Siach
> ---
> arch/arm/dts/armada-388-helios4.dts |
Hi Alex,
On 14 June 2018 at 12:05, Alexander Graf wrote:
>
>
>
> On 14.06.18 19:15, Simon Glass wrote:
> > Hi Alex,
> >
> > On 14 June 2018 at 11:08, Alexander Graf wrote:
> >>
> >> On 06/14/2018 06:55 PM, Simon Glass wrote:
> >>>
> >>> Hi Alex,
> >>>
> >>> On 14 June 2018 at 10:42, Alexander
Hi Alex,
On 14 June 2018 at 12:22, Alexander Graf wrote:
> With efi_loader we do not control payload applications, so we can not
> teach them about the difference between virtual and physical addresses.
>
> Instead, let's just always map host virtual addresses in the efi memory
> map. That way
On 14 June 2018 at 12:22, Alexander Graf wrote:
> The fs_read() function wants to get an address rather than the
> pointer to a buffer.
>
> So let's convert the passed buffer from pointer back a the address
> to make efi_loader on sandbox happier.
>
> Signed-off-by: Alexander Graf
>
> ---
>
> v1
Hi Alex,
On 14 June 2018 at 12:22, Alexander Graf wrote:
> We try hard to make sure that SMBIOS tables live in the lower 32bit.
> However, when we can not find any space at all there, we should not
> error out but instead just fall back to map them in the full address
> space instead.
>
>
Hi Alex,
On 14 June 2018 at 12:22, Alexander Graf wrote:
> The EFI image loader tries to determine which target architecture we're
> working with to only load PE binaries that match.
>
> So far this has worked based on CONFIG defines, because the target CPU
> was always indicated by a config
On 14 June 2018 at 12:22, Alexander Graf wrote:
> In the sandbox environment we can not easily build efi stub binaries
> right now, so let's disable the respective test cases for the efi
> selftest suite.
>
> Signed-off-by: Alexander Graf
> ---
> lib/efi_selftest/Makefile | 2 +-
> 1 file
On 14 June 2018 at 12:22, Alexander Graf wrote:
> The bootefi command gets a few addresses as values passed in. In sandbox,
> these values are in U-Boot address space, so we need to make sure we
> explicitly call map_sysmem() on them to be able to access them.
>
> Signed-off-by: Alexander Graf
>
With efi_loader we do not control payload applications, so we can not
teach them about the difference between virtual and physical addresses.
Instead, let's just always map host virtual addresses in the efi memory
map. That way we can be sure that all memory allocation functions always
return
On Thu, Jun 14, 2018 at 1:12 PM, Dr. Philipp Tomsich
wrote:
>
>> On 14 Jun 2018, at 19:39, Joe Hershberger wrote:
>>
>> On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann
>> wrote:
>>> We have to use RK3328_RXCLK_DLY_ENA_GMAC_ENABLE instead of
>>> RK3328_RXCLK_DLY_ENA_GMAC_MASK in
The EFI image loader tries to determine which target architecture we're
working with to only load PE binaries that match.
So far this has worked based on CONFIG defines, because the target CPU
was always indicated by a config define. With sandbox however, this is
not longer true as all sandbox
The fs_read() function wants to get an address rather than the
pointer to a buffer.
So let's convert the passed buffer from pointer back a the address
to make efi_loader on sandbox happier.
Signed-off-by: Alexander Graf
---
v1 -> v2:
- Clarify address vs pointer
- include mapmem.h
---
From: Simon Glass
Add these so that we can build the EFI loader for sandbox. The values are
for x86_64 so potentially bogus. But we don't support relocation within
sandbox anyway.
Signed-off-by: Simon Glass
Signed-off-by: Alexander Graf
---
lib/efi_loader/efi_runtime.c | 12
1
This patch set augments Simon's patch set for efi_loader support
in sandbox[1], but follows a different memory allocation scheme.
Instead of keeping U-Boot (physical) addresses in the EFI memory
map, this patch set makes the EFI memory map contain host virtual
(virtual) addresses. That way most
From: Simon Glass
With sandbox these values depend on the host system. Let's assume that it
is x86_64 for now.
Signed-off-by: Simon Glass
Signed-off-by: Alexander Graf
---
include/config_distro_bootcmd.h | 13 +
1 file changed, 13 insertions(+)
diff --git
From: Simon Glass
This allows this feature to build within sandbox. This is for testing
purposes only since it is not possible for sandbox to load native code.
Signed-off-by: Simon Glass
Signed-off-by: Alexander Graf
---
lib/efi_loader/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1
From: Heinrich Schuchardt
When running on the sandbox the stack is not necessarily at a higher memory
address than the highest free memory.
There is no reason why the checking of the highest memory address should be
more restrictive for EFI_ALLOCATE_ANY_PAGES than for
EFI_ALLOCATE_MAX_ADDRESS.
The bootefi command gets a few addresses as values passed in. In sandbox,
these values are in U-Boot address space, so we need to make sure we
explicitly call map_sysmem() on them to be able to access them.
Signed-off-by: Alexander Graf
---
cmd/bootefi.c | 13 -
1 file changed, 8
In the sandbox environment we can not easily build efi stub binaries
right now, so let's disable the respective test cases for the efi
selftest suite.
Signed-off-by: Alexander Graf
---
lib/efi_selftest/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Currently efi.h determines a few bits of its environment according to
config options. This falls apart with the efi stub support which may
result in efi.h getting pulled into the stub as well as real U-Boot
code. In that case, one may be 32bit while the other one is 64bit.
This patch changes the
We try hard to make sure that SMBIOS tables live in the lower 32bit.
However, when we can not find any space at all there, we should not
error out but instead just fall back to map them in the full address
space instead.
Signed-off-by: Alexander Graf
---
lib/efi_loader/efi_smbios.c | 11
Hi Duncan,
On Thu, Jun 14, 2018 at 1:03 PM, wrote:
> Cloned most recent u-boot 2018.06.14
> make clean works
> make menuconfig fails:
>
> /bin/sh: 1: bison: not found
> scripts/kconfig/Makefile:229: recipe for target
> 'scripts/kconfig/dochecklxdialog' failed make[1]: ***
>
This commit enables UART5 found in S900 SoC for serial console support.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
arch/arm/dts/bubblegum_96.dts | 12
1 file changed, 12 insertions(+)
diff --git
This commit adds Actions Semi OWL family base clock and S900 SoC specific
clock support. For S900 peripheral clock support, only UART clock has been
added for now.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2:
* Removed
> On 14 Jun 2018, at 19:39, Joe Hershberger wrote:
>
> On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
>> We have to use RK3328_RXCLK_DLY_ENA_GMAC_ENABLE instead of
>> RK3328_RXCLK_DLY_ENA_GMAC_MASK in rk3328_gmac_set_to_rgmii()
>> to enable the RX delay.
>> The MASK was used in a
This commit adds UART node for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
arch/arm/dts/s900.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/dts/s900.dtsi
Add myself as the Maintainer for Actions Semi OWL family and its
relevant board, drivers.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS
This commit adds Actions Semi OWL family UART support. This driver
relies on baudrate configured by primary bootloaders.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
drivers/serial/Kconfig | 8 +++
This commit adds uCRobotics Bubblegum-96 board support. This board is
one of the 96Boards Consumer Edition platform based on Actions Semi
S900 SoC.
Features:
- Actions Semi S900 SoC (4xCortex A53, Power VR G6230 GPU)
- 2GiB RAM
- 8GiB eMMC, uSD slot
- WiFi, Bluetooth and GPS module
- 2x Host, 1x
This commit adds Actions Semi S900 CMU register definitions to clock
bindings.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2:
* Added missing Signed-off-by tag
include/dt-bindings/clock/s900_cmu.h | 77
This commit adds Clock Management Unit (CMU) nodes for Actions Semi
S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
arch/arm/dts/s900.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git
This commit adds Actions Semi OWL SoC family support with S900 as the
first target SoC.
Signed-off-by: Manivannan Sadhasivam
---
Changes in v3:
* Moved the change log from cover letter
Changes in v2: None
arch/arm/Kconfig| 9 +
arch/arm/Makefile | 1 +
This patchset adds SoC support for Actions Semi S900 SoC and ucRobotics
Bubblegum-96 board along with UART and Clock drivers.
S900 SoC consists of 4 ARM Cortex-A53 cores up to 1.8GHz with
Imagination Power VR G6230 GPU. More information on this SoC can be
found in Actions Semi product page:
On 14.06.18 19:15, Simon Glass wrote:
> Hi Alex,
>
> On 14 June 2018 at 11:08, Alexander Graf wrote:
>>
>> On 06/14/2018 06:55 PM, Simon Glass wrote:
>>>
>>> Hi Alex,
>>>
>>> On 14 June 2018 at 10:42, Alexander Graf wrote:
On 06/14/2018 06:33 PM, Simon Glass wrote:
>
> Hi
Cloned most recent u-boot 2018.06.14
make clean works
make menuconfig fails:
/bin/sh: 1: bison: not found
scripts/kconfig/Makefile:229: recipe for target
'scripts/kconfig/dochecklxdialog' failed make[1]: ***
[scripts/kconfig/dochecklxdialog] Error 1 Makefile:491: recipe for
target 'menuconfig'
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> The DP83867 has a muxing option for the CLK_OUT pin. It is possible
> to set CLK_OUT for different channels.
> Create a binding to select a specific clock for CLK_OUT pin.
>
> Based on commit '9708fb630d19ee51ae3aeb3a533e3010da0e8570'
On 14.06.18 19:55, Heinrich Schuchardt wrote:
> On 06/14/2018 12:41 AM, Mark Kettenis wrote:
>> This series makes it possible to run EFI applications in non-secure
>> mode. It allows me to run OpenBSD on the Technexion PICO-PI-IMX7 and
>> Banana Pi boards using the PSCI implementation provided
On 06/14/2018 12:41 AM, Mark Kettenis wrote:
> This series makes it possible to run EFI applications in non-secure
> mode. It allows me to run OpenBSD on the Technexion PICO-PI-IMX7 and
> Banana Pi boards using the PSCI implementation provided by U-Boot.
>
> The second version avoids using r3 to
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> Add the ability to read the phy-handle node of the
> gmac. Upon reading this handle the phy-id
> can be stored based on the reg node in the DT.
>
> The phy-handle also needs to be stored and passed
> to the phy to access any phy data that
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> Using PHY internal delays in combination with the phy-mode
> rgmii-id/rxid/txid was not possible. Only rgmii was supported.
>
> Now we can disable rockchip's gmac delay lines and also use
> rgmii-id/rxid/txid.
>
> Based on commit
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> The data manual for DP83867IR/CR, SNLS484E[1], revised march 2017,
> advises that strapping RX_DV/RX_CTRL pin in mode 1 and 2 is not
> supported (see note below Table 5 (4-Level Strap Pins)).
>
> There are some boards which have the pin
> Am 14.06.2018 um 19:15 schrieb Ivan Gorinov :
>
> On Wed, Jun 13, 2018 at 05:36:26PM -0700, Ivan Gorinov wrote:
>
>>> But bootefi selftest with your patch leads to an immediate reset of the
>>> qemu-x86_64 board.
>>
>> Reproduced the qemu-x86_64 reset.
>> The "info registers" command shows
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> The DP83867 when not properly bootstrapped - especially with LED_0 pin -
> can enter N/A MODE4 for "port mirroring" feature.
>
> To provide normal operation of the PHY, one needs not only to explicitly
> disable the port mirroring feature,
Hi,
On 14 June 2018 at 11:25, Manivannan Sadhasivam
wrote:
> Hi Simon,
>
> On Thu, Jun 14, 2018 at 08:16:53AM -0600, Simon Glass wrote:
>> Hi,
>>
>> On 14 June 2018 at 07:13, Manivannan Sadhasivam
>> wrote:
>> > Hi Simon,
>> >
>> > On Thu, Jun 14, 2018 at 06:58:40AM -0600, Simon Glass wrote:
>>
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> This patch adds support for enabling or disabling the lane swapping
> (called "port mirroring" in PHY's CFG4 register) feature of the DP83867
> TI's PHY device.
>
> One use case is when bootstrap configuration enables this feature (because
On Thu, Jun 14, 2018 at 12:09 PM, Trent Piepho wrote:
> On Thu, 2018-06-14 at 10:53 +, u-boot-requ...@lists.denx.de wrote:
>> Message: 52
>> Date: Thu, 14 Jun 2018 11:48:48 +0200
>> From: Janine Hagemann
>> To: albert.u.b...@aribaud.net, s...@chromium.org,
>>
On Thu, Jun 14, 2018 at 4:48 AM, Janine Hagemann wrote:
> We have to use RK3328_RXCLK_DLY_ENA_GMAC_ENABLE instead of
> RK3328_RXCLK_DLY_ENA_GMAC_MASK in rk3328_gmac_set_to_rgmii()
> to enable the RX delay.
> The MASK was used in a wrong way.
>
> Signed-off-by: Janine Hagemann
Acked-by: Joe
On Thu, Jun 14, 2018 at 2:08 AM, Michal Simek wrote:
> phyread can timeout and val will contain random value. Initialize it to
> zero not to report random value in case of error.
>
> Signed-off-by: Michal Simek
Acked-by: Joe Hershberger
> ---
>
> Reported by: Coverity (local)
>
> ---
>
Hi Simon,
On Thu, Jun 14, 2018 at 08:16:53AM -0600, Simon Glass wrote:
> Hi,
>
> On 14 June 2018 at 07:13, Manivannan Sadhasivam
> wrote:
> > Hi Simon,
> >
> > On Thu, Jun 14, 2018 at 06:58:40AM -0600, Simon Glass wrote:
> >> Hi,
> >>
> >> On 12 June 2018 at 22:15, Manivannan Sadhasivam
> >>
On Wed, Jun 13, 2018 at 05:36:26PM -0700, Ivan Gorinov wrote:
> > But bootefi selftest with your patch leads to an immediate reset of the
> > qemu-x86_64 board.
>
> Reproduced the qemu-x86_64 reset.
> The "info registers" command shows CR0.MP = 0.
> Setting it in 64-bit startup code did not
Hi Alex,
On 14 June 2018 at 11:08, Alexander Graf wrote:
>
> On 06/14/2018 06:55 PM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 14 June 2018 at 10:42, Alexander Graf wrote:
>>>
>>> On 06/14/2018 06:33 PM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 10:26, Alexander Graf
On Thu, 2018-06-14 at 10:53 +, u-boot-requ...@lists.denx.de wrote:
> Message: 52
> Date: Thu, 14 Jun 2018 11:48:48 +0200
> From: Janine Hagemann
> To: albert.u.b...@aribaud.net, s...@chromium.org,
> philipp.toms...@theobroma-systems.com, w.ego...@phytec.de,
>
On 06/14/2018 06:55 PM, Simon Glass wrote:
Hi,
On 14 June 2018 at 10:33, Alexander Graf wrote:
This patch set augments Simon's patch set for efi_loader support
in sandbox[1], but follows a different memory allocation scheme.
Instead of keeping U-Boot (physical) addresses in the EFI memory
On 06/14/2018 06:55 PM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 10:42, Alexander Graf wrote:
On 06/14/2018 06:33 PM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 10:26, Alexander Graf wrote:
On 06/14/2018 06:13 PM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 10:07, Alexander
On Thu, Jun 14, 2018 at 5:04 AM, Alexander Graf wrote:
> Currently we can choose between 2 different types of behavior for the
> serverip variable:
>
> 1) Always overwrite it with the DHCP server IP address (default)
> 2) Ignore what the DHCP server says (CONFIG_BOOTP_SERVERIP)
>
> This patch
Hi Tom,
This is my current patch queue for efi. Please pull.
Alex
The following changes since commit acaee30608ce203289a180d664b7f0abb2e64ee7:
ARM: DTS: resync a3517.dtsi with Linux 4.17 (2018-06-13 07:49:14 -0400)
are available in the git repository at:
Add a new bootefi_run_prepare() function which holds common code used to
set up U-Boot to run EFI code. Make use of this from the existing
bootefi_test_prepare() function, as well as do_bootefi_exec().
Also shorten a few variable names.
Signed-off-by: Simon Glass
---
Changes in v7: None
Hi Alex,
On 14 June 2018 at 10:42, Alexander Graf wrote:
> On 06/14/2018 06:33 PM, Simon Glass wrote:
>>
>> Hi Alex,
>>
>> On 14 June 2018 at 10:26, Alexander Graf wrote:
>>>
>>> On 06/14/2018 06:13 PM, Simon Glass wrote:
Hi Alex,
On 14 June 2018 at 10:07, Alexander Graf
On Thu, Jun 14, 2018 at 5:04 AM, Alexander Graf wrote:
> The ax25-ae350 target currently uses CONFIG_BOOTP_SERVERIP which means we
> ignore the DHCP provided TFTP ip address. This breaks every case where we
> do now provide a serverip environment variable.
>
> Instead, let's use the new
Hi Alex,
On 14 June 2018 at 10:33, Alexander Graf wrote:
> The fs_read() function wants to get a virtual (u-boot address space
> in sandbox) address rather than a physical (host address space in
> sandbox) one.
>
The terminology is wrong here. It is not about virtual and physical
addresses -
We plan to run more than one EFI test. In order to avoid duplicating code,
create functions which handle preparing for running the test and cleaning
up afterwards.
Also shorten the awfully long variable names here.
Signed-off-by: Simon Glass
---
Changes in v7: None
Changes in v6: None
Changes
This jumps to test code which can call directly into the EFI support. It
does not need a separate image so it is easy to write tests with it.
This test can be executed without causing problems to the run-time
environemnt (e.g. U-Boot does not need to reboot afterwards).
For now the test just
1 - 100 of 218 matches
Mail list logo
