On 21.07.20 04:51, Heinrich Schuchardt wrote:
dev_read_size_cells() and dev_read_addr_cells() do not walk up the device
tree to find the number of cells. On error they return 1 and 2
respectively. On qemu_arm64_defconfig this leads to the incorrect detection
of address of the second flash bank as
The test can run on sandbox build and it attempts to execute a firmware
update via a capsule-on-disk, using a raw image capsule,
CONFIG_EFI_CAPSULE_RAW.
To run this test successfully, you need configure U-Boot specifically;
See test_capsule_firmware.py for requirements, and hence it won't run
on T
In this commit, a very simple firmware management protocol driver
is implemented. It will take a binary image in a capsule file and
apply the data using dfu backend storage drivers via dfu_write_by_alt()
interface.
So "dfu_alt_info" variable should be properly set to specify a device
and location
"efidebug capsule" is more or less a debugging utility.
efidebug capsule update: invoke UpdateCapsule against data on memory
efidebug capsule show: show a capsule header
efidebug capsule result: dump a capsule result variable
Signed-off-by: AKASHI Takahiro
---
cmd/efidebug.c | 235
The test can run on sandbox build and it attempts to execute a firmware
update via a capsule-on-disk, using a FIT image capsule,
CONFIG_EFI_CAPSULE_FIT.
To run this test successfully, you need configure U-Boot specifically;
See test_capsule_firmware.py for requirements, and hence it won't run
on T
This is a utility mainly for test purpose.
mkeficapsule -f: create a test capsule file for FIT image firmware
Having said that, you will be able to customize the code to fit
your specific requirements for your platform.
Signed-off-by: AKASHI Takahiro
---
tools/Makefile | 3 +
tools/mk
In this commit, a very simple firmware management protocol driver
is implemented. It will take a common FIT image firmware in a capsule
file and apply the data using dfu backend storage drivers via
update_fit() interface.
So "dfu_alt_info" variable should be properly set to specify a device
and lo
This function is a variant of dfu_write_by_name() and takes a DFU alt
setting number for dfu configuration.
It will be utilised to implement UEFI capsule management protocol for
raw image in a later commit.
Signed-off-by: AKASHI Takahiro
---
drivers/dfu/dfu_alt.c | 47 ++
A capsule tagged with the guid, EFI_FIRMWARE_MANAGEMENT_CAPSULE_ID_GUID,
is handled as a firmware update object.
What efi_update_capsule() basically does is to load any firmware management
protocol (or fmp) drivers contained in a capsule, find out an appropriate
fmp driver and then invoke its set_i
Capsule data can be loaded into the system either via UpdateCapsule
runtime service or files on a file system (of boot device).
The latter case is called "capsules on disk", and actual updates will
take place at the next boot time.
In this commit, we will support capsule on disk mechanism.
Please
In this commit, skeleton functions for capsule-related API's are
added under CONFIG_EFI_UPDATE_CAPSULE configuration.
Detailed implementation for a specific capsule type will be added
in the succeeding patches.
Signed-off-by: AKASHI Takahiro
---
include/efi_api.h| 12 +++
include/ef
If this option, CONFIG_EFI_SETUP_EARLY, is enabled, the initialisation
of UEFI subsystem will be done as part of U-Boot initialisation.
Please note that this option won't be enabled explicitly by users,
instead, should be enabled implicitly by other configuration options.
Specifically, this featu
Memory range capsule gives us a way to notify that some memory regions
should be left untouched across the next reset.
See UEFI specification, section 8.5.3.
Since how we should handle this kind of capsule is totally up to
the system, no implementation will be added in this commit.
Signed-off-by:
Summary
===
'UpdateCapsule' is one of runtime services defined in UEFI specification
and its aim is to allow a caller (OS) to pass information to the firmware,
i.e. U-Boot. This is mostly used to update firmware binary on devices by
instructions from OS.
While 'UpdateCapsule' is a runtime serv
The main purpose of this patch is to separate a generic interface for
updating firmware using DFU drivers from "auto-update" via tftp.
This function will also be used in implementing UEFI capsule update
in a later commit.
Signed-off-by: AKASHI Takahiro
---
common/Kconfig | 14 +
co
The range of an addressable pointer can go beyond 'integer'.
So change the argument type to a void pointer.
Signed-off-by: AKASHI Takahiro
---
common/update.c | 3 ++-
drivers/dfu/dfu_alt.c | 4 ++--
include/dfu.h | 4 ++--
3 files changed, 6 insertions(+), 5 deletions(-)
diff --g
This function is essentially independent from tffp, and will also be
utilised in implementing UEFI capsule update in a later commit.
So just give it a more generic name.
In addition, a new configuration option, CONFIG_DFU_ALT, was introduced
so that the file will be compiled with different options,
This variable will be utilized to enumerate all dfu entities
for UEFI capsule firmware update in a later commit.
Signed-off-by: AKASHI Takahiro
---
drivers/dfu/dfu.c | 2 +-
include/dfu.h | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/dfu/dfu.c b/drivers/dfu/d
Signed-off-by: AKASHI Takahiro
---
v1:
* execute 'make install' with sudo
---
.travis.yml | 16
1 file changed, 16 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 1ff140855ea3..c99c37947c7f 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -52,6 +52,14 @@ addons:
-
Hello Michal,
Am 21.07.2020 um 15:14 schrieb Michal Simek:
The commit 2bd261dd1712 ("gpio: search for gpio label if gpio is not found
through bank name") introduced the option to search gpio via labels (gpio
hog). This patch is just follow up on this and fills pin name based on
gpio-line-names D
On Tue, Jul 21, 2020 at 10:21:52AM -0600, Simon Glass wrote:
> Hi Marty,
>
> Did you check spl_boot_device()?
>
After sending the initial email I noticed your binman work, which does
some of the stuff I think I need. My current setup is as follows:
diff --git a/arch/arm/dts/Makefile b/arch/arm/d
On Tue, Jul 21, 2020 at 06:45:58PM +0900, AKASHI Takahiro wrote:
> This version of sbsigntools is a prerequisite in testing "intermediate
> certificates" support as part of UEFI secure boot as I added '--addcert'
> option to 'sbsign' command:
>
> ===
> commit 7d6210e4b1fd
> Author: AKASHI T
On Mon, Jul 20, 2020 at 10:44:49PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> PR for spinand changes.
>
> Summary:
> - add new series Micron SPI NAND devices (Shivamurthy)
>
> The following changes since commit 7303ba10a4a39852b9ba356fae5656b43122eec6:
>
> Merge https://gitlab.denx.de/u-boot/cus
Hi David,
Does this board dts available in kernel mainline?
Thanks,
- Kever
On 2020/7/21 下午3:13, David Bauer wrote:
This adds support for the NanoPi R2S from FriendlyArm.
Rockchip RK3328 SoC
1GB DDR4 RAM
Gigabit Ethernet (WAN)
Gigabit Ethernet (USB3) (LAN)
USB 2.0 Host Port
MicroSD slot
Hi Jagan
> From: Jagan Teki [mailto:ja...@amarulasolutions.com]
> Sent: Tuesday, July 21, 2020 2:26 PM
> To: Rick Jian-Zhi Chen(陳建志); Atish Patra; Palmer Dabbelt; Bin Meng; Paul
> Walmsley; Anup Patel; Sagar Kadam
> Cc: U-Boot-Denx; linux-amarula
> Subject: Re: [PATCH v5 0/6] riscv: sifive/fu540:
On 2020-07-21, Tom Rini wrote:
> On Sun, Jul 19, 2020 at 11:23:05AM -0700, Vagrant Cascadian wrote:
>
>> The mx6cuboxi target no longer builds reproducibility on Debian. I've
>> bisected it down to:
>>
>> eb9124f5748c96ffd548e50fd6989c3b5395b353 mx6cuboxi: enable OF_CONTROL with
>> DM_MMC and D
The current code does not trim the output buffer correctly.
In fact it doesn't trim the buffer at all, since it calculates a wrong
value for it, which isn't even applied.
So let's remove the unused temporary size variable and trim the buffer
correctly.
Since we are editing efi_get_next_variable_nam
On Sun, Jul 19, 2020 at 11:23:05AM -0700, Vagrant Cascadian wrote:
> The mx6cuboxi target no longer builds reproducibility on Debian. I've
> bisected it down to:
>
> eb9124f5748c96ffd548e50fd6989c3b5395b353 mx6cuboxi: enable OF_CONTROL with
> DM_MMC and DM_USB
Are you tracking any other platf
Hi Walter,
On Tue, Jul 21, 2020 at 2:24 PM Walter Lozano
wrote:
>
> As both MMC and GPIO driver now supports OF_PLATDATA, enable it in
> defconfig in order to reduce the SPL footprint.
Could you add in the commit log how many kB of SPL size reduction this gives?
Thanks
From: Stephen Warren
Remove a double space introduced by my previous fixdep fix.
Fixes: 76ae74d348a0 ("fixdep: fix CONFIG_IS_ENABLED etc. handling")
Signed-off-by: Stephen Warren
---
scripts/basic/fixdep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/basic/fixdep
For testing automated updates via dfu and mtd we need the dfu and mtd
commands as well as preboot support.
Signed-off-by: Heinrich Schuchardt
---
configs/qemu_arm64_defconfig | 9 +
configs/qemu_arm_defconfig | 9 +
2 files changed, 18 insertions(+)
diff --git a/configs/qemu_a
Function mtdparts_init() is needed for the DFU MTD driver.
Signed-off-by: Heinrich Schuchardt
---
drivers/dfu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dfu/Kconfig b/drivers/dfu/Kconfig
index 46c915f9e5..106f38817a 100644
--- a/drivers/dfu/Kconfig
+++ b/drivers/dfu/Kcon
DFU_OVER_TFTP has been defined as a synonym for DFU_TFTP. Remove the
superfluous symbol.
Move build dependencies expressed in common/update.c as an error message to
Kconfig.
Signed-off-by: Heinrich Schuchardt
---
cmd/dfu.c | 10 +-
common/update.c | 4
drivers/dfu/Kc
Using UPDATE_TFTP the firmware can be updated from TFTP by writing to NOR
flash. The same is possible by defining a dfu command in CONFIG_PREBOOT.
The dfu command cannot only write to NOR but also to other devices. In
README.dfutfp UPDATE_TFTP has been marked as deprecated. It is not used
by any b
Continuing with the approach in commit rename
additional drivers to allow the OF_PLATDATA support.
Signed-off-by: Walter Lozano
---
drivers/pinctrl/nxp/pinctrl-imx6.c | 6 --
drivers/video/imx/mxc_ipuv3_fb.c | 4 ++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers
As both MMC and GPIO driver now supports OF_PLATDATA, enable it in
defconfig in order to reduce the SPL footprint.
Signed-off-by: Walter Lozano
---
configs/mx6cuboxi_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/mx6cuboxi_defconfig b/configs/mx6cuboxi_defconfig
index cd4
After enabling OF_PLATDATA support to both MMC and GPIO drivers add the
support for card detection.
Signed-off-by: Walter Lozano
---
drivers/mmc/fsl_esdhc_imx.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/fsl_esdhc_imx.c b/drivers/
Continuing with the OF_PLATADATA support for iMX6 to reduce SPL
footprint, add it to mxc_gpio. Thanks to this, it will be possible to
enable card detection on MMC driver.
Signed-off-by: Walter Lozano
---
drivers/gpio/mxc_gpio.c | 18 +-
1 file changed, 17 insertions(+), 1 deleti
On 21.07.20 19:03, Faiz Abbas wrote:
> Jan,
>
> On 21/07/20 12:06 pm, Jan Kiszka wrote:
>> On 21.07.20 01:23, Jaehoon Chung wrote:
>>> On 7/20/20 10:21 AM, Peng Fan wrote:
Hi Jan,
> Subject: am654_sdhci: mmc fail to send stop cmd
>
> Hi all,
>
> on one device with one
As discussed in commit rename fsl_esdhc_imx
driver to allow the OF_PLATDATA support.
Signed-off-by: Walter Lozano
---
drivers/mmc/fsl_esdhc_imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/fsl_esdhc_imx.c b/drivers/mmc/fsl_esdhc_imx.c
index 5b61eeb214..7d76
In order to reduce the footprint of SPL by removing dtb and library
overhead add OF_PLATDATA support to fsl_esdhc_imx. This initial
approach does not support card detection, which will be enabled after
adding OF_PLATDATA support to GPIO.
Signed-off-by: Walter Lozano
---
drivers/mmc/fsl_esdhc_im
The SPL in iMX6 boards is restricted to 68 KB as this is the free available
space in OCRAM for most revisions. In this context, adding OF_CONTROL and DM
increases the SPL size which could make it difficult to add specific features
required for custom scenarios.
These patches aim to take advantage
Jan,
On 21/07/20 12:06 pm, Jan Kiszka wrote:
> On 21.07.20 01:23, Jaehoon Chung wrote:
>> On 7/20/20 10:21 AM, Peng Fan wrote:
>>> Hi Jan,
>>>
Subject: am654_sdhci: mmc fail to send stop cmd
Hi all,
on one device with one specific SD-card (possibly an aging one), I'm seein
Hi Simon,
On 21.07.2020 17:17, Simon Glass wrote:
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
Factor out ppc-specific bdinfo setup from generic init sequence to
arch_setup_bdinfo in arch/powerpc/lib/bdinfo.c.
Signed-off-by: Ovidiu Panait
---
arch/powerpc/lib/bdinfo.c | 25 +
Hi Marty,
On Sun, 19 Jul 2020 at 21:33, Marty E. Plummer wrote:
>
> Greetings.
>
> I've been working on u-boot for rk3399-gru-kevin, Samsung Chromebook
> Plus. In theory it should be fairly similar to the Bob chromebook, and
> as such my work is largely based on it. Aside from some trivial change
On 21.07.20 16:02, Stefan Sørensen wrote:
> When reading a directory, EFI_BUFFER_TOO_SMALL should be returned when
> the supplied buffer is too small, so a use-case is to call
> efi_file_read with *buffer_size=0 and buffer=NULL to obtain the needed
> size before doing the actual read.
>
> So drop t
Disable ram rockchip debug driver for ROCKPi N8/N10 boards
since we have verified ram in many instances with respective
U-Boot versions.
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
configs/rock-pi-n10-rk3399pro_defconfig | 1 +
configs/rock-pi-n8-rk3288_defconfig | 1 +
2 files cha
Enable PCI/NVME for M.2 Slot on RockPI-4 boards.
=> nvme info
Device 0: Vendor: 0x144d Rev: 4L1QCXB7 Prod: S35FNX0J623292
Type: Hard Disk
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
configs/rock-pi-n10-rk3399pr
Add u-boot,spl-boot-order for ROCKPi N10, so-that it can able
to boot from eMMC and SDMMC in order.
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
arch/arm/dts/rk3399pro-rock-pi-n10-u-boot.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/dts/rk3399pro-rock-pi-n10-u-
From: Suniel Mahesh
Enable common on board devices for ROCKPi N8.
- USB 2.0 Host
- USB 2.0 OTG/Gadget
- HDMI Out
Signed-off-by: Suniel Mahesh
Signed-off-by: Jagan Teki
---
Changes for v2:
- squash common device enablement
configs/rock-pi-n8-rk3288_defconfig | 16
1 file cha
Radxa dalang carrier board has 2x USB 2.0 and 1x USB 3.0
ports.
This patch adds support to enable all these USB ports for
N10 and N8 combinations SBCs.
Note that the USB 3.0 port on RockPI N8 combination works
as USB 2.0 OTG since it is driven from RK3288.
Signed-off-by: Jagan Teki
---
Changes
This patch adds support to enable PCIe for RockPI N10.
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
arch/arm/dts/rk3399pro-vmarc-som.dtsi | 40 +--
1 file changed, 38 insertions(+), 2 deletions(-)
diff --git a/arch/arm/dts/rk3399pro-vmarc-som.dtsi
b/arch/arm/dt
This patch adds support to enable HDMI out for
N10 and N8 combinations SBCs.
Signed-off-by: Jagan Teki
---
Changes for v2:
- none
arch/arm/dts/rk3288-vmarc-som.dtsi| 10 ++
arch/arm/dts/rk3399pro-vmarc-som.dtsi | 12 +++
.../dts/rockchip-radxa-dalang-carrier.
From: Suniel Mahesh
Add console settings like stdin, stdout and stderr as
usbkbd and vidconsole respectively for evb-rk3288 targets.
This would certainly help to detect the attached video
devices (like HDMI) and print the console messages on display.
Signed-off-by: Suniel Mahesh
Signed-off-by:
From: Suniel Mahesh
Enable common on board devices for ROCKPi N10.
- USB 2.0 Host
- USB 3.0 Host
- USB 3.0 Gadget
- HDMI Out
Signed-off-by: Suniel Mahesh
Signed-off-by: Jagan Teki
---
Changes for v2:
- squash common device enablement
configs/rock-pi-n10-rk3399pro_defconfig | 21
rk3288 and rk3288w have a usb host0 ohci controller.
Although rk3288 ohci doesn't actually work on hardware, but
rk3288w ohci can work well.
So add usb host0 ohci node in rk3288 dtsi and the quirk in
ohci platform driver will disable ohci on rk3288.
Signed-off-by: Jagan Teki
---
Changes for v2:
From: Suniel Mahesh
This sync has changes required to use HDMI CEC pin in U-Boot.
Sync dts from linux v5.8-rc5 commit:
"ARM: dts: rockchip: define the two possible rk3288 CEC pins"
(sha1: 838980dd04e994bf81cf104fa01ae60802146b39)
Signed-off-by: Suniel Mahesh
Signed-off-by: Jaga
Series enable hardware enablement on ROCKPi N8/N10
boards.
- USB 3.0 Host
- USB 2.0 Host
- USB 3.0 Gadget
- USB 2.0 Gadget
- HDMI Out
- PCIe
Note: dts patches are Synced from linux-next and few from mailing list.
Jagan Teki (8):
ARM: dts: rockchip: Sync ROCKPi N8/N10 dts(i) from Linux
ARM: d
Sync ROCKPi N8/N10 dts(i) changes from Linux.
commit ("ARM: dts: rockchip: Add Radxa Rock Pi N8 initial
support")
Signed-off-by: Suniel Mahesh
Signed-off-by: Jagan Teki
Reviewed-by: Kever Yang
---
Changes for v2:
- collect kerver r-b
arch/arm/dts/rk3288-rock-pi-n8.dts| 2 +-
arc
From: Yan Liu
Current pytest only support upto 2 stage boot;
Some boards like TI K3 am6/J7 boards use 3 stage
boot. This patch adds u_boot_spl2 to be able to
handle the 3-stage boot case. User needs to set
"env__spl2_skipped" in u_boot_boardenv config
file to use this support. By default it is se
When reading a directory, EFI_BUFFER_TOO_SMALL should be returned when
the supplied buffer is too small, so a use-case is to call
efi_file_read with *buffer_size=0 and buffer=NULL to obtain the needed
size before doing the actual read.
So drop the buffer!=NULL requirement when doing directory read
ROC-RK3399-PC has specific set of configurations for
on-board led setup.
Due to easiness for user to know the state of the board
roc-rk339-pc board code will setup the low power led
on/off, and waiting for user to press power key and then
glow full power led.
All this needs to happen only during
reset cause is a generic functionality based on the soc
cru registers in rockchip. This can be used for printing
the cause of reset in cpuinfo or some other place where
reset cause is needed.
Other than cpuinfo, reset cause can also be using during
bootcount for checking the specific reset cause
roc-rk3399-pc has some specific requirements to support LEDS,
environment. board detection and etc prior to U-Boot proper.
So as of now SPL would be a better stage for these custom board
requirements to support unlike TPL. Adding few of these custom
requirements like LEDS in TPL would require extr
reset reason can be used several stages of U-Boot bootloader
like SPL, U-Boot proper based on the requirements.
Clearing the status register end of get_reset_cause will end
up showing the wrong reset cause when it read the second time.
For example, if board resets, SPL reads the reset status as
RS
This series supports custom initialization code required for
roc-rk3399-pc board on SPL stage.
Now this series is well mature code handling to add custom
spl_board_init code parts.
roc-rk3399-pc would require custom leds initialization based
on user intervention of the power key. This code han
Add weak led_setup() so that board which has an uncommon
led setup code that can make use of custom implementation.
Signed-off-by: Jagan Teki
---
Changes for v6:
- new patch
arch/arm/mach-rockchip/rk3399/rk3399.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-rockchip/r
> Hi Daniel,
>
> On 18.07.20 15:25, Daniel Schwierzeck wrote:
> > > From: Suneel Garapati
...
> > found another issue:
> >
> > drivers/gpio/octeon_gpio.c: In function 'octeon_gpio_probe':
> > drivers/gpio/octeon_gpio.c:189:16: warning: implicit declaration of
> > function 'dm_pci_map_bar'; did
On 17/07/2020 14:22, Philippe Reynes wrote:
> Add a simple driver which allows use of buttons attached to GPIOs.
>
> Reviewed-by: Simon Glass
> Signed-off-by: Philippe Reynes
> ---
> Changelog:
> v2:
> - remove useless default in Kconfig
> - re-order include
> - fix condition in button_gpio_remo
scan_dev_for_efi is supposed to be called from scan_dev_for_boot.
However this call is missing for ls1028ardb and ls1028aqds boards. As
a result EFI boot doesn’t work. Fix this issue by adding
scan_dev_for_efi call.
Signed-off-by: Mian Yousaf Kaukab
---
include/configs/ls1028aqds.h | 1 +
includ
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
>
> Move sram related bdinfo from arch-specific setup_board_part1 to generic
> code in setup_bdinfo. Also use "if (IS_ENABLED(CONFIG_SYS_HAS_SRAM))"
> instead of "#ifdef CONFIG_SYS_SRAM_BASE".
>
> Signed-off-by: Ovidiu Panait
> ---
>
> common/bo
On Mon, 20 Jul 2020 at 08:18, Ovidiu Panait wrote:
>
> Introduce setup_bdinfo initcall as a generic routine to populate bdinfo
> fields.
>
> Signed-off-by: Ovidiu Panait
> ---
>
> common/board_f.c | 6 ++
> include/init.h | 10 ++
> 2 files changed, 16 insertions(+)
Reviewed-by:
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
>
> Factor out m68k-specific bdinfo setup to arch_setup_bdinfo in
> arch/m68k/lib/bdinfo.c. Also, use if(IS_ENABLED()) instead of #ifdef where
> possible.
>
> Signed-off-by: Ovidiu Panait
> ---
>
> arch/m68k/lib/bdinfo.c | 21 +++
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
>
> Factor out ppc-specific bdinfo setup from generic init sequence to
> arch_setup_bdinfo in arch/powerpc/lib/bdinfo.c.
>
> Signed-off-by: Ovidiu Panait
> ---
>
> arch/powerpc/lib/bdinfo.c | 25 +
> common/board_f.c
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
>
> Now that all arch specific code was converted to setup_bdinfo, we can
> remove setup_board_part1.
>
> Signed-off-by: Ovidiu Panait
> ---
>
> common/board_f.c | 12 +---
> 1 file changed, 1 insertion(+), 11 deletions(-)
Reviewed-by:
On Mon, 20 Jul 2020 at 08:18, Ovidiu Panait wrote:
>
> bi_sramstart and bi_sramsize are generic members of the bd_info structure,
> so move the m68k/powerpc-specific prints to generic code. Also, print them
> only if SRAM support is enabled via CONFIG_SYS_HAS_SRAM.
>
> Signed-off-by: Ovidiu Panait
Hi Philippe,
On Mon, 20 Jul 2020 at 08:30, Philippe REYNES
wrote:
>
> Hi Simon,
>
> > Hi Philippe,
> >
> > On Fri, 17 Jul 2020 at 06:22, Philippe Reynes
> > wrote:
> >>
> >> Add a test to confirm that we can read button state
> >> using the button-gpio driver.
> >>
> >> Signed-off-by: Philippe R
On 7/10/20 6:41 AM, Michal Simek wrote:
> The commit 4cc24aeaf420 ("serial: Add missing Kconfig dependencies for
> debug consoles") has added incorrect dependency for SIFIVE debug uart which
> should depend on SIFIVE driver instead of PL01x.
>
> Fixes: 4cc24aeaf420 ("serial: Add missing Kconfig de
Hi Ovidiu,
On Mon, 20 Jul 2020 at 08:20, Ovidiu Panait wrote:
>
> In most cases (arc, ppc, mips, sh, m68k) gd->bd->bi_memsize and
> gd->bd->bi_memstart are populated in a similar fashion:
>
> bd->bi_memstart = CONFIG_SYS_SDRAM_BASE;
> bd->bi_memsize = gd->ram_size;
>
> However, there is a
On 7/21/20 10:00 AM, Michal Simek wrote:
> Hi Sean,
>
> On 21. 07. 20 15:58, Sean Anderson wrote:
>> The debug sifive serial driver depends on the wrong serial driver, making
>> it unselectable.
>>
>> Fixes: 4cc24aeaf42 ("serial: Add missing Kconfig dependencies for debug
>> consoles")
>>
>> Sig
Hi Sean,
On 21. 07. 20 15:58, Sean Anderson wrote:
> The debug sifive serial driver depends on the wrong serial driver, making
> it unselectable.
>
> Fixes: 4cc24aeaf42 ("serial: Add missing Kconfig dependencies for debug
> consoles")
>
> Signed-off-by: Sean Anderson
> CC: Michal Simek
> ---
>
The debug sifive serial driver depends on the wrong serial driver, making
it unselectable.
Fixes: 4cc24aeaf42 ("serial: Add missing Kconfig dependencies for debug
consoles")
Signed-off-by: Sean Anderson
CC: Michal Simek
---
drivers/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 dele
Hi kever,
On Tue, Jul 21, 2020 at 8:43 AM Kever Yang
wrote:
>
> On 2020/7/20 下午6:53, Jagan Teki wrote:
> > Hi Kever,
> >
> > On Sat, Jul 18, 2020 at 5:41 PM Kever Yang
> wrote:
> >> Hi Jagan,
> >>
> >> On 2020/7/10 下午11:50, Jagan Teki wrote:
> >>> From: Suniel Mahesh
> >>>
> >>> Rockchip RK808
On 21. 07. 20 8:40, Heiko Schocher wrote:
> Hi Michal,
>
> Am 20.07.2020 um 10:30 schrieb Michal Simek:
>> Hi Heiko,
>>
>> pá 22. 5. 2020 v 11:10 odesílatel Heiko Schocher napsal:
>>>
>>> dm_gpio_lookup_name() searches for a gpio through
>>> the bank name. But we have also gpio labels, and it
Enable this feature especially when gpio-line-names are supported which is
used by number of Xilinx boards.
Signed-off-by: Michal Simek
---
configs/xilinx_versal_virt_defconfig | 1 +
configs/xilinx_zynq_virt_defconfig | 1 +
configs/xilinx_zynqmp_virt_defconfig | 1 +
3 files changed, 3 inse
With OF_CONTROL disabled the build fails for
include/dm/read.h:932:10: error: ‘ENOTSUPP’ undeclared (first use in this
function)
Fixes: 134f3c366d78 ("dm: core: gracefully handle alias seq without of")
Signed-off-by: Dan Murphy
---
include/dm/read.h | 2 ++
1 file changed, 2 insertions(+)
diff
The commit 2bd261dd1712 ("gpio: search for gpio label if gpio is not found
through bank name") introduced the option to search gpio via labels (gpio
hog). This patch is just follow up on this and fills pin name based on
gpio-line-names DT property.
Signed-off-by: Michal Simek
---
arch/sandbox/d
On Tue, Jul 21, 2020 at 06:56:39PM +0900, AKASHI Takahiro wrote:
> Hi Tom,
>
> I'd like to modify travis.yml as follows below,
> but the script failed at 'make install':
>
> ===8<===
> /bin/mkdir -p '/usr/local/bin'
> /usr/bin/install -c sbsign sbverify sbattach sbvarsign sbsiglist sbkeysync
>
On Tue, Jul 21, 2020 at 7:01 PM Wolfgang Wallner
wrote:
>
> Fix some typos in arch/x86/include/asm/irq.h.
>
> Signed-off-by: Wolfgang Wallner
>
> ---
>
> arch/x86/include/asm/irq.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Reviewed-by: Bin Meng
Hi Neil,
On 7/21/20 1:41 PM, Neil Armstrong wrote:
> This checks and handles RX errors on the Amlogic UART controller
> after experiencing errors on the Khadas VIM3 & VIM3L when UART AO A
> lines are not connected.
>
> When the RX line is not connected, the first byte is erroneous and breaks
> th
On Thu, Jul 16, 2020 at 06:44:43AM +0200, Heinrich Schuchardt wrote:
> On 7/16/20 3:52 AM, AKASHI Takahiro wrote:
> > On Wed, Jul 15, 2020 at 04:42:20PM +0200, Heinrich Schuchardt wrote:
> > On 15.07.20 16:06, Michal Simek wrote:
>
>
> On 15. 07. 20 15:23, Lukasz Majewski wrote:
> >>
This checks and handles RX errors on the Amlogic UART controller
after experiencing errors on the Khadas VIM3 & VIM3L when UART AO A
lines are not connected.
When the RX line is not connected, the first byte is erroneous and breaks
the U-Boot autoboot, breaking automatic boot.
This checks and dro
Hi Daniel,
On 18.07.20 15:25, Daniel Schwierzeck wrote:
From: Suneel Garapati
Add support for GPIO controllers found on Octeon II/III and Octeon TX
TX2 SoC platforms.
Signed-off-by: Aaron Williams
Signed-off-by: Suneel Garapati
Signed-off-by: Stefan Roese
Cc: Simon Glass
Cc: Daniel Schw
Fix some typos in arch/x86/include/asm/irq.h.
Signed-off-by: Wolfgang Wallner
---
arch/x86/include/asm/irq.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/irq.h b/arch/x86/include/asm/irq.h
index e5c916070c..bee0760c2d 100644
--- a/arch/x86/incl
This adds support for the NanoPi R2S from FriendlyArm.
Rockchip RK3328 SoC
1GB DDR4 RAM
Gigabit Ethernet (WAN)
Gigabit Ethernet (USB3) (LAN)
USB 2.0 Host Port
MicroSD slot
Reset button
WAN - LAN - SYS LED
Signed-off-by: David Bauer
---
arch/arm/dts/Makefile | 1 +
arch/ar
Dear Jagan sir:
Many thanks for your response. Sorry that it is my first time to apply
the patch, if there is any problem, your comment would be appreciated.
Follow my understanding, I rebase the master and the branch
"UpdateWinbondID" is up to date. I use patman to check my wor
In this test case, an image may have a signature with additional
intermediate certificates. A chain of trust will be followed and all
the certificates in the middle of chain must be verified before loading.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/conftest.py| 116 ++
The function, pkcs7_verify_one(), will be utilized to rework signature
verification logic aiming to support intermediate certificates in
"chain of trust."
To do that, its function interface is expanded, adding an extra argument
which is expected to return the last certificate in trusted chain.
The
In this commit, efi_signature_verify(with_sigdb) will be re-implemented
using pcks7_verify_one() in order to support certificates chain, where
the signer's certificate will be signed by an intermediate CA (certificate
authority) and the latter's certificate will also be signed by another CA
and so
It won't be very useful to customize HELLO_PATH and EFI_SECBOOT_IMAGE_NAME
under the current code base. So just remove them.
Signed-off-by: AKASHI Takahiro
---
test/py/tests/test_efi_secboot/conftest.py | 10 +++---
test/py/tests/test_efi_secboot/defs.py | 6 --
2 files changed, 3 i
1 - 100 of 128 matches
Mail list logo