Real marketing name of the board was recently updated so
to accommodate that change renaming the board and all
related to it.
Signed-off-by: Alexey Brodkin
---
arch/arc/Kconfig | 6 +++---
arch/arc/dts/Makefile | 2 +-
arch/arc/dts/{emdk.dts
Updates the device tree file from the the Linux tree as of v4.19-rc4,
exactly Linux commit:
commit 7876320f8880 (tag: v4.19-rc4)
Author: Linus Torvalds
Date: Sun Sep 16 11:52:37 2018 -0700
Linux 4.19-rc4
Signed-off-by: Vasily Khoruzhick
Acked-by: Maxime Ripard
Tested-by: Maxime Ripard
Both GPIOs are optional, so we shouldn't fail if any is missing.
Without this fix reset is not deasserted if sleep GPIO is missing.
Signed-off-by: Vasily Khoruzhick
Acked-by: Maxime Ripard
Tested-by: Maxime Ripard
Cc: Vagrant Cascadian
---
drivers/video/bridge/video-bridge-uclass.c | 16 +
Allwinner A64 has a I2C controller, which is in the R_ MMIO zone and has
two groups of pinmuxes on PL bank, so it's called R_I2C.
Add support for this I2C controller and the pinmux which doesn't conflict
with RSB.
Signed-off-by: Vasily Khoruzhick
Acked-by: Maxime Ripard
Tested-by: Maxime Ripard
Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
USB-connected touchpad and an eDP LCD panel connected via a RGB-eDP
bridge from Analogix.
Signed-off-by: Vasily Khoruzhick
Acked-by: Maxime Ripard
Tested-by: Maxime Ripard
Cc: Vagrant Cascadian
---
arch/arm/dts/Makefile
A64 and H6 support automatic delay calibration and Linux driver uses it
instead of hardcoded delays. Add support for it to u-boot driver.
Fixes eMMC instability on Pinebook
Signed-off-by: Vasily Khoruzhick
Acked-by: Maxime Ripard
Tested-by: Maxime Ripard
Cc: Vagrant Cascadian
---
arch/arm/in
This series adds support for the Pinebook, an allwinner A64 laptop
produced by Pine64. It also syncs sun50i-a64.dtsi with linux,
adds support for mmc delay calibration, R_I2C controller,
and addresses the issue with activating video bridge when any of
GPIOs is missing.
v2: - sync sun50i-a64.dtsi w
On Wed, Oct 17, 2018 at 10:43:22AM +0200, Alexander Graf wrote:
>
>
> On 17.10.18 09:32, AKASHI Takahiro wrote:
> > With this patch applied, we will be able to selectively execute
> > an EFI application by specifying a load option, say "-1" for Boot0001,
> > "-2" for Boot0002 and so on.
> >
> >
On Wed, Oct 17, 2018 at 10:06:58AM +0200, Alexander Graf wrote:
>
>
> On 17.10.18 09:32, AKASHI Takahiro wrote:
> > This patch set is a collection of patches to enhance efi user interfaces
> > /commands. It will help improve user experience on efi boot and make it
> > more usable without edk2's s
On Wednesday, October 17, 2018 5:23:04 PM PDT André Przywara wrote:
> On 10/17/18 6:09 AM, Vasily Khoruzhick wrote:
>
> Hi,
>
> > Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
> > USB-connected touchpad and an eDP LCD panel connected via a RGB-eDP
> > bridge from Analogix.
On Tue, Oct 16, 2018 at 03:21:10PM +0200, Alexander Graf wrote:
>
>
> On 12.10.18 07:09, AKASHI Takahiro wrote:
> > This is a preparatory patch so that USB boot will be supported
> > in distro boot script by default.
> >
> > Signed-off-by: AKASHI Takahiro
>
> How about something like this inst
On Tue, Oct 16, 2018 at 03:15:13PM +0200, Alexander Graf wrote:
>
>
> On 12.10.18 07:07, AKASHI Takahiro wrote:
> > The current scenario for default UEFI booting, scan_dev_for_efi, has
> > several issues:
> > * invoke 'bootmgr' only if BOOTEFI_NAME binary does exit even though
> > 'bootmgr' can
On 10/17/18 6:09 AM, Vasily Khoruzhick wrote:
Hi,
> Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
> USB-connected touchpad and an eDP LCD panel connected via a RGB-eDP
> bridge from Analogix.
>
> Signed-off-by: Vasily Khoruzhick
> ---
> arch/arm/dts/Makefile
On 10/17/18 6:09 AM, Vasily Khoruzhick wrote:
> Allwinner A64 has a I2C controller, which is in the R_ MMIO zone and has
> two groups of pinmuxes on PL bank, so it's called R_I2C.
>
> Add support for this I2C controller and the pinmux which doesn't conflict
> with RSB.
>
> Signed-off-by: Vasily K
On 10/17/18 6:09 AM, Vasily Khoruzhick wrote:
> Both GPIOs are optional, so we shouldn't fail if any is missing. Without
> this fix reset is not deasserted when sleep GPIO is missing.
>
> Signed-off-by: Vasily Khoruzhick
That looks much better now, thanks.
One small thing:
> ---
> drivers/vide
On 10/17/18 6:09 AM, Vasily Khoruzhick wrote:
> A64 supports automatic delay calibration and Linux driver uses it
> instead of hardcoded delays. Add support for it to u-boot driver.
>
> Fixes eMMC instability on Pinebook
>
> Signed-off-by: Vasily Khoruzhick
> ---
> arch/arm/include/asm/arch-sun
On 10/17/18 4:40 PM, Vasily Khoruzhick wrote:
> On Wednesday, October 17, 2018 8:18:41 AM PDT Andre Przywara wrote:
>> On Tue, 16 Oct 2018 22:09:30 -0700
>> Vasily Khoruzhick wrote:
>>
>> Hi,
>>
>>> Updates the device tree file from the the Linux tree as of v4.19-rc4,
>>
>>> exactly Linux commit:
Hi Alexander,
On Tue, 16 Oct 2018 15:04:26 +0200
Alexander Graf wrote:
...
> >
> >> Glancing at cmd/pxe.c,
> >> there is a problem though, in that if ${fdt_addr_r} were defined,
> >> a PXE file using the FDTDIR directive would attempt loading a dtb
> >> file named "-qemu-arm.dtb" instead of f
Simon Goldschmidt schrieb am Mi., 10.
Okt. 2018, 22:16:
> On Wed, Oct 10, 2018 at 10:03 PM Simon Glass wrote:
> >
> > Hi Simon,
> >
> > On 10 October 2018 at 07:28, Simon Goldschmidt
> > wrote:
> > >
> > > + Marek (as he commented on the original patch
> http://patchwork.ozlabs.org/patch/955765
Fix some typos in comments.
Signed-off-by: Heinrich Schuchardt
---
lib/efi_loader/efi_device_path.c | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/lib/efi_loader/efi_device_path.c b/lib/efi_loader/efi_device_path.c
index adb9938d45..49bbdb72af 10064
On Wed, Oct 17, 2018 at 09:24:34AM +0200, Alexander Graf wrote:
> Hi Tom,
>
> This is my current patch queue for efi for inclusion into 2018.11. Please
> pull.
>
> Alex
>
>
> The following changes since commit 2364b70c87a8d4ac327a44161df32d2c8e209545:
>
> Merge branch 'master' of git://gi
Hi Alex,
On 16 October 2018 at 08:48, Alexander Graf wrote:
>
>
>
> On 29.09.18 20:29, Simon Glass wrote:
> > Hi Alex,
> >
> > On 23 September 2018 at 23:34, Alexander Graf wrote:
> >>
> >>
> >> On 24.09.18 00:47, Simon Glass wrote:
> >>> On my Ubuntu 18.04.1 machine two driver-model bus tests h
On 10/17/2018 07:37 PM, Alexander Graf wrote:
>
>
> On 17.10.18 19:05, Heinrich Schuchardt wrote:
>> When an operating system started via bootefi tries to reset or power off
>> this is done by calling the EFI runtime ResetSystem(). On most ARMv8 system
>> the actual reset relies on PSCI. Dependin
On 17.10.18 19:05, Heinrich Schuchardt wrote:
> When an operating system started via bootefi tries to reset or power off
> this is done by calling the EFI runtime ResetSystem(). On most ARMv8 system
> the actual reset relies on PSCI. Depending on whether the PSCI firmware
> resides the hypervisor
On Wed, 17 Oct 2018 10:09:55 -0700
Vasily Khoruzhick wrote:
> On Wed, Oct 17, 2018 at 9:54 AM Andre Przywara
> wrote:
> >
> > On Wed, 17 Oct 2018 17:29:58 +0200
> > Maxime Ripard wrote:
> >
> > Hi,
> >
> > > On Wed, Oct 17, 2018 at 04:18:41PM +0100, Andre Przywara wrote:
> > > > On Tue, 16
On 10/16/18 8:33 PM, Bin Meng wrote:
On Wed, Oct 17, 2018 at 7:01 AM Bin Meng wrote:
Hi Stephen,
On Wed, Oct 17, 2018 at 12:27 AM Stephen Warren wrote:
On 10/15/18 5:43 PM, Bin Meng wrote:
Hi Stephen,
On Tue, Oct 16, 2018 at 6:43 AM Stephen Warren wrote:
On 10/15/18 3:53 PM, Stephen W
On Wed, Oct 17, 2018 at 9:54 AM Andre Przywara wrote:
>
> On Wed, 17 Oct 2018 17:29:58 +0200
> Maxime Ripard wrote:
>
> Hi,
>
> > On Wed, Oct 17, 2018 at 04:18:41PM +0100, Andre Przywara wrote:
> > > On Tue, 16 Oct 2018 22:09:30 -0700
> > > Vasily Khoruzhick wrote:
> > >
> > > Hi,
> > >
> > > >
When an operating system started via bootefi tries to reset or power off
this is done by calling the EFI runtime ResetSystem(). On most ARMv8 system
the actual reset relies on PSCI. Depending on whether the PSCI firmware
resides the hypervisor (EL2) or in the secure monitor (EL3) either an HVC
or a
On 10/16/18 20:06, Xiaoliang Yang wrote:
> Hi York,
>
> The old version of this patch is: http://patchwork.ozlabs.org/patch/918957/
> There is a little mistake about LSCH3 not support for imx-watchdog in old
> version patch, I have fixed it.
> If there is a need to rewrite CONFIG_IMX_WATCHDOG to
On Wed, 17 Oct 2018 17:29:58 +0200
Maxime Ripard wrote:
Hi,
> On Wed, Oct 17, 2018 at 04:18:41PM +0100, Andre Przywara wrote:
> > On Tue, 16 Oct 2018 22:09:30 -0700
> > Vasily Khoruzhick wrote:
> >
> > Hi,
> >
> > > Updates the device tree file from the the Linux tree as of
> > > v4.19-rc4,
On Wednesday, October 17, 2018 8:18:41 AM PDT Andre Przywara wrote:
> On Tue, 16 Oct 2018 22:09:30 -0700
> Vasily Khoruzhick wrote:
>
> Hi,
>
> > Updates the device tree file from the the Linux tree as of v4.19-rc4,
>
> > exactly Linux commit:
> Does this work easily without syncing the .dts fi
On Wednesday, October 17, 2018 8:22:51 AM PDT Jernej Škrabec wrote:
> Hi!
>
> Dne sreda, 17. oktober 2018 ob 17:13:42 CEST je Vasily Khoruzhick
napisal(a):
> > On Tuesday, October 16, 2018 10:09:32 PM PDT Vasily Khoruzhick wrote:
> > > Pinebook is a laptop produced by Pine64, with USB-connected k
On Wed, Oct 17, 2018 at 04:18:41PM +0100, Andre Przywara wrote:
> On Tue, 16 Oct 2018 22:09:30 -0700
> Vasily Khoruzhick wrote:
>
> Hi,
>
> > Updates the device tree file from the the Linux tree as of v4.19-rc4,
> > exactly Linux commit:
>
> Does this work easily without syncing the .dts files
Hi!
Dne sreda, 17. oktober 2018 ob 17:13:42 CEST je Vasily Khoruzhick napisal(a):
> On Tuesday, October 16, 2018 10:09:32 PM PDT Vasily Khoruzhick wrote:
> > Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
> > USB-connected touchpad and an eDP LCD panel connected via a RGB-eD
From: Denis Zalevskiy
If there is an I2C mux, current bus should be switched before
manipulating with I2C.
Signed-off-by: Denis Zalevskiy
Signed-off-by: Fabien Lahoudere
---
drivers/bootcount/Kconfig | 15 -
drivers/bootcount/bootcount_i2c.c | 71 ++
From: Denis Zalevskiy
u-boot's ext3/4 write/modify functionality sometimes corrupts
filesystem in the case if it requires recovery (e.g. after unexpected
shutdown) and we want to avoid the only filesystem modification we
have - bootcounter writing. So, bootcounter will be stored in the EEPROM
whe
From: Denis Zalevskiy
Use standard configuration logic to define EEPROM constants.
Names are based on VPD_EEPROM_ prefix because EEPROM_ is already
used by i2c_eeprom driver.
Signed-off-by: Denis Zalevskiy
Signed-off-by: Fabien Lahoudere
---
board/ge/bx50v3/Kconfig | 2 ++
board/ge/bx50v
From: Denis Zalevskiy
Bootcount driver should verify size against the maximum available space.
New configuration parameter adds this capability and keeps backward
compatibility by providing default value.
Signed-off-by: Denis Zalevskiy
Signed-off-by: Fabien Lahoudere
---
drivers/bootcount/Kco
From: Denis Zalevskiy
Merge functionality duplicated in bx50v3 and mx53ppd: the logic
is the same except that process_vpd is called at different phases.
Also read_vpd could end up in error, so there is no VPD data in this
case - it shouldn't be processed.
Signed-off-by: Denis Zalevskiy
Signed-o
From: Michal Hrusecky
Add path containing board name (if available) to the list of paths tried via
PXE by default. Some SoC families are quite diverse and sometimes it makes
sense to have special image just for a specific boards.
Signed-off-by: Michal Hrusecky
---
cmd/pxe.c | 3 +++
1 file cha
GE boards need bootcount set in EEPROM instead of file to avoid some issues.
This series replace v2 sent by Sebastian Reichel on 2018-07-20.
Changes since v2:
- Patches have been rebased to apply correctly on master.
- Remove a build time warning
- Remove checkpatch.pl warning
Denis Zalevs
From: Denis Zalevskiy
The bus is statically defined, so remove redundant parameters
from read_vpd() for PPD and Bx50v3.
Signed-off-by: Denis Zalevskiy
Signed-off-by: Fabien Lahoudere
---
board/ge/bx50v3/bx50v3.c | 6 +++---
board/ge/mx53ppd/mx53ppd.c | 6 +++---
2 files changed, 6 insertion
On 16. 10. 18 17:10, Alexander Graf wrote:
>
>
> On 16.10.18 16:57, Michal Simek wrote:
>> On 16.10.2018 16:55, Alexander Graf wrote:
>>>
>>>
>>> On 16.10.18 16:51, Michal Simek wrote:
On 16.10.2018 16:23, Alexander Graf wrote:
>
...
>> +#define ENV_MEM_LAYOUT_SETTINGS
Hi York,
The old version of this patch is: http://patchwork.ozlabs.org/patch/918957/
There is a little mistake about LSCH3 not support for imx-watchdog in old
version patch, I have fixed it.
If there is a need to rewrite CONFIG_IMX_WATCHDOG to Kconfig file, I will pull
a new patch to do this. It
On Tue, 16 Oct 2018 22:09:30 -0700
Vasily Khoruzhick wrote:
Hi,
> Updates the device tree file from the the Linux tree as of v4.19-rc4,
> exactly Linux commit:
Does this work easily without syncing the .dts files as well?
> commit 7876320f8880 (tag: v4.19-rc4)
> Author: Linus Torvalds
> Date:
On Tuesday, October 16, 2018 10:09:32 PM PDT Vasily Khoruzhick wrote:
> Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
> USB-connected touchpad and an eDP LCD panel connected via a RGB-eDP
> bridge from Analogix.
>
> Signed-off-by: Vasily Khoruzhick
+CC Jernej
> ---
> ar
Hi,
Dne sreda, 17. oktober 2018 ob 17:03:23 CEST je Vasily Khoruzhick napisal(a):
> On Tuesday, October 16, 2018 10:09:30 PM PDT Vasily Khoruzhick wrote:
> > Updates the device tree file from the the Linux tree as of v4.19-rc4,
> > exactly Linux commit:
> >
> > commit 7876320f8880 (tag: v4.19-rc4
On Tuesday, October 16, 2018 10:09:30 PM PDT Vasily Khoruzhick wrote:
> Updates the device tree file from the the Linux tree as of v4.19-rc4,
> exactly Linux commit:
>
> commit 7876320f8880 (tag: v4.19-rc4)
> Author: Linus Torvalds
> Date: Sun Sep 16 11:52:37 2018 -0700
>
> Linux 4.19-rc4
On Tue, Oct 16, 2018 at 10:09:32PM -0700, Vasily Khoruzhick wrote:
> Pinebook is a laptop produced by Pine64, with USB-connected keyboard,
> USB-connected touchpad and an eDP LCD panel connected via a RGB-eDP
> bridge from Analogix.
>
> Signed-off-by: Vasily Khoruzhick
> ---
> arch/arm/dts/Makef
Hei hei,
while setting up U-Boot for a new board, I read doc/README.distro and tried to
follow it for making things smooth with standard distributions. The document
mentions the so called "Boot Loader Specification" [1] as follows:
> This is roughly
> as specified at:
>
> http://www.freedeskto
Hi Stefan
Sorry for top-posting.
Why can't we read SFDP parameters from flash and auto-detect 3-byte/4-byte
addressing mode?
Using address width information we can support both types of flash i.e. flashes
supporting 3-byte addressing mode as well as flashes supporting 4-byte
addressing mode.
Add functionality to read SFDP parameters in fsl_qspi driver.
Also, use the address width information from SFDP to enable
flash access above 16 MB.
Introduce a way to access parent structure by adding pointer
to struct spi_slave in struct fsl_qspi_priv.
Signed-off-by: Rajat Srivastava
---
drive
Signed-off-by: Rajat Srivastava
---
drivers/mtd/spi/spi_flash_ids.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_ids.c
index ad0a0c8150..db4a93c7f5 100644
--- a/drivers/mtd/spi/spi_flash_ids.c
+++ b/drivers/mtd/s
Add support for JESD216 rev B standard JEDEC Serial
Flash Discoverable Parameters (SFDP) tables to
dynamically initialize flash size, page size and
address width of the flash. More parameters can be
added as per requirement.
Already existing method for parsing these parameters
are not deprecated, w
Add functionality to read and parse SFDP parameters to auto-detect
flash size, page size and address width of flash. This enables
flash access above 16MB using 4-byte addressing mode.
Add driver support to get SFDP information of flash and use it to
access flash above 16MB.
Enable reading and par
On 10/17/2018 12:46 PM, Heinrich Schuchardt wrote:
> On 10/17/2018 09:32 AM, AKASHI Takahiro wrote:
>> Factor out efi_set_bootdev() and extract efi_dp_from_name().
>> This function will be used to set a boot device in efishell command.
>>
>> Signed-off-by: AKASHI Takahiro
>> ---
>> cmd/bootefi.c
On 10/17/2018 09:32 AM, AKASHI Takahiro wrote:
> Factor out efi_set_bootdev() and extract efi_dp_from_name().
> This function will be used to set a boot device in efishell command.
>
> Signed-off-by: AKASHI Takahiro
> ---
> cmd/bootefi.c| 42 ++--
> in
From: Keerthy
There is no SPL specific Kconfig symbol defined for DM_REGULATOR_GPIO but
Makefile uses a SPL tag for building gpio-regulator. This makes
gpio-regulator can never be built for SPL. Fix it by dropping the
SPL tag in Makefile. CONFIG_SPL_POWER_SUPPORT is used for including
regulator s
Default setup is 0 which is incorrect place because it points to OCM
which is allocated for SPL only in our case.
Use address in DDR.
Signed-off-by: Michal Simek
---
include/configs/zynq-common.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/configs/zynq-common.h b/include/confi
This adds support for TSE PCS (Triple Speed Ethernet Physical Coding
Sublayer) that uses SGMII adapter when the phy-mode in device tree is
set to sgmii.
Signed-off-by: Ooi, Joyce
---
arch/arm/mach-socfpga/include/mach/misc.h | 1 +
arch/arm/mach-socfpga/misc.c | 5 +
arch/arm/ma
On Wed, Oct 17, 2018 at 8:54 AM Alexander Graf wrote:
>
>
>
> On 16.10.18 21:33, Simon Goldschmidt wrote:
> > Currently, only the kernel can be compressed in a FIT image.
> > By moving the uncompression logic to 'fit_image_load()', all types
> > of images can be compressed.
> >
> > This works perf
LX2160AQDS is a development board that supports LX2160A
family SoCs. This patch add base support for this board.
Signed-off-by: Wasim Khan
Signed-off-by: Sriram Dash
Signed-off-by: Pankaj Bansal
---
Notes:
The checkpatch script reported 28 warnings about line over 80
characters, that i
LX2160AQDS is a development board that supports LX2160A
family SoCs. This patch add base support for this board.
Signed-off-by: Wasim Khan
Signed-off-by: Sriram Dash
Signed-off-by: Pankaj Bansal
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index a76678d5d8..a8e274e88c 100644
--- a/arch/arm
On 17.10.18 09:32, AKASHI Takahiro wrote:
> With this patch applied, we will be able to selectively execute
> an EFI application by specifying a load option, say "-1" for Boot0001,
> "-2" for Boot0002 and so on.
>
> => bootefi bootmgr -1
I don't think -1 is very good user experience :). How
On 17.10.18 09:32, AKASHI Takahiro wrote:
> In this patch, helper functions for an load option variable (Boot)
> are added:
> * efi_parse_load_option(): parse a string into load_option data
> (renamed from parse_load_option and exported)
> * efi_marshel_load_option():
From: Andreas Dannenberg
The earlier commit f4fcba5c5ba ("clk: implement clk_set_defaults()")
which introduced the functionality for setting clock defaults such as
rates and parents will skip the processing when executing in a re-reloc
state. This for example can prevent the assigning of clock pa
On 17.10.18 09:32, AKASHI Takahiro wrote:
> This patch set is a collection of patches to enhance efi user interfaces
> /commands. It will help improve user experience on efi boot and make it
> more usable without edk2's shell utility.
That's amazing, thanks a lot :)
> Patch#1 to #4 are for efis
In this patch, helper functions for an load option variable (Boot)
are added:
* efi_parse_load_option(): parse a string into load_option data
(renamed from parse_load_option and exported)
* efi_marshel_load_option(): convert load_option data into a string
Those funct
With this patch applied, we will be able to selectively execute
an EFI application by specifying a load option, say "-1" for Boot0001,
"-2" for Boot0002 and so on.
=> bootefi bootmgr -1
Please note that Boot need not be included in "BootOrder".
Signed-off-by: AKASHI Takahiro
---
cmd/boo
Factor out efi_set_bootdev() and extract efi_dp_from_name().
This function will be used to set a boot device in efishell command.
Signed-off-by: AKASHI Takahiro
---
cmd/bootefi.c| 42 ++--
include/efi_loader.h | 4 +++
lib/efi_loader/efi_d
The current way how command parameters, particularly "fdt addr," are
handled makes it a bit complicated to add a subcommand-specific parameter.
So just refactor the code and extract efi_handle_fdt().
This commit is a preparatory change for enhancing bootmgr sub-command.
Signed-off-by: AKASHI Taka
Currently, there is no easy way to add or modify UEFI variables.
In particular, bootmgr supports BootOrder/Boot variables, it is
quite hard to define them as u-boot variables because they are represented
in a complicated and encoded format.
The new command, efishell, helps address these issues
As in the case of fs_set_blk_dev(), fs_set_blk_dev_with_part() should
maintain and update fs_dev_part whenever called.
Without this patch, a problem will come up when an efi binary associated
with efi's BOOT variable is invoked via "bootefi bootmgr".
Signed-off-by: AKASHI Takahiro
---
fs/fs
This patch set is a collection of patches to enhance efi user interfaces
/commands. It will help improve user experience on efi boot and make it
more usable without edk2's shell utility.
Patch#1 to #4 are for efishell.
Patch#5 and #6 are for bootmgr.
Let's see how it works:
=> efishell boot add 1
Hi Tom,
This is my current patch queue for efi for inclusion into 2018.11. Please pull.
Alex
The following changes since commit 2364b70c87a8d4ac327a44161df32d2c8e209545:
Merge branch 'master' of git://git.denx.de/u-boot-i2c (2018-10-16 07:25:28
-0400)
are available in the git repository a
On Tue, Oct 16, 2018 at 09:56:33PM -0700, Vasily Khoruzhick wrote:
> Fix off-by-one that prevented PWM driver to use prescaler bypass.
> Without this change prescaler is always enabled.
>
> Signed-off-by: Vasily Khoruzhick
For the whole series,
Acked-by: Maxime Ripard
Thanks!
Maxime
--
Maxim
76 matches
Mail list logo
