On 06/13/2018 04:37 AM, Simon Glass wrote:
The current code causes a compiler error on gcc 4.8.4 as used by sandbox
on Ubuntu 14.04, which is fairly recent. Init these variables to fix the
problem.
Signed-off-by: Simon Glass
I thought this patch was obsolete now?
Alex
Sync the gpio.h header with Linux 4.17, which contains new macros.
Signed-off-by: Marek Vasut
Cc: Tom Rini
---
include/dt-bindings/gpio/gpio.h | 21 +
1 file changed, 21 insertions(+)
diff --git a/include/dt-bindings/gpio/gpio.h b/include/dt-bindings/gpio/gpio.h
index
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 813d1fb56dc0af9567feb86cd71c49f14662044b:
>>
>> Merge branch 'master' of git://git.denx.de/u-boot-ubi (2018-06-08
>> 10:08:20 -0400)
>>
>> are available
On 06/14/2018 02:27 AM, Ivan Gorinov wrote:
UEFI specifies the calling convention used in Microsoft compilers;
first arguments of a function are passed in (%rcx, %rdx, %r8, %r9).
All other compilers use System V ABI by default, passing first integer
arguments of a function in (%rdi, %rsi, %rdx,
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 pass
Make sure that functions are working with proper strcture.
Signed-off-by: Michal Simek
---
Reported by: Coverity (local)
---
drivers/serial/serial_zynq.c | 27 ---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/drivers/serial/serial_zynq.c
This issue was found when OF_LIVE was enabled that there are scrambled
chars on the console like this:
Chip ID:zu3eg
Watchdog: Started��j� sdhci@ff16: 0, sdhci@ff17: 1
In:serial@ff01
I found a solution for this problem exactly the same as I found later in
serial_msm
On 06/13/2018 04:37 AM, Simon Glass wrote:
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
---
Changes in v6:
- Warn about building sandbox EFI support
On 06/13/2018 04:37 AM, Simon Glass wrote:
With sandbox these values depend on the host system. Let's assume that it
is x86_64 for now.
Signed-off-by: Simon Glass
---
Changes in v6:
- Warn about building sandbox EFI support on something other than __x86_64__
Changes in v5: None
Changes in
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, but as well stop some IC internal
testing (which disables RGMII
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 strapped this way and need
software workaround suggested by the data
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
of e.g. LED_0 wrong wiring) so then one needs to disable it in
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
---
drivers/net/gmac_rockchip.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi Guillaume,
On 14.06.2018 14:19, guillaume.gar...@free.fr wrote:
Clearfog config fails to build with U-Boot v2018.07-rc1, because SPL is too big:
LD spl/u-boot-spl
ld.bfd: SPL image too big
make[1]: *** [scripts/Makefile.spl:347: spl/u-boot-spl] Error 1
make: ***
Hi Siva,
On 14 June 2018 at 00:53, Siva Durga Prasad Paladugu wrote:
> Hi Simon,
>
>> -Original Message-
>> From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
>> Sent: Saturday, June 09, 2018 3:29 AM
>> To: Michal Simek
>> Cc: Siva Durga Prasad Paladugu ; U-Boot
- Stefan Roese a écrit :
> Hi Guillaume,
>
> On 14.06.2018 14:19, guillaume.gar...@free.fr wrote:
> > Clearfog config fails to build with U-Boot v2018.07-rc1, because SPL is too
> > big:
> >
> > LD spl/u-boot-spl
> >ld.bfd: SPL image too big
> >make[1]: ***
Hi,
this series contain some changes in this driver.
1. Coding style fixes - using BIT macro
2. Using output fifo more effectively
3. Avoid initialization after relocation again
4. Make sure that priv is valid all the time
5. Keep sparse happy
Thanks,
Michal
Michal Simek (5):
serial: zynq:
Coding style is checking to use BIT macros instead of shifts.
The patch is also fixing the rest of macros which should be BITs instead
of hex numbers.
Signed-off-by: Michal Simek
---
drivers/serial/serial_zynq.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
At start-up, the regulators have to be enabled. Let's use
regulators_enable_boot_on() to enable the regulators needed
for boot.
Signed-off-by: Wadim Egorov
Signed-off-by: Janine Hagemann
---
arch/arm/mach-rockchip/rk3288-board.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
add PHY_TI to support dp83867
Signed-off-by: Janine Hagemann
---
configs/phycore-rk3288_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/phycore-rk3288_defconfig b/configs/phycore-rk3288_defconfig
index 50b0c98..7d0535f 100644
--- a/configs/phycore-rk3288_defconfig
+++
On 21:36-20180613, Florian Fainelli wrote:
[...]
> >>> c) This workaround applies to only the boot processor. It is important
> >>> to apply workaround as necessary (context-save-restore) around low
> >>> power context loss OR additional processors as necessary in either
> >>> firmware
Change logic and put char to fifo till there is a space in output fifo.
Origin logic was that output fifo needs to be empty. It means only one
char was in output queue.
Also remove unused ZYNQ_UART_SR_TXEMPTY macro.
Signed-off-by: Michal Simek
---
drivers/serial/serial_zynq.c | 4 ++--
1 file
This function is used only inside this driver that's why should be
static.
Signed-off-by: Michal Simek
---
drivers/serial/serial_zynq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/serial/serial_zynq.c b/drivers/serial/serial_zynq.c
index
While trying to boot from network on a RISC-V AX25 platform, I saw
that the DHCP IP address did not get populated from the DHCP server
IP address. The reason for that was simple: CONFIG_BOOTP_SERVERIP
was set.
I don't know the history of that option, but it seems to decrease
intuitivity levels of
On 06/13/2018 04:37 AM, Simon Glass wrote:
With sandbox the U-Boot code is not mapped into the sandbox memory range
so does not need to be excluded when allocating EFI memory. Update the EFI
memory init code to take account of that.
Also use mapmem instead of a cast to convert a memory address
On 14 June 2018 at 03:32, Michal Simek wrote:
> Coding style is checking to use BIT macros instead of shifts.
> The patch is also fixing the rest of macros which should be BITs instead
> of hex numbers.
>
> Signed-off-by: Michal Simek
> ---
>
> drivers/serial/serial_zynq.c | 16
On 14 June 2018 at 03:32, Michal Simek wrote:
> This function is used only inside this driver that's why should be
> static.
>
> Signed-off-by: Michal Simek
> ---
>
> drivers/serial/serial_zynq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Simon Glass
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
> >> 813d1fb56dc0af9567feb86cd71c49f14662044b:
> >>
> >> Merge branch 'master' of
Actually the DRAM is not only seperated in one
bank. The DRAM bank information is stored in
gd->bd->bi_dram, so reserve lmb according to
gd->bd->bi_dram.
Signed-off-by: Jason Zhu
---
common/bootm.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/common/bootm.c
Actually the DRAM is not only seperated in one
bank. The DRAM bank information is stored in
gd->bd->bi_dram, so reserve lmb according to
gd->bd->bi_dram.
Signed-off-by: Jason Zhu
---
common/bootm.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/common/bootm.c
Add USB as boot target depending on the configuration.
Signed-off-by: Neil Armstrong
---
include/configs/meson-gx-common.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/configs/meson-gx-common.h
b/include/configs/meson-gx-common.h
index 6e61b70..7435f34 100644
---
From: Beniamino Galvani
Introduce a basic clock driver for Amlogic Meson SoCs which supports
enabling/disabling clock gates and getting their frequency.
Signed-off-by: Beniamino Galvani
Signed-off-by: Neil Armstrong
---
arch/arm/include/asm/arch-meson/clock.h | 117 ++
Enable USB on all Amlogic Meson GXL based board.
Enable Regulator support on all boards.
Enable ADC support on the LibreTech-CC board.
Signed-off-by: Neil Armstrong
---
configs/khadas-vim_defconfig | 14 ++
configs/libretech-cc_defconfig | 17 +
From: Beniamino Galvani
Use the clk framework to initialize clocks from drivers that need them
instead of having hardcoded frequencies and initializations from board
code.
Signed-off-by: Beniamino Galvani
Signed-off-by: Neil Armstrong
---
arch/arm/include/asm/arch-meson/gx.h | 10
Hi Alex,
On 14 June 2018 at 04:12, Alexander Graf wrote:
> On 06/13/2018 04:37 AM, Simon Glass wrote:
>>
>> With sandbox the U-Boot code is not mapped into the sandbox memory range
>> so does not need to be excluded when allocating EFI memory. Update the EFI
>> memory init code to take account
> When we boot using memdp (bootefi on an address without previous
> load that populates the device path) then the memory device path
> we pass in is not backed by any handle.
>
> That can result in weird effects. For example grub gets very grumpy
> about this inside the efi_net module and just
We can call commands like dhcp and bootp without arguments or with
explicit command line arguments that really should tell the code where
to look for files instead.
Unfortunately, the current code simply overwrites command line arguments
in the dhcp case with dhcp values.
This patch allows the
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 CONFIG_BOOT_PREFER_SERVERIP option to fall back
to the DHCP provided TFTP
This pin is supplied by 1.8V, but the default iodomain
setting is 3.3V.
Signed-off-by: Janine Hagemann
---
board/phytec/phycore_rk3288/phycore-rk3288.c | 16
1 file changed, 16 insertions(+)
diff --git a/board/phytec/phycore_rk3288/phycore-rk3288.c
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 is available.
Signed-off-by: Janine Hagemann
---
The register was not read before the writing, so the
previous value was overwritten.
Signed-off-by: Janine Hagemann
---
drivers/net/phy/ti.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/ti.c b/drivers/net/phy/ti.c
index 8f3ed8a..d7ae881 100644
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' mainline
linux kernel.
Signed-off-by: Janine Hagemann
---
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 'eaf70ad14cbbb99d46b78b1307628a16a3f6075d' from
mainline linux kernel.
The CLK_O_SEL default is synchronus to XI input clock,
which is 25 MHz. Set CLK_O_SEL to channel A transmit
clock so we have 125 MHz on CLK_OUT.
Signed-off-by: Janine Hagemann
---
arch/arm/dts/rk3288-phycore-som.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
On 06/13/2018 04:37 AM, Simon Glass wrote:
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
Are you sure you want to enable a "builder", not the "build"? (see
subject
The SARADC driver was merged after the following commit :
commit d35812368a59 ("regmap: change regmap_init_mem() to take ofnode instead
udevice")
Thus breaking build, this patch fixes the regmap_init_mem accordingly.
Signed-off-by: Neil Armstrong
---
drivers/adc/meson-saradc.c | 2 +-
1 file
This patchset :
- fixes meson-saradc build
- adds the meson clock driver from Beniamino with it's consent
- switches to the clock driver for Ethernet and I2C
- Enables boot from USB if config is enabled
- finally enables USB, Regulator & ADC drivers for selected boards
Beniamino Galvani (2):
Hi Stefan,
Clearfog config fails to build with U-Boot v2018.07-rc1, because SPL is too big:
LD spl/u-boot-spl
ld.bfd: SPL image too big
make[1]: *** [scripts/Makefile.spl:347: spl/u-boot-spl] Error 1
make: *** [Makefile:1510: spl/u-boot-spl] Error 2
Guillaume
Hi Alex,
On 14 June 2018 at 04:11, Alexander Graf wrote:
> On 06/13/2018 04:37 AM, Simon Glass wrote:
>>
>> The current code causes a compiler error on gcc 4.8.4 as used by sandbox
>> on Ubuntu 14.04, which is fairly recent. Init these variables to fix the
>> problem.
>>
>> Signed-off-by: Simon
Hi Alex,
On 13 June 2018 at 04:17, Alexander Graf wrote:
>
>
> On 13.06.18 03:29, Simon Glass wrote:
>> Hi Bin, Alex,
>>
>> On 12 June 2018 at 09:36, Bin Meng wrote:
>>> From: Alexander Graf
>>>
>>> Currently efi.h determines a few bits of its environment according to
>>> config options. This
On 14 June 2018 at 04:45, Ley Foon Tan wrote:
> Change to use CONFIG_IS_ENABLED(DM_RESET), so this can work in SPL
> build (CONFIG_SPL_DM_RESET) and U-boot build (CONFIG_DM_RESET).
>
> Signed-off-by: Ley Foon Tan
> ---
> include/reset.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
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
> 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
On 06/13/2018 04:37 AM, Simon Glass wrote:
These constants are defined in arch-specific code but redefined here. Add
a TODO to clean this up.
Signed-off-by: Simon Glass
Reviewed-by: Heinrich Schuchardt
This patch is part of efi-next already.
Alex
Hi Ken,
On 12 June 2018 at 22:33, wrote:
> From: Ken Ma
>
> Add a uclass which provides access to MDIO busses and includes
> operations required by MDIO.
> The implementation is based on the existing mii/phy/mdio data
> structures and APIs.
> This patch also adds evice tree binding for MDIO
On 14 June 2018 at 03:32, Michal Simek wrote:
> Change logic and put char to fifo till there is a space in output fifo.
> Origin logic was that output fifo needs to be empty. It means only one
> char was in output queue.
> Also remove unused ZYNQ_UART_SR_TXEMPTY macro.
>
> Signed-off-by: Michal
On 14 June 2018 at 03:32, Michal Simek wrote:
> This issue was found when OF_LIVE was enabled that there are scrambled
> chars on the console like this:
> Chip ID:zu3eg
> Watchdog: Started��j� sdhci@ff16: 0, sdhci@ff17: 1
> In:serial@ff01
>
> I found a solution for this
Hi,
On 14 June 2018 at 03:32, Michal Simek wrote:
> Make sure that functions are working with proper strcture.
>
> Signed-off-by: Michal Simek
> ---
>
> Reported by: Coverity (local)
>
> ---
> drivers/serial/serial_zynq.c | 27 ---
> 1 file changed, 24 insertions(+), 3
Hi,
On 12 June 2018 at 22:15, 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
> ---
>
On 14 June 2018 at 04:45, Ley Foon Tan wrote:
> Rename CONFIG_SPL_RESET_SUPPORT to CONFIG_SPL_DM_RESET, so can use
> CONFIG_IS_ENABLED(DM_RESET) checking in reset.h later.
>
> Signed-off-by: Ley Foon Tan
> ---
> arch/arm/mach-stm32mp/Kconfig | 2 +-
> common/spl/Kconfig| 2 +-
>
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 adds a 3rd option:
3) Use serverip from DHCP if no serverip is
On Wed, Jun 13, 2018 at 06:05:08AM +0200, Marek Vasut wrote:
> The following changes since commit 813d1fb56dc0af9567feb86cd71c49f14662044b:
>
> Merge branch 'master' of git://git.denx.de/u-boot-ubi (2018-06-08
> 10:08:20 -0400)
>
> are available in the Git repository at:
>
>
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 implementation and makes it possible
> to boot kernels into hypervisor mode using
On 14.6.2018 14:58, Simon Glass wrote:
> Hi,
>
> On 14 June 2018 at 03:32, Michal Simek wrote:
>> Make sure that functions are working with proper strcture.
>>
>> Signed-off-by: Michal Simek
>> ---
>>
>> Reported by: Coverity (local)
>>
>> ---
>> drivers/serial/serial_zynq.c | 27
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 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)
>
> ---
>
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 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 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:
> 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: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
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
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
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.
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: 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
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 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:
> 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
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
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:
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
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
---
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
With sandbox these values depend on the host system. Let's assume that it
is x86_64 for now.
Signed-off-by: Simon Glass
---
Changes in v7:
- Drop an unnecessary comment
Changes in v6:
- Warn about building sandbox EFI support on something other than __x86_64__
Changes in v5: None
Changes in
At present this code casts addresses to pointers so cannot be used with
sandbox. Update it to use mapmem instead.
Signed-off-by: Simon Glass
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3:
- Drop incorrect map_sysmem() in write_smbios_table()
With sandbox the U-Boot code is not mapped into the sandbox memory range
so does not need to be excluded when allocating EFI memory. Update the EFI
memory init code to take account of that.
Also use mapmem instead of a cast to convert a memory address to a
pointer.
Signed-off-by: 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
---
Changes in v7:
- Drop an unnecessary comment
Changes in v6:
- Warn about building sandbox EFI support
A limitation of the EFI loader at present is that it does not build with
sandbox. This makes it hard to write tests, since sandbox is used for most
testing in U-Boot.
This series enables the EFI loader feature. It allows sandbox to build and
run a trivial function which calls the EFI API to
This does not work at present and gives the following error:
output: 'ld.bfd: read in flex scanner failed
scripts/Makefile.lib:390: recipe for target
'lib/efi_selftest/efi_selftest_miniapp_return_efi.so' failed
It may be possible to figure this out with suitable linker magic but it
does not
This function can be used from do_bootefi_exec() so that we use mostly the
same code for a normal EFI application and an EFI test.
Rename the function and use it in both places.
Signed-off-by: Simon Glass
---
Changes in v7:
- Drop patch "efi: Init the 'rows' and 'cols' variables"
- Drop
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
> map, this patch set makes the EFI
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
---
Changes in v7:
- Update patch subject s/builder/build/
Changes in v6: None
Changes in v5: None
Changes in v4: None
> 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
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 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
1 - 100 of 218 matches
Mail list logo
