"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
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
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 +++
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
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.
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
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.
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 +
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
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
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
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
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 | 16 +++
Hi Pratyush,
On Mon, 8 Jun 2020 at 12:05, Pratyush Yadav wrote:
>
> Hi Simon,
>
> On 01/06/20 08:45AM, Simon Glass wrote:
> > Hi Pratyush,
> >
> > On Mon, 1 Jun 2020 at 05:22, Pratyush Yadav wrote:
> > >
> > > On 31/05/20 08:08AM, Simon Glass wrote:
> > > > Hi Pratyush,
> > > >
> > > > On Fri,
On Sun, 7 Jun 2020 at 10:47, Heinrich Schuchardt wrote:
>
> Up to now the RAM size of the sandbox is hard coded as 128 MiB. This does
> not allow testing the correct handling of addresses outside the 32bit
> range. 128 MiB is also rather small when tracing functions where the trace
> is written
Hi Sean,
On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>
> The pinmux property allows for smaller and more compact device trees,
> especially when there are many pins which need to be assigned individually.
> Instead of specifying an array of strings to be parsed as pins and a
> function
Hi Sean,
On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>
> This extends the pinctrl-sandbox driver to support pin muxing, and adds a
> test for that behaviour. The test is done in C and not python (like the
> existing tests for the pinctrl uclass) because it needs to call
>
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
Hi Michal,
On Tue, 16 Jun 2020 at 07:53, Michal Simek wrote:
>
>
>
> On 16. 06. 20 15:43, Simon Glass wrote:
> > On Mon, 15 Jun 2020 at 07:41, Michal Simek wrote:
> >>
> >> Remove adhoc dt binding for fixed-partition definition for i2c eeprom.
> >> fixed-partition are using reg property instead
Hi Pratyush,
On Thu, 11 Jun 2020 at 13:45, Pratyush Yadav wrote:
>
> initr_dm_devices() is called somewhere after board_init(). It can be
> used by drivers to initialize devices to some default bootup state.
> Those devices might use mmio read/write operations to perform the
> initialization.
>
On Thu, 11 Jun 2020 at 13:45, Pratyush Yadav wrote:
>
> This command lets the user list, select, and deselect mux controllers
> introduced with the mux framework on the fly. It has 3 subcommands:
> list, select, and deselect.
>
> List: Lists all the mux present on the system. The muxes are listed
Hi Stephen,
On Mon, 8 Jun 2020 at 11:25, Stephen Warren wrote:
>
> On 6/8/20 11:12 AM, Simon Glass wrote:
> > Hi Stephen,
> >
> > On Mon, 8 Jun 2020 at 10:43, Stephen Warren wrote:
> >>
> >> On 6/7/20 7:45 AM, Simon Glass wrote:
> >>> On Thu, 4 Jun 2020 at 09:24, Heiko Schocher wrote:
>
>
On Tue, 9 Jun 2020 at 23:36, Bin Meng wrote:
>
> From: Bin Meng
>
> It should be "writable".
>
> Signed-off-by: Bin Meng
> ---
>
> (no changes since v1)
>
> test/dm/fdtdec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Simon Glass
Hi Rasmus,
On Fri, 12 Jun 2020 at 05:02, Rasmus Villemoes
wrote:
>
> When building host tools, the CONFIG_GZIP etc. symbols are not defined
> anyway, so this does not (should not) change anything [1]. However,
> since the host tools also don't include linux/kconfig.h, one cannot
> use the
Hi Duncan,
On Mon, 15 Jun 2020 at 11:31, Duncan Hare wrote:
>
> Is there U-Boot with Ethernet available in U-Boot for the Raspberry PI 4?
>
> If not is u-boot without Ethernet available for the Raspberry Pi 4, and and
> interface spec available for the and Pi 4 Ethernet driver?
>
> I have read
On Tue, 16 Jun 2020 at 01:41, Patrick Delaunay wrote:
>
> Add test for the erase command tested on ENV in EXT4.
>
> Signed-off-by: Patrick Delaunay
> ---
>
> (no changes since v1)
>
> configs/sandbox64_defconfig| 1 +
> configs/sandbox_defconfig | 1 +
>
On Tue, 16 Jun 2020 at 01:40, Patrick Delaunay wrote:
>
> Add support of environment location with a new sandbox command
> 'env_loc'.
>
> When the user change the environment location with the command
> 'env_loc ' the env is reinitialized and saved;
> the GD_FLG_ENV_DEFAULT flag is also updated.
On Wed, 10 Jun 2020 at 04:41, Rayagonda Kokatanur
wrote:
>
> Enable clock subsystem for ns3.
>
> Signed-off-by: Rayagonda Kokatanur
> ---
> configs/bcm_ns3_defconfig | 2 ++
> 1 file changed, 2 insertions(+)
It feels like I have already reviewed some of these patches. Can you
check if you
On Tue, 9 Jun 2020 at 23:36, Bin Meng wrote:
>
> From: Bin Meng
>
> Add DECLARE_GLOBAL_DATA_PTR since it is referenced in the test codes.
>
> Signed-off-by: Bin Meng
> ---
>
> (no changes since v1)
>
> test/dm/fdtdec.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Simon Glass
You
Hi Michal,
On Wed, 10 Jun 2020 at 07:18, Michal Simek wrote:
>
> Remove adhoc dt binding for fixed-partition definition for i2c eeprom.
> fixed-partition are using reg property instead of offset/size pair.
>
> Signed-off-by: Michal Simek
> ---
>
> Just build tested - ge_bx50v3_defconfig
>
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
Logically, the current update_tftp() should and does compile and work
correctly even without satisfying the following condition:
> #if defined(CONFIG_UPDATE_TFTP) && !defined(CONFIG_MTD_NOR_FLASH)
> #error "CONFIG_UPDATE_TFTP and !CONFIG_MTD_NOR_FLASH needed for
> legacy behaviour"
> #endif
It
DFU_OVER_TFTP support on "dfu" command relies on update_tftp()
being available. Just explicitly add this dependency.
Signed-off-by: AKASHI Takahiro
---
drivers/dfu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dfu/Kconfig b/drivers/dfu/Kconfig
index
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
On Thu, 11 Jun 2020 at 13:45, Pratyush Yadav wrote:
>
> From: Jean-Jacques Hiblot
>
> Add a new subsystem that handles multiplexer controllers. The API is the
> same as in Linux.
>
> Signed-off-by: Jean-Jacques Hiblot
> Signed-off-by: Pratyush Yadav
> ---
> drivers/Kconfig | 2
On 6/16/20 11:11 PM, Simon Glass wrote:
> Hi Sean,
>
> On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>>
>> This extends the pinctrl-sandbox driver to support pin muxing, and adds a
>> test for that behaviour. The test is done in C and not python (like the
>> existing tests for the pinctrl
On Fri, 29 May 2020 at 15:38, Pratyush Yadav wrote:
>
> From: Jean-Jacques Hiblot
>
> Add a test to verify that GPIOs can be acquired/released using the managed
> API. Also check that the GPIOs are released when the consumer device is
> removed.
>
> Signed-off-by: Jean-Jacques Hiblot
> ---
>
On 6/16/20 11:11 PM, Simon Glass wrote:
> On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>>
>> This more closely mirrors Linux's behaviour, and will make it easier to
>> transition to using function+color in the future.
>>
>> Signed-off-by: Sean Anderson
>> ---
>> This patch was previously
On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>
> Change the type of gpio_dwabp_platdata.base from fdt_addr_t to a void
> pointer, since we pass it to readl.
>
> Signed-off-by: Sean Anderson
> Reviewed-by: Bin Meng
> ---
> This patch was previously submitted as part of
>
Hi Pratyush,
On Mon, 8 Jun 2020 at 06:37, Pratyush Yadav wrote:
>
> On 01/06/20 11:08AM, Simon Glass wrote:
> > Hi Pratyush,
> >
> > On Fri, 29 May 2020 at 16:04, Pratyush Yadav wrote:
> > >
> > > Prepare the way for a managed GPIO API by handling NULL pointers without
> > > crashing or
On Sun, 7 Jun 2020 at 19:27, Sean Anderson wrote:
>
> This more closely mirrors Linux's behaviour, and will make it easier to
> transition to using function+color in the future.
>
> Signed-off-by: Sean Anderson
> ---
> This patch was previously submitted as part of
>
On Thu, 11 Jun 2020 at 13:45, Pratyush Yadav wrote:
>
> From: Jean-Jacques Hiblot
>
> This will probe the multiplexer devices that have a "u-boot,mux-autoprobe"
> property. As a consequence they will be put in their idle state.
>
> Signed-off-by: Jean-Jacques Hiblot
> Signed-off-by: Pratyush
On Sat, 13 Jun 2020 at 04:59, Heinrich Schuchardt wrote:
>
> Add random number generation APIs to the HTML documentation.
> Fix style issues.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> MAINTAINERS | 1 +
> doc/api/index.rst | 1 +
> doc/api/rng.rst | 17 +
>
Hi Pratyush,
On Thu, 11 Jun 2020 at 13:45, Pratyush Yadav wrote:
>
> From: Jean-Jacques Hiblot
>
> This adds a driver for mmio-based syscon multiplexers controlled by
> bitfields in a syscon register range.
> This is heavily based on the linux mmio-mux driver.
>
> Signed-off-by: Jean-Jacques
On Fri, 12 Jun 2020 at 06:08, Pratyush Yadav wrote:
>
> From: Jean-Jacques Hiblot
>
> The tests are basically the same as for the regular API. Except that
> the reset are initialized using the managed API, and no freed manually.
>
> Signed-off-by: Jean-Jacques Hiblot
> Signed-off-by: Pratyush
On Wed, 10 Jun 2020 at 04:41, Rayagonda Kokatanur
wrote:
>
> Add L3 memory flush support for NS3.
>
> Signed-off-by: Rayagonda Kokatanur
> ---
> arch/arm/cpu/armv8/Makefile | 1 +
> arch/arm/cpu/armv8/bcmns3/Makefile | 5 ++
> arch/arm/cpu/armv8/bcmns3/lowlevel.S | 90
On Tue, 9 Jun 2020 at 23:36, Bin Meng wrote:
>
> From: Bin Meng
>
> This adds a test case to test the functionality of the fdtdec API
> fdtdec_add_reserved_memory().
>
> Signed-off-by: Bin Meng
> ---
>
> Changes in v3:
> - correct typo in the comments, and some minor rewording
>
>
On Wed, 10 Jun 2020 at 04:41, Rayagonda Kokatanur
wrote:
>
> Add support for Broadcom Northstar 3 SoC.
> NS3 is a octo-core 64-bit ARMv8 Cortex-A72 processors
> targeting a broad range of networking applications.
>
> Signed-off-by: Rayagonda Kokatanur
> ---
> arch/arm/Kconfig | 10
Hi
On 6/5/20 9:24 AM, Patrick Delaunay wrote:
> From: Etienne Carriere
>
> Add OP-TEE firmware node in stm32mp15 U-Boot DTSI. This node is
> needed since commit [1] that changed U-Boot/stm32mp15 to detect
> OP-TEE availability by probing the resource instead of relying on
> U-Boot configuration.
Hi
On 6/5/20 9:24 AM, Patrick Delaunay wrote:
> From: Etienne Carriere
>
> Fix the sequence in stm32mp1 fdt.c that disables OP-TEE resources
> defined in FDT when U-boot detects OP-TEE firmware is not present.
>
> Before this change, helper function stm32_fdt_disable_optee()
> set property
Hi Stephen,
> From: Stephen Warren
> Sent: mardi 16 juin 2020 00:09
>
> On 6/15/20 8:01 AM, Patrick Delaunay wrote:
> > Add a pytest for testing the env info sub-command:
> >
> > test_env_info: test command with several option
> >
> > test_env_info_quiet: test the result of the sub-command with
Hi,
This is a combined series of both omap4/omap5 DM conversion in one.
The main change across all the boards in this version is to drop SPI
support completely. SPI is only available on expansion headers on the
omap4 panda / omap5 uevm boards, and it is impossible for the authors of
the patches
Hi Jassi,
> ... a polite ping, Lukasz.
The only excuse for so long lack of my response are my personal issues
caused by the covid-19.
Sorry for that..
>
> On Sun, Jun 7, 2020 at 3:59 PM wrote:
> >
> > From: Jassi Brar
> >
> > MAX3420 implements FullSpeed USB Device over SPI.
> > Another
Don't return error with ret=-ENOENT when the optional ops drv->init
is absent but only if env_driver_lookup doesn't found driver.
This patch correct an issue for the code
if (!env_init())
env_load()
When only ext4 is supported (CONFIG_ENV_IS_IN_EXT4),
as the backend env/ext4.c doesn't
Hi,
V2 is only a rebase and adaptation of the serie [1].
In this serie, I add sandbox test with CONFIG_ENV_IS_NOWHERE
activated with other location: at least one CONFIG_ENV_IS_IN_...
is defined and ENV_IS_IN_DEVICE is automatically defined.
To test this feature, I activate and test
Add support of opts erase for env in ext4,
this opts is used by command 'env erase'.
This command only fill the env file (CONFIG_ENV_EXT4_FILE)
with 0, the CRC and the saved environment becomes invalid.
Signed-off-by: Patrick Delaunay
---
Changes in v2:
- use CONFIG_IS_ENABLED to set .erase
The default environment is still used with "ENVL_NOWHERE"
indicated by the weak function env_get_location() and
activated by CONFIG_ENV_IS_NOWHERE.
Signed-off-by: Patrick Delaunay
Reviewed-by: Simon Glass
---
(no changes since v1)
board/sandbox/sandbox.c| 12
Add support of environment location with a new sandbox command
'env_loc'.
When the user change the environment location with the command
'env_loc ' the env is reinitialized and saved;
the GD_FLG_ENV_DEFAULT flag is also updated.
When the user set the same env location, the environment is
Add basic test to persistent environment in ext4:
save and load in host ext4 file 'uboot.env'.
On first execution an empty EXT4 file system is created in
persistent data dir: env.ext4.img.
Signed-off-by: Patrick Delaunay
---
(no changes since v1)
test/py/tests/test_env.py | 87
Add the absolute path to the default value of
CONFIG_ENV_EXT4_FILE = "/uboot.env".
This patch avoid the error :
Saving Environment to EXT4... File System is consistent
Please supply Absolute path
Signed-off-by: Patrick Delaunay
---
For information, it is the value used today by all the
Add a missing initialization of gd->env_valid in env_ext4_load
as it is already done in some other env device.
Set gd->env_valid = ENV_VALID in env_ext4_save() and env_ext4_load().
This patch allows to have a correct information in 'env info' command.
Signed-off-by: Patrick Delaunay
---
(no
Split the function env_ext4_save to prepare the erase support.
Signed-off-by: Patrick Delaunay
---
(no changes since v1)
env/ext4.c | 28
1 file changed, 20 insertions(+), 8 deletions(-)
diff --git a/env/ext4.c b/env/ext4.c
index ac9f126bec..027a721b69 100644
---
Add test for the erase command tested on ENV in EXT4.
Signed-off-by: Patrick Delaunay
---
(no changes since v1)
configs/sandbox64_defconfig| 1 +
configs/sandbox_defconfig | 1 +
configs/sandbox_flattree_defconfig | 1 +
configs/sandbox_spl_defconfig | 1 +
Convert omap5 uevm board to device model.
Signed-off-by: Tero Kristo
---
v3:
* dropped SPI support
arch/arm/dts/omap5-u-boot.dtsi | 42 ++
board/ti/omap5_uevm/evm.c | 78 +-
configs/omap5_uevm_defconfig | 13 --
3 files changed, 62
From: Peter Ujfalusi
Copy all device tree files required for omap4 sdp4430 support from
mainline Linux.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Tero Kristo
---
arch/arm/dts/omap4-sdp-es23plus.dts | 14 +
arch/arm/dts/omap4-sdp.dts | 713
2 files
From: Peter Ujfalusi
Convert omap4 sdp to device model.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Tero Kristo
---
v3:
* dropped SPI support
arch/arm/dts/Makefile | 4
board/ti/sdp4430/sdp.c | 12
configs/omap4_sdp4430_defconfig | 12 +---
3
Convert omap4 panda to device model.
Signed-off-by: Tero Kristo
---
v3:
* dropped SPI support
v2:
* dropped some apparently dead USB EHCI init code, this was just
causing a compile time warning.
arch/arm/dts/Makefile | 4 +++
arch/arm/dts/omap4-u-boot.dtsi | 39
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 20/35] acpi: Support writing a GPIO
>
> Allowing writing out a reference to a GPIO within the ACPI output. This
> can be used by ACPI code to access a GPIO at runtime.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3:
> -
Hi,
> From: Patrick DELAUNAY
> Sent: vendredi 5 juin 2020 09:24
>
> From: Etienne Carriere
>
> Fix the sequence in stm32mp1 fdt.c that disables OP-TEE resources defined in
> FDT when U-boot detects OP-TEE firmware is not present.
>
> Before this change, helper function
Hi,
> From: Patrick DELAUNAY
> Sent: vendredi 5 juin 2020 09:25
>
> From: Etienne Carriere
>
> Add OP-TEE firmware node in stm32mp15 U-Boot DTSI. This node is needed
> since commit [1] that changed U-Boot/stm32mp15 to detect OP-TEE availability
> by probing the resource instead of relying on
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 05/35] acpi: Support generation of ACPI code
>
> Add a new file to handle generating ACPI code programatically. This is
> used when information must be dynamically added to the tables, e.g. the
> SSDT.
>
> Initial support is just
Hi Simon,
> -"Simon Glass" schrieb: -
> Betreff: [PATCH v2 04/25] x86: mp_init: Switch parameter names in start_aps()
>
> These parameters are named differently from elsewhere in this file. Switch
> them to avoid confusion.
>
> Also add comments to this function.
>
> Signed-off-by:
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v2 10/25] x86: mp: Support APs waiting for instructions
>
> At present the APs (non-boot CPUs) are inited once and then parked ready
> for the OS to use them. However in some cases we want to send new requests
> through, such as to
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v2 13/25] x86: mp: Allow running functions on multiple CPUs
>
> Add a way to run a function on a selection of CPUs. This supports either
> a single CPU, all CPUs, just the main CPU or just the 'APs', in Intel
> terminology.
>
> It
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 21/35] acpi: Support copying properties from device tree
> to ACPI
>
> Some drivers in Linux support both device tree and ACPI. U-Boot itself
> uses Linux device-tree bindings for its own configuration but does not use
> ACPI.
>
v2:
For patch #1, replace u32 with u8 for rtl_reset_bmu().
For patch #3, use USB_BP(n) to replace USB_BP_0 ~ USB_BP_7.
Write the registers in bulk for rtl_clear_bp().
For patch #4, add a macro for the magic value. Remove type casts.
Write the register in bulk, if it is possible. Reduce indent.
Some settings of PHY have to work after resetting PHY.
Signed-off-by: Hayes Wang
---
drivers/usb/eth/r8152.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/eth/r8152.c b/drivers/usb/eth/r8152.c
index 041cb22dd3..7f988543a1 100644
--- a/drivers/usb/eth/r8152.c
The original rtl_clear_bp() is used to clear the firmware of both
PLA and USB MCU. The new one could clear the firmware of PLA or
USB independently. It is unnecessary to clear firmware, if there
is no one to be updated.
Besides, clear the firmware by writing the relative registers in
bulk.
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v2 20/25] x86: mtrr: Add support for writing to MTRRs on any
> CPU
>
> To enable support for the 'mtrr' command, add a way to perform MTRR
> operations on selected CPUs.
>
> This works by setting up a little 'operation' structure
Hi Simon,
> -"Simon Glass" schrieb: -
> Betreff: [PATCH v2 24/25] x86: mp: Add more comments to the module
>
> Add a description of how this module works and also some missing function
> comments.
Great to see more documenation :)
>
> Drop struct cpu_map since it is not used.
>
>
287be3294af6179782f8a561afca427620504581:
Merge branch '2020-06-15-misc-bugfixes' (2020-06-15 11:24:42 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git
tags/u-boot-stm32-20200616
for you to fetch changes up
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v2 17/25] x86: Don't enable SMP in SPL
>
> SMP should be set up in U-Boot where possible, not SPL. Disable it in SPL.
> For 64-bit U-Boot we should find a way to allow SMP operations in U-Boot,
> but this is somewhat more
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v2 18/25] x86: coral: Update the memory map
>
> This currently excludes the temporary memory used to start up the APs.
> Add it.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v2:
> - Add new patch to add AP_DEFAULT_BASE to
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 29/35] acpi: Support ordering SSDT data by device
>
> Add a /chosen property to control the order in which the data appears
> in the SSDT. This allows matching up U-Boot's output from a dump of the
> known-good data obtained from
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 32/35] x86: Allow devices to write to DSDT
>
> Call the new core function to inject ASL programmatically into the DSDT.
> This is made up of fragments generated by devices that have the
> inject_dsdt() method. The normal, compiled
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 30/35] x86: Allow devices to write an SSDT
>
> Call the new core function to write the SSDT. This is made up of fragments
> generated by devices that have the fill_ssdt() method.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes
From: Thomas Schaefer
- Despite other ext4 filesystem functions, ext4fs_mount returns
0 in case of error.
- This leads to u-boot crash in case that an SD card
with valid partition table but without ext4 filesystem created
in a partition is found on SD card.
- Fix this by returning a proper
From: Thomas Schaefer
- Despite other ext4 filesystem functions, ext4fs_mount returns
0 in case of error.
- This leads to u-boot crash in case that an SD card
with valid partition table but without ext4 filesystem created
in a partition is found on SD card.
- Fix this by returning a proper
Changes for v3:
- Resend via git send-email
Changes for v2:
- Coding Style cleanup
Signed-off-by: Nico Becker
---
arch/arm/dts/Makefile | 3 +-
...ocfpga_cyclone5_ica_moritz_iii-u-boot.dtsi | 45 ++
.../dts/socfpga_cyclone5_ica_moritz_iii.dts | 123
Hi,
On 16/06/2020 06:35, Anand Moon wrote:
> Hi Neil,
>
> On Thu, 11 Jun 2020 at 19:20, Neil Armstrong wrote:
>>
>> Move the natural text Amlogic board README files to doc/board/amlogic
>> into reStructuredText and :
>> - add reStructuredText markup for bash code
>> - fix secondary titles
Reset bmu after disabling Tx/Rx. This is used to clear the FIFO of
Tx/Rx. The remained data may be transferred after Tx/Rx is re-enabled.
And it results in garbage data.
Signed-off-by: Hayes Wang
---
drivers/usb/eth/r8152.c | 14 ++
drivers/usb/eth/r8152.h | 7 ++-
2 files
This is used to support RTL8153B and RTL8154B.
Signed-off-by: Hayes Wang
---
drivers/usb/eth/r8152.c| 207 -
drivers/usb/eth/r8152.h| 41 +++-
drivers/usb/eth/r8152_fw.c | 170 ++
3 files changed, 414 insertions(+), 4
Hi Simon,
-"Simon Glass" schrieb: -
> Betreff: [PATCH v3 12/35] acpi: Support generation of SPI descriptor
>
> Add a function to write a SPI descriptor to the generated ACPI code.
>
> Signed-off-by: Simon Glass
> ---
>
> Changes in v3:
> - Make acpi_device_write_spi() static
> - Add
On Tue, 2020-06-16 at 07:43 -0600, Simon Glass wrote:
> Hi Nicolas,
>
> On Fri, 12 Jun 2020 at 10:47, Nicolas Saenz Julienne
> wrote:
> > There is no distinction in DT between the PCI controller device and the
> > root bridge, whereas such distinction exists from dm's perspective. Make
> > sure
On Tue, Jun 16, 2020 at 01:59:03PM +0200, Heiko Thiery wrote:
> From: Thomas Schaefer
>
> - Despite other ext4 filesystem functions, ext4fs_mount returns
> 0 in case of error.
> - This leads to u-boot crash in case that an SD card
> with valid partition table but without ext4 filesystem
On Tue, Jun 16, 2020 at 04:27:22PM +0200, Oliver Graute wrote:
> As proposed here:
>
> https://lists.denx.de/pipermail/u-boot/2020-January/396749.html
>
> Both of my imx8qm boards (Advantech and Congatec) aren't booting
> 2020.01 without this change. Whats the proper way to fix this on my side?
On 23:45-20200613, Jagan Teki wrote:
> On Wed, May 27, 2020 at 6:27 PM Jagan Teki wrote:
> >
> > OF_CONTROL, DM_SPI and other driver model migration deadlines
> > are expired for this board.
> >
> > Drop it.
> >
> > Cc: Nishanth Menon
>
> Any comments?
I think this should be fine. OMAP3 ES1.0
On Tue, Jun 16, 2020 at 02:43:07PM +0900, AKASHI Takahiro wrote:
> UEFI subsystem uses utf-16 string, but checkpatch.pl complains
> about any occurrences of L"xxx" which is definitely legal.
> So just suppress this kind of warning.
> Precautiously, we will check u"xxx" as well.
>
>
While commit 048a648298b1 ("checkpatch.pl: Update to v5.7") largely
re-syncs us with checkpatch.pl from v5.7 there are a number of things
missing still. Re-copy the script and again take care to keep our
allowed debug prints and now localized checks intact.
Fixes: 048a648298b1 ("checkpatch.pl:
Hi Walter,
On Fri, 12 Jun 2020 at 11:38, Walter Lozano wrote:
>
>
> On 11/6/20 23:22, Simon Glass wrote:
> > Hi Walter,
> >
> > On Thu, 11 Jun 2020 at 13:07, Walter Lozano
> > wrote:
> >> Hi Simon,
> >>
> >> On 11/6/20 14:22, Simon Glass wrote:
> >>> Hi Walter,
> >>>
> >>> On Thu, 11 Jun 2020
1 - 100 of 204 matches
Mail list logo
