Signed-off-by: Amrita Kumari
Signed-off-by: Ashish Kumar
Signed-off-by: Ran Wang
---
Change in v3:
- none
Change in v2:
Remove macro CONFIG_HAS_FSL_XHCI_USB and CONFIG_USB_XHCI_FSL
and
Signed-off-by: Ashish Kumar
Signed-off-by: Amrita Kumari
Signed-off-by: Ran Wang
---
Change in v3:
1.Move HAS_FSL_XHCI_USB and USB_XHCI_FSL define to other patch file.
Change in v2:
1.Adjust USB nodes position in
use Kconfig to select xhci accordingly.
Signed-off-by: Ran Wang
---
Change in v3:
New patch file.
drivers/usb/host/Kconfig | 6 ++
include/configs/ls1012afrdm.h | 1 -
include/configs/ls1012aqds.h | 1 -
include/configs/ls1012ardb.h | 1 -
Because COMFIG_DM_USB have been enabled and will not use it anymore.
Signed-off-by: Ran Wang
---
Change in v3:
New patch file.
include/configs/ls1012afrdm.h | 5 -
include/configs/ls1012aqds.h | 3 ---
include/configs/ls1012ardb.h | 4
Use Kconfig to select QE-HDLC and USB pin-mux.
Signed-off-by: Ran Wang
---
Change in v3:
New patch file.
arch/arm/cpu/armv8/fsl-layerscape/Kconfig | 7 +++
include/configs/ls1012afrdm.h | 4
include/configs/ls1012aqds.h | 4
Hi Peng,
On Tue, Oct 10, 2017 at 9:50 PM, Peng Fan wrote:
> When adding DM support, I have tested on my board. What issue do you see?
SD card is not detected, so I cannot load the zImage with mainline U-Boot.
Please test it using the latest U-Boot mainline.
Thanks
Memory allocated via malloc is not guaranteed to be zeroized.
So explicitly use calloc instead of malloc.
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Replaced malloc/memset with calloc
Changes for v3: Updated patch description
Changes for v4: Updated patch
On Wed, Oct 11, 2017 at 5:04 AM, Tom Rini wrote:
> On Tue, Oct 10, 2017 at 11:27:39AM +0200, Marek Vasut wrote:
>
>> Hi,
>>
>> I am considering offloading xhci maintainership to Bin .
>> Thoughts ?
>
> If Bin wants it, I have no objections.
>
Thanks for the offer. Glad I can
Hi Fabio,
> -Original Message-
> From: Fabio Estevam [mailto:fabio.este...@nxp.com]
> Sent: Wednesday, October 11, 2017 12:44 AM
> To: sba...@denx.de
> Cc: Peng Fan ; u-boot@lists.denx.de; Fabio Estevam
>
> Subject: [PATCH 2/2] mx6slevk: Remove
On 10/10/2017 02:22 PM, Rob Clark wrote:
Re-send of the patch series to get Shell.efi working, and almost get
SCT.efi (the UEFI test suite) working.
Since last time, I've updated to Heinrich's latest SetWatchdogTimer
patch (as of yesterday evening), and adressed review comments on the
three
On Sun, Oct 08, 2017 at 09:48:02PM +0300, Tuomas Tynkkynen wrote:
> The option is specified in Kconfig, but still a few config header files
> are overriding the choice by #undef'ing it. Re-sync the option with
> moveconfig to rid of the #undefs.
>
> Signed-off-by: Tuomas Tynkkynen
On Sun, Oct 08, 2017 at 09:48:01PM +0300, Tuomas Tynkkynen wrote:
> Having this as a 'default y' is rather annoying because it doesn't
> actually compile unless other options are defined in the board header:
>
> ../cmd/bootm.c: In function 'do_imls_nor':
> ../cmd/bootm.c:330:7: error:
On 10/10/2017 02:22 PM, Rob Clark wrote:
From: Leif Lindholm
Not complete, but enough for Shell.efi and SCT.efi. We'll implement the
rest as needed or once we have SCT running properly so there is a way to
validate the interface against the conformance test suite.
Hi, Tom.
The following changes since commit 37a7908137a8c904f43c83f3e6c269cd51bf6126:
ARM: dts: rmobile: Update DTS to match Linux 4.13 (2017-09-12 23:01:51 +0200)
are available in the git repository at:
git://git.denx.de/u-boot-sh.git rmobile
for you to fetch changes up to
On 10/10/2017 02:23 PM, Rob Clark wrote:
Shell.efi uses this, and supporting color attributes makes things look
nicer. Map the EFI fg/bg color attributes to ANSI escape sequences.
Not all colors have a perfect match, but spec just says "Devices
supporting a different number of text colors are
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Device tree for Stratix10 SoC
>
> Signed-off-by: Chin Liang See
> ---
> arch/arm/dts/Makefile| 3 +-
>
On Tue, Oct 10, 2017 at 6:28 PM, Heinrich Schuchardt wrote:
> On 10/10/2017 02:23 PM, Rob Clark wrote:
>>
>> These devices have small image size limits, so exclude EFI_LOADER to
>> help avoid exceeding limits.
>>
>> Signed-off-by: Rob Clark
>> ---
>>
On 10/10/2017 02:23 PM, Rob Clark wrote:
An event can be created with type==0, Shell.efi does this for an event
that is set when Ctrl-C is typed. So our current approach of having a
fixed set of timer slots, and determining which slots are unused by
type==0 doesn't work so well. But we don't
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Add mailbox support for Stratix SoC
>
> Signed-off-by: Ley Foon Tan
> Signed-off-by: Chin Liang See
> ---
>
On 10/10/2017 02:23 PM, Rob Clark wrote:
When we don't have a real device/image path, such as 'bootefi hello',
construct a mem-mapped device-path.
This fixes 'bootefi hello' after devicepath refactoring.
Fixes: 95c5553ea2 ("efi_loader: refactor boot device and loaded_image handling")
On 10/10/2017 02:23 PM, Rob Clark wrote:
These devices have small image size limits, so exclude EFI_LOADER to
help avoid exceeding limits.
Signed-off-by: Rob Clark
---
lib/efi_loader/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Oct 09, 2017 at 05:30:17PM -0600, Simon Glass wrote:
> Hi Tom,
>
> Sorry for the delay with v2.
>
>
> The following changes since commit 0d3aaa35b87573c229d65bc79050ab13f39d8ec2:
>
> Travis-CI: Fix microblaze and xilinx jobs (2017-10-07 15:54:18 -0400)
>
> are available in the git
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Add misc support such as EMAC and cpu info printout for Stratix SoC
>
> Signed-off-by: Chin Liang See
> ---
> arch/arm/mach-socfpga/Makefile
On Tue, Oct 10, 2017 at 11:27:39AM +0200, Marek Vasut wrote:
> Hi,
>
> I am considering offloading xhci maintainership to Bin .
> Thoughts ?
If Bin wants it, I have no objections.
--
Tom
signature.asc
Description: PGP signature
___
U-Boot mailing
Hi, all
This patch enables HDMI on CPU without VPU.
A similar patch for the mainline kernel:
https://patchwork.kernel.org/patch/9874831/
Tested on MCIMX6Q4AVT10AD.
Signed-off-by: Nikolay Petukhov
Cc: Stefano Babic sba...@denx.de
---
arch/arm/mach-imx/mx6/soc.c | 5
Recent discussions confirmed (what the code always assumed): the
Rockchip BROM always enters U-Boot with the stack-pointer valid
(i.e. the U-Boot startup code is running off the BROM stack).
We can thus replace the back-to-bootrom code (i.e. both the
save_boot_params and back_to_bootrom
Hello,
I ran into a problem with the JFFS2 filesystem driver implemented in U-Boot.
I've got a NAND device that has correctable ECC errors (corrected somewhere in
mtd/nand/nand_base.c).
The NAND driver tells the filesystem layer (jffs2_1pass.c) above that there
occurred correctable ECC errors
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Add pinmux driver support for Stratix SoC
>
> Signed-off-by: Chin Liang See
> ---
> arch/arm/mach-socfpga/Makefile | 2 +
>
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Add Reset Manager driver support for Stratix SoC
>
> Signed-off-by: Chin Liang See
> ---
> arch/arm/mach-socfpga/Makefile | 1 +
On Thu, Oct 5, 2017 at 8:07 AM, wrote:
> From: Chin Liang See
>
> Add Clock Manager driver support for Stratix SoC
>
> Signed-off-by: Chin Liang See
> --
> Changes in v2
> - Declared defines for constant value used
>
Last user of this option went away in commit:
fdc7718999 ("board: usb_a9263: Update to support DT and DM")
Signed-off-by: Tuomas Tynkkynen
---
drivers/spi/Makefile | 1 -
drivers/spi/atmel_dataflash_spi.c | 184 --
2
Last user of this option went away in commit:
fdc7718999 ("board: usb_a9263: Update to support DT and DM")
Signed-off-by: Tuomas Tynkkynen
---
README | 7 -
arch/arm/mach-at91/arm926ejs/at91sam9260_devices.c | 2 +-
Removal of the legacy DataFlash code turned genimg_get_image() into a
no-op. Drop all calls to it and the function itself.
Signed-off-by: Tuomas Tynkkynen
---
common/bootm.c | 3 ---
common/image-fdt.c | 3 ---
common/image.c | 27 ---
Last user of this option went away in commit:
fdc7718999 ("board: usb_a9263: Update to support DT and DM")
Signed-off-by: Tuomas Tynkkynen
---
cmd/nvedit.c | 3 +--
env/Kconfig | 15 ---
env/Makefile | 1 -
env/dataflash.c |
These patches remove:
CONFIG_ENV_IS_IN_DATAFLASH
CONFIG_ATMEL_DATAFLASH_SPI
CONFIG_HAS_DATAFLASH
Last user of these went away in July, in commit fdc77189994b2ac794862
("board: usb_a9263: Update to support DT and DM"). AFAICT their
replacements using DM + DT are:
Hi Jagan, Marek,
On 10/10/2017 16:08, Marek Vasut wrote:
> On 10/10/2017 04:04 PM, Jagan Teki wrote:
>> On Tue, Oct 10, 2017 at 7:10 PM, Marek Vasut wrote:
>>> On 10/10/2017 03:32 PM, Jagan Teki wrote:
On Tue, Oct 10, 2017 at 1:21 AM, Marek Vasut wrote:
>
On Tue, Oct 10, 2017 at 10:30:42PM +0530, Jagan Teki wrote:
> On Tue, Oct 10, 2017 at 10:26 PM, Antony Antony wrote:
> > On Tue, Oct 10, 2017 at 07:28:23PM +0530, Jagan Teki wrote:
> >> On Tue, Oct 10, 2017 at 7:15 PM, Antony Antony wrote:
> >> > Add
On Tue, Oct 10, 2017 at 07:21:57PM +0530, Jagan Teki wrote:
> On Tue, Oct 10, 2017 at 7:18 PM, Peter Robinson wrote:
> > Shouldn't we just be syncing changes to the DT from the kernel?
>
I guess syncing could possibly solve the problem! Kernel DTSI got the
compiltables I
On Tue, Oct 10, 2017 at 10:26 PM, Antony Antony wrote:
> On Tue, Oct 10, 2017 at 07:28:23PM +0530, Jagan Teki wrote:
>> On Tue, Oct 10, 2017 at 7:15 PM, Antony Antony wrote:
>> > Add initial DT for NanoPi NEO Plus2 by FriendlyARM
>> > - Allwinner quad core
On Tue, Oct 10, 2017 at 07:28:23PM +0530, Jagan Teki wrote:
> On Tue, Oct 10, 2017 at 7:15 PM, Antony Antony wrote:
> > Add initial DT for NanoPi NEO Plus2 by FriendlyARM
> > - Allwinner quad core H5 Cortex A53 with an ARM Mali-450MP GPU
> > - 1 GB DDR3 RAM
> > - 8GB eMMC
> To start porting I was planning to copy all the files of the board
minnowmax and rename it with the name of our product.
> I saw that minnowmax use FSP 1.0 exactly like Broadwell-DE. I hope that
helps.
You might want to join Coreboot mailing list. I am 1000% sure this will
help you far beyond
While having DM driver is a good thing, currently this defconfig
is completely broken in a way that SD cards can not even be detected.
Remove some of the DM drivers to avoid the regression for now
and allow booting a kernel stored in the SD card again.
Re-adding the DM drivers can be revisited
We should call gpio_request() prior to reading the GPIO value.
Signed-off-by: Fabio Estevam
---
Applied on top of:
https://patchwork.ozlabs.org/patch/820477/
and
https://patchwork.ozlabs.org/patch/820298/
board/freescale/mx6slevk/mx6slevk.c | 3 +++
1 file changed, 3
This makes gcc no longer expect an out-of-line version of the
functions being present elsewhere.
This fixes a failure to build on several marvell targets with gcc-7 on
Debian:
https://bugs.debian.org/877963
Signed-off-by: Adrian Bunk
Signed-off-by: Vagrant Cascadian
> Correct a mistake in the part number handling of
> 16a73b249d138fedeb188710533902ed7aac1ddc and only increment part once
> per loop.
>
> Signed-off-by: Jonathan Gray
> Tested-by: Peter Robinson
Thanks, applied to efi-next
Alex
On 10/10/2017 06:50 AM, Patrick DELAUNAY wrote:
Hi Stephen,
-Original Message-
From: Stephen Warren [mailto:swar...@wwwdotorg.org]
On 10/09/2017 01:47 AM, Patrick Delaunay wrote:
- copy the reference gpt binary file as it is modified during the test
to avoid issue if the test
For the RK3188, the BROM will attempt to load up the first stage
image (SPL for the RK3188) in two steps: first 1KB to offset 0x800
in the SRAM and then the remainder to offset 0xc00 in the SRAM.
It always enters at 0x804, though.
With this changeset, the RK3188 boot removes the TPL (stub) stage
There still are a few CONFIG_SPL_* options selected using defines from
rk3188_common.h instead of via Kconfig. This migrates those over to
Kconfig.
Signed-off-by: Philipp Tomsich
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in
The BROM supports forcing it to enter download-mode, if an appropriate
result/cmd-word is returned to it. There already is a series to
support this in review, so this prepares the (newly C-version) of the
back-to-bootrom code to accept a cmd to passed on to the BROM.
All the existing call-sites
With all targets converted to generate prepadded images, this removes
the spl_boot0 field from our config structure and removes the unused
code-path (for images that are not prepadded): i.e. spl_boot0 is now
implied as 'true' and the code is specialised by removing the other
case.
Signed-off-by:
Some Rockchip BROM versions (e.g. the RK3188 and RK3066) first read 1KB data
from NAND into SRAM and executes it. Then, following a return to bootrom, the
BROM loads additional code to SRAM (not overwriting the first block read) and
reenters at the same address as the first time.
To support
The back-to-bootrom implementation for Rockchip has always relied on
the stack-pointer being valid on entry, so there was little reason to
have this as an assembly implementation.
This provides a new C-only implementation of save_boot_params and
back_to_bootrom (relying on setjmp/longjmp) and
The save_boot_params_ret() prototype (for those of us, that have a
valid SP on entry and can implement save_boot_params() in C), was
previously only defined for !defined(CONFIG_ARM64).
This moves the declaration to a common block to ensure the prototype
is available to everyone that might need
The previous setjmp-implementation (as a static inline function that
contained an 'asm volatile' sequence) was extremely fragile: (some
versions of) GCC optimised the set of registers. One critical example
was the removal of 'r9' from the clobber list, if -ffixed-reg9 was
supplied.
To increase
This updates the BCM235xx boot0-hook to the updated boot0 semantics
by emitting _start and the vector table before the boot0 hook (as
was the case before).
Signed-off-by: Philipp Tomsich
Version-changes: 5
- ran 'whitespace-cleanup'
---
Changes in v5:
With the boot0-hook inserting the additional padding to receive our
SPL magic, the SPL_TEXT_BASE can be aligned again.
Signed-off-by: Philipp Tomsich
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
As no '.type' was set for save_boot_params_ret in start.S, binutils
did not track whether it was emitted as A32 or T32. By properly
marking save_boot_params_ret as a potential function entry, we can
make sure that the compiler will insert the appropriate instructions
for branching to
With the updated boot0 semantics (i.e. giving the boot0-hook control
over when and where the vector table is emitted), the boot0-hook for
the socfpga needs to be adjusted.
Signed-off-by: Philipp Tomsich
---
Changes in v5: None
Changes in v4: None
Changes
This updates the BCM281xx boot0-hook to the updated boot0 semantics
by emitting _start and the vector table before the boot0 hook (as
was the case before).
Signed-off-by: Philipp Tomsich
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Rockchip SoCs bootrom design is like this:
- First 2KB or 4KB internal memory is for bootrom stack and heap;
- Then the first 4-byte suppose to be a TAG like 'RK33';
- The the following memory address end with '0004' is the first
instruction load and running by bootrom;
Let's use the boot0 hook
From: Kever Yang
The '_start' is using as vector table base address, and will write
to VBAR register, so it needs to be aligned to 0x20 for armv7.
Signed-off-by: Kever Yang
[Updated to current code base:]
Signed-off-by: Philipp Tomsich
From: Kever Yang
Enable the spl_boot0 in SPL and use the pre-padding TAG memory,
the mkimage do not need to pad it but only need to replace the value
with correct TAG value.
Signed-off-by: Kever Yang
[Updated:]
Signed-off-by: Philipp
From: Kever Yang
After we use boot0 hook, we can use offset '000' instead of '004' as
SPL_TEXT_BASE.
Signed-off-by: Kever Yang
[Updated tag in commit summary:]
Signed-off-by: Philipp Tomsich
---
The boot0 hook on ARM does not insert its payload before the vector
table. This is both a mismatch with thec comment above it and
contradict usage of the boot0 hook on ARM64.
To fix this (and unify the semantics for ARM and ARM64), we change the
boot0-hook semantics on ARM to match those on
On 10/10/2017 12:45 PM, Faiz Abbas wrote:
> Hi Marek,
>
> On Tuesday 10 October 2017 01:30 PM, Marek Vasut wrote:
>> On 10/10/2017 07:48 AM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>
>> Hi,
>>
>> [...]
>>
> - dwc3_flush_cache((uintptr_t)trb, sizeof(*trb));
> +
On 10/10/2017 04:04 PM, Jagan Teki wrote:
> On Tue, Oct 10, 2017 at 7:10 PM, Marek Vasut wrote:
>> On 10/10/2017 03:32 PM, Jagan Teki wrote:
>>> On Tue, Oct 10, 2017 at 1:21 AM, Marek Vasut wrote:
Add support for the DHCOM i.MX6 PDK board. This board has:
On Tue, Oct 10, 2017 at 7:10 PM, Marek Vasut wrote:
> On 10/10/2017 03:32 PM, Jagan Teki wrote:
>> On Tue, Oct 10, 2017 at 1:21 AM, Marek Vasut wrote:
>>> Add support for the DHCOM i.MX6 PDK board. This board has:
>>> - FEC ethernet
>>> - EHCI USB host
>>> - 3x
On Tue, Oct 10, 2017 at 7:15 PM, Antony Antony wrote:
> Add initial DT for NanoPi NEO Plus2 by FriendlyARM
> - Allwinner quad core H5 Cortex A53 with an ARM Mali-450MP GPU
> - 1 GB DDR3 RAM
> - 8GB eMMC flash (Samsung KLM8G1WEPD-B031)
> - micro SD card slot
> - Gigabit
On Tue, Oct 10, 2017 at 7:18 PM, Peter Robinson wrote:
> Shouldn't we just be syncing changes to the DT from the kernel?
And add last merge commit details on commit message.
thanks!
--
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream
Shouldn't we just be syncing changes to the DT from the kernel?
On Tue, Oct 10, 2017 at 2:35 PM, Antony Antony wrote:
> add more specific, Allwinner H5 SoC, compaitable to mmc0,1,2
> current one comes from sun8i-h3.dtsi
> compatible = "allwinner,sun7i-a20-mmc",
Add initial DT for NanoPi NEO Plus2 by FriendlyARM
- Allwinner quad core H5 Cortex A53 with an ARM Mali-450MP GPU
- 1 GB DDR3 RAM
- 8GB eMMC flash (Samsung KLM8G1WEPD-B031)
- micro SD card slot
- Gigabit Ethernet (external RTL8211E-VB-CG chip)
- 802.11 b/g/n WiFi, Bluetooth 4.0 (Ampak AP6212A
On 10/10/2017 03:32 PM, Jagan Teki wrote:
> On Tue, Oct 10, 2017 at 1:21 AM, Marek Vasut wrote:
>> Add support for the DHCOM i.MX6 PDK board. This board has:
>> - FEC ethernet
>> - EHCI USB host
>> - 3x SDMMC
>>
>> Signed-off-by: Marek Vasut
>> Cc: Stefano Babic
add more specific, Allwinner H5 SoC, compaitable to mmc0,1,2
current one comes from sun8i-h3.dtsi
compatible = "allwinner,sun7i-a20-mmc", "allwinner,sun5i-a13-mmc";
Signed-off-by: Antony Antony
---
arch/arm/dts/sun50i-h5.dtsi | 12
1 file changed, 12
On Tue, Oct 10, 2017 at 1:21 AM, Marek Vasut wrote:
> Add support for the DHCOM i.MX6 PDK board. This board has:
> - FEC ethernet
> - EHCI USB host
> - 3x SDMMC
>
> Signed-off-by: Marek Vasut
> Cc: Stefano Babic
> ---
> V2: Use get_cpu_type() and
Hi Stephen,
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
>
> On 10/09/2017 01:47 AM, Patrick Delaunay wrote:
> > - copy the reference gpt binary file as it is modified during the test
> >to avoid issue if the test fail: the test always restart with clean
On Tue, Oct 10, 2017 at 3:55 AM, Jonathan Gray wrote:
> When searching for partitions don't stop if a partition is not present
> for a given partition number as there may be valid partitions after.
>
> Search for up to MAX_SEARCH_PARTITIONS matching the other callers of
>
On Tue, Oct 10, 2017 at 11:32 AM, Jonathan Gray wrote:
> Correct a mistake in the part number handling of
> 16a73b249d138fedeb188710533902ed7aac1ddc and only increment part once
> per loop.
>
> Signed-off-by: Jonathan Gray
Tested-by: Peter Robinson
This fixes an issue with OpenBSD's bootloader, and I think should also
fix a similar issue with grub2 on legacy devices. In the legacy case
we were creating disk objects for the partitions, but not also the
parent device.
Reported-by: Jonathan Gray
Signed-off-by: Rob Clark
Hi Simon,
Thanks for the info. I already have all the necessary blobs from the current
working implementation with Coreboot + U-Boot: FPS, ME, Microcode, Flash
Descriptor, VGA Rom.
To start porting I was planning to copy all the files of the board minnowmax
and rename it with the name of our
Shell.efi uses this, and supporting color attributes makes things look
nicer. Map the EFI fg/bg color attributes to ANSI escape sequences.
Not all colors have a perfect match, but spec just says "Devices
supporting a different number of text colors are required to emulate the
above colors to the
We need the _EX version for SCT.. and we need to wire up the
corresponding objects in the systab properly, as well as dealing
with the console_in object advertising multiple protocols.
Signed-off-by: Rob Clark
---
include/efi_api.h | 61 +-
An event can be created with type==0, Shell.efi does this for an event
that is set when Ctrl-C is typed. So our current approach of having a
fixed set of timer slots, and determining which slots are unused by
type==0 doesn't work so well. But we don't have any particularly good
reason to have a
These devices have small image size limits, so exclude EFI_LOADER to
help avoid exceeding limits.
Signed-off-by: Rob Clark
---
lib/efi_loader/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/Kconfig b/lib/efi_loader/Kconfig
index
From: Heinrich Schuchardt
The watchdog is initialized with a 5 minute timeout period.
It can be reset by SetWatchdogTimer.
It is stopped by ExitBoottimeServices.
Signed-off-by: Heinrich Schuchardt
---
cmd/bootefi.c | 1 +
In some cases, it is quite useful to have (for example) EFI on screen
but u-boot on serial port.
This adds two new optional environment variables, "efiin" and "efiout",
which can be used to set EFI console input/output independently of
u-boot's input/output. If unset, EFI console will default to
When we don't have a real device/image path, such as 'bootefi hello',
construct a mem-mapped device-path.
This fixes 'bootefi hello' after devicepath refactoring.
Fixes: 95c5553ea2 ("efi_loader: refactor boot device and loaded_image handling")
Signed-off-by: Rob Clark
---
From: Leif Lindholm
Enough implementation of the following protocols to run Shell.efi and
SCT.efi:
EfiHiiConfigRoutingProtocolGuid
EfiHiiDatabaseProtocol
EfiHiiStringProtocol
We'll fill in the rest once SCT is running properly so we can validate
the
From: Leif Lindholm
Not complete, but enough for Shell.efi and SCT.efi.
Initial skeleton written by Leif, and then implementation by myself.
Cc: Leif Lindholm
Signed-off-by: Rob Clark
---
include/efi_api.h
From: Leif Lindholm
Not complete, but enough for Shell.efi and SCT.efi. We'll implement the
rest as needed or once we have SCT running properly so there is a way to
validate the interface against the conformance test suite.
Initial skeleton written by Leif, and then
Re-send of the patch series to get Shell.efi working, and almost get
SCT.efi (the UEFI test suite) working.
Since last time, I've updated to Heinrich's latest SetWatchdogTimer
patch (as of yesterday evening), and adressed review comments on the
three new sets of protocols added. Part of that, to
Hi David,
On Thu, Oct 5, 2017 at 8:46 AM, Fabio Estevam wrote:
> From: Sven-Ola Tuecke
>
> We have at least a minor count of boards, that failed to re-initialize
> PCI express in the Linux kernel. Typical failure rate is 20% on affected
>
Hi,
On Tuesday 10 October 2017 11:07 AM, Faiz Abbas wrote:
> +Kishon
>
> On Friday 06 October 2017 05:03 PM, Faiz Abbas wrote:
>> Hi,
>>
>> On Thursday 05 October 2017 04:57 PM, Marek Vasut wrote:
>>> On 10/04/2017 03:11 PM, Faiz Abbas wrote:
Hi,
On Wednesday 04 October 2017 06:01
Hi Jagan,
On Mon, Oct 9, 2017 at 3:05 PM, Jagan Teki wrote:
> I didn't dig much, but the i.MX6UL case has rebooting with DM_MMC for
> both SPL and U-Boot proper.
Looks like the same issue I saw with mx6q, which has been fixed by this commit:
Hi Philipp:
On 2017年10月10日 18:50, Dr. Philipp Tomsich wrote:
On 10 Oct 2017, at 11:22, Andy Yan > wrote:
Hi:
On 2017年10月10日 17:01, Andy Yan wrote:
Hi Philipp:
On 2017年10月07日 03:28, Philipp Tomsich wrote:
Some Rockchip BROM
> On 10 Oct 2017, at 11:22, Andy Yan wrote:
>
> Hi:
>
>
> On 2017年10月10日 17:01, Andy Yan wrote:
>> Hi Philipp:
>>
>> On 2017年10月07日 03:28, Philipp Tomsich wrote:
>>> Some Rockchip BROM versions (e.g. the RK3188 and RK3066) first read 1KB data
>>> from NAND into SRAM
Hi Marek,
On Tuesday 10 October 2017 01:30 PM, Marek Vasut wrote:
> On 10/10/2017 07:48 AM, Kishon Vijay Abraham I wrote:
>> Hi,
>
> Hi,
>
> [...]
>
- dwc3_flush_cache((uintptr_t)trb, sizeof(*trb));
+ dwc3_flush_cache((uintptr_t)dwc->ep0_trb_addr, sizeof(*trb) *
On Tue, Oct 10, 2017 at 10:01:46AM +0200, Alexander Graf wrote:
> > When searching for partitions don't stop if a partition is not present
> > for a given partition number as there may be valid partitions after.
> >
> > Search for up to MAX_SEARCH_PARTITIONS matching the other callers of
> >
> -Original Message-
> From: York Sun
> Sent: Tuesday, October 03, 2017 11:32 PM
> To: Xiaowei Bao ; Mingkai Hu
>
> Cc: u-boot@lists.denx.de
> Subject: Re: [PATCH] Powerpc: Make pcie link state judge more specific
>
> On 09/24/2017 08:44 PM, Bao
Correct a mistake in the part number handling of
16a73b249d138fedeb188710533902ed7aac1ddc and only increment part once
per loop.
Signed-off-by: Jonathan Gray
---
lib/efi_loader/efi_disk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/efi_loader/efi_disk.c
> -Original Message-
> From: Bao Xiaowei [mailto:xiaowei@nxp.com]
> Sent: Monday, September 25, 2017 11:27 AM
> To: M.h. Lian ; Z.q. Hou ;
> Mingkai Hu ; York Sun ;
> hamish.mar...@alliedtelesis.co.nz;
1 - 100 of 111 matches
Mail list logo