Hi Mark/Tom
On 9/25/2023 9:01 PM, Tom Rini wrote:
On Mon, Sep 25, 2023 at 05:27:26PM +0200, Mark Kettenis wrote:
Date: Mon, 25 Sep 2023 11:21:26 -0400
From: Tom Rini
On Sun, Sep 24, 2023 at 04:48:32PM +0530, Udit Kumar wrote:
In case of new memory range to be added is coalesced
with any alr
Thanks Simon
On 9/25/2023 9:39 PM, Simon Glass wrote:
Hi Udit,
On Sun, 24 Sept 2023 at 22:10, Kumar, Udit wrote:
On 9/24/2023 7:21 PM, Heinrich Schuchardt wrote:
Am 24. September 2023 13:18:32 MESZ schrieb Udit Kumar :
[..]
Assumption
Thanks Heinrich will fix this typo in v2.
Let me wa
On Mon, Sep 25, 2023 at 10:18:55AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 25 Sept 2023 at 09:13, Tom Rini wrote:
> >
> > On Mon, Sep 25, 2023 at 08:35:44AM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 25 Sept 2023 at 08:08, Tom Rini wrote:
> > > >
> > > > On Sun, Sep 24,
On Mon, Sep 25, 2023 at 10:27:43AM +0200, Rasmus Villemoes wrote:
> On 04/05/2023 14.35, Rasmus Villemoes wrote:
> > On 03/05/2023 16.54, Tom Rini wrote:
>
> >> The one last problem now is on stm32mp15_dhcor_basic which is a
> >> defconfig missing one from OF_LIST but including it in the its file,
On Mon, Sep 25, 2023 at 11:25 AM Simon Glass wrote:
>
> Hi Miquel,
>
> On Mon, 25 Sept 2023 at 09:24, Miquel Raynal
> wrote:
> >
> > Hi Simon,
> >
> > > > > > > > > > > I was assuming that I should create a top-level
> > > > > > > > > > > compatible = "binman"
> > > > > > > > > > > node, with s
On 25/09/2023 20.19, Tom Rini wrote:
> On Mon, Sep 25, 2023 at 10:27:43AM +0200, Rasmus Villemoes wrote:
>> On 04/05/2023 14.35, Rasmus Villemoes wrote:
>>> On 03/05/2023 16.54, Tom Rini wrote:
>>
The one last problem now is on stm32mp15_dhcor_basic which is a
defconfig missing one from O
Thanks Stefan!
All the best,
Tony
On Mon, Sep 25, 2023 at 1:14 AM Stefan Roese wrote:
>
> On 9/6/23 07:22, Tony Dinh wrote:
> > Add hook in sata_mv probe to enable bootstd bootdev.
> >
> > Note: bootdev_setup_for_sibling_blk() invocation is a noop if bootsd is
> > not enabled for ahci sata yet.
On Mon, Sep 25, 2023 at 01:32:59PM -0300, Fabio Estevam wrote:
> From: Eduard Strehlau
>
> CONFIG_SYS_BOOT_LOCKED means that a restricted boot environment will
> be used. In this case, hab_auth_img_or_fail should be called to prevent
> U-Boot to continue running when the fitImage authentication
That outputs LLC about a second after the mxsldr terminates (kinda slowly,
the individual characters can be seen being emitted one at a time), and
then about 5 seconds later, "Pref". But nothing after that point.
At least it looks like there is something happening, which is excellent!
Thank you!
On Sun, Sep 24, 2023 at 01:24:53PM -0600, Simon Glass wrote:
> For U-Boot proper we have CONFIG_SYS_MALLOC_F which indicates that a
> malloc() pool is available before relocation.
>
> For SPL we only have CONFIG_SPL_SYS_MALLOC_F_LEN which indicates the
> size of the pool.
>
> In various places w
Hi Simon,
I commented on the v1 thread, but let's continue the discussion here
On Thu, 21 Sept 2023 at 04:58, Simon Glass wrote:
>
> Standard passage provides for a bloblist to be passed from one firmware
> phase to the next. That can be used to pass the devicetree along as well.
> Add an option
On Sun, Sep 24, 2023 at 01:25:01PM -0600, Simon Glass wrote:
> This feature has some helpers in its header file so that its functions
> resolve to nothing when the feature is disabled. Add a few more and use
> these to simplify the code.
>
> With this there are no more #ifdefs in board_init_r()
>
Hi Simon,
Here is an observation during testing the bootflow command.
If there is a SCSI bootflow, scanning for USB bootflow will remove that existing
SCSI bootflow. To bring it back, I scanned for SCSI bootflow again, and it was
back to normal. Perhaps there is some kind of indexing problem?
Pl
On Sun, Sep 24, 2023 at 01:25:23PM -0600, Simon Glass wrote:
> The PCI helpers read only the base address for a PCI region. In some cases
> the size is needed as well, e.g. to pass along to a driver which needs to
> know the size of its register area.
>
> Update the functions to allow the size to
From: Sean Edmond
In our datacenter application, a single DHCP server is servicing 36000+ clients.
Improvements are required to the DHCPv4 retransmission behavior to align with
RFC and ensure less pressure is exerted on the server:
- retransmission backoff interval maximum is configurable
(env
From: Sean Edmond
This patch introduces 3 improvements to align with RFC 951:
- retransmission backoff interval maximum is configurable
- initial retranmission backoff interval is configurable
- transaction ID is kept the same for each BOOTP/DHCPv4 request
In applications where thousands of node
From: Sean Edmond
The new config option BOOTP_RANDOM_XID will randomize the transaction ID
for each new BOOT/DHCPv4 exchange.
Signed-off-by: Sean Edmond
---
cmd/Kconfig | 7 +++
net/bootp.c | 31 +--
2 files changed, 24 insertions(+), 14 deletions(-)
diff --gi
From: Sean Edmond
Allow dhcp server pass pxe config file full path by using option 209
Signed-off-by: Sean Edmond
---
cmd/Kconfig | 4
cmd/pxe.c | 10 ++
net/bootp.c | 21 +
3 files changed, 35 insertions(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 43ca
On Sun, Sep 24, 2023 at 01:24:45PM -0600, Simon Glass wrote:
> This series tidies up SPL a little and adds some core ofnode functions
> needed to support Universal Payload. It also includes a few minor fix-ups
> for sandbox.
>
> For SPL the changes include CONFIG naming, removing various #ifdefs
Hi Kever,
It would be nice to get some feedback and plans for this and the
following series :-)
rockchip: rk3568: Fix use of PCIe bifurcation (this series)
https://patchwork.ozlabs.org/cover/1816140/
rockchip: rk3568-nanopi-r5: Add missing PCIe options
https://patchwork.ozlabs.org/cover/1816147/
With MMC_PWRSEQ enabled the following link issue may happen when
building SPL and SPL_PWRSEQ is not enabled.
aarch64-linux-gnu-ld.bfd: drivers/mmc/meson_gx_mmc.o: in function
`meson_mmc_probe':
drivers/mmc/meson_gx_mmc.c:295: undefined reference to `pwrseq_set_power'
Fix this by adding a SPL
Hi Rob,
On Mon, 25 Sept 2023 at 12:49, Rob Herring wrote:
>
> On Mon, Sep 25, 2023 at 11:25 AM Simon Glass wrote:
> >
> > Hi Miquel,
> >
> > On Mon, 25 Sept 2023 at 09:24, Miquel Raynal
> > wrote:
> > >
> > > Hi Simon,
> > >
> > > > > > > > > > > > I was assuming that I should create a top-lev
Hi Rogan,
On Mon, Sep 25, 2023 at 4:27 PM Rogan Dawes wrote:
>
> That outputs LLC about a second after the mxsldr terminates (kinda slowly,
> the individual characters can be seen being emitted one at a time), and then
> about 5 seconds later, "Pref". But nothing after that point.
>
> At least
Hi Ilias,
On Mon, 25 Sept 2023 at 21:37, Ilias Apalodimas
wrote:
>
> On Fri, Sep 22, 2023 at 04:11:15PM +0900, Masahisa Kojima wrote:
> > This supports to boot from the URI device path.
> > When user selects the URI device path, bootmgr downloads
> > the file using wget into the address specified
On Mon, 25 Sept 2023 at 21:12, Ilias Apalodimas
wrote:
>
> On Fri, Sep 22, 2023 at 04:11:18PM +0900, Masahisa Kojima wrote:
> > This adds the description about HTTP Boot.
> >
> > Signed-off-by: Masahisa Kojima
> > ---
> > doc/develop/uefi/uefi.rst | 30 ++
> > 1 file
Hi Ilias,
On Mon, 25 Sept 2023 at 21:46, Ilias Apalodimas
wrote:
>
> Kojima-san,
>
> [...]
> > /* Carve out DT reserved memory ranges */
> > void efi_carve_out_dt_rsv(void *fdt);
> > /* Purge unused kaslr-seed */
> > diff --git a/lib/efi_loader/efi_bootmgr.c b/lib/efi_loader/efi_bootmgr.c
> >
Hi Fabio,
That prints "LLC", but does not print "Pref".
Rogan
On Tue, 26 Sept 2023 at 02:15, Fabio Estevam wrote:
> Hi Rogan,
>
> On Mon, Sep 25, 2023 at 4:27 PM Rogan Dawes wrote:
> >
> > That outputs LLC about a second after the mxsldr terminates (kinda
> slowly, the individual characters
On Thu, Sep 14, 2023 at 12:49 PM Heinrich Schuchardt wrote:
>
> On 9/14/23 08:48, Wu, Fei wrote:
> > On 9/14/2023 2:05 PM, Heinrich Schuchardt wrote:
> >>
> >>
> >> Am 14. September 2023 07:30:55 MESZ schrieb Fei Wu :
> >>> In order to enable PCIe passthrough on qemu riscv, the physical memory
> >
Hi Tom,
The following changes since commit 15155ab0a3d1f839509bcac620bfb38f950bead6:
Merge tag 'u-boot-imx-20230923' of
https://source.denx.de/u-boot/custodians/u-boot-imx (2023-09-24 17:15:31 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-ri
Hi Keerthy
On 9/25/2023 7:12 PM, Nishanth Menon wrote:
On 18:56-20230925, Keerthy wrote:
Hi Tom,
https://lore.kernel.org/linux-arm-kernel/5187c590-ee9a-4c46-b326-655f4c371...@linaro.org/T/#me178708007a6b3b9695ae0ff84475fa4f49f283c
I have posted the ESM patches to the linux kernel device tree
On 22/09/23 12:30, Alexander Dahl wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hello Durai,
>
> Am Thu, Sep 21, 2023 at 10:36:27PM +0530 schrieb Durai Manickam KR:
>> This patch series adds boot from NAND support, configs update and
>>
On 25/09/2023 17.14, Jonas Karlman wrote:
>> fit,align
>> -Indicates what alignment to use for the FIT and its external data,
>> -and provides the alignment to use. This is passed to mkimage via
>> -the -B flag.
>> +Indicates what alignment to use for the FIT a
Le 24/09/2023 à 21:24, Simon Glass a écrit :
> It doesn't make sense to have some boards do this differently. Drop the
> condition in the hope that the maintainers can figure out any run-time
> problems.
This was added by commit ea8256f072 ("SPL: Port SPL framework to
powerpc"), and the commit
This patch series allows users to access SCMI base protocol provided by
SCMI server (platform). It will also be utilized in separate patches
in the future to add sanity/validity checks for other protocols.
See SCMI specification document v3.2 beta[1] for more details about SCMI
base protocol.
What
The commit 85dc58289238 ("firmware: scmi: prepare uclass to pass channel
reference") added an explicit parameter, channel, but it seems to make
the code complex.
Hiding this parameter will allow for adding a generic (protocol-agnostic)
helper function, i.e. for PROTOCOL_VERSION, in a later patch.
SCMI specification allows any protocol to have its own channel for
the transport. While the current SCMI driver may assign its channel
from a device tree, the core function, devm_scmi_process_msg(), doesn't
use a protocol's channel, but always use an agent's channel.
With this commit, devm_scmi_pr
In sandbox scmi agent, channels are not used at all. But in this patch,
dummy channels are supported in order to test protocol-specific channels.
Signed-off-by: AKASHI Takahiro
---
v5
* new commit
---
arch/sandbox/include/asm/scmi_test.h | 13
drivers/firmware/scmi/sandbox-scmi_agent.
Any SCMI protocol may have its own channel.
Test this feature on sandbox as the necessary framework was added
in a prior commit.
Signed-off-by: AKASHI Takahiro
---
v5
* new commit
---
arch/sandbox/dts/test.dts | 1 +
test/dm/scmi.c| 20 ++--
2 files changed, 19 inser
SCMI base protocol is mandatory according to the SCMI specification.
With this patch, SCMI base protocol can be accessed via SCMI transport
layers. All the commands, except SCMI_BASE_NOTIFY_ERRORS, are supported.
This is because U-Boot doesn't support interrupts and the current transport
layers ar
Move the location of scmi_bind_protocols() backward for changes
in later patches.
There is no change in functionality.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* remove scmi_bind_protocols() from the original place. See patch#1
* s/depeding/de
This framework allows SCMI protocols to be installed and bound to the agent
so that the agent can manage and utilize them later.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
V4
* remove 'agent' variable as it should be added in the following commit
v
This is a simple implementation of SCMI base protocol for sandbox.
The main use is in SCMI unit test.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Reviewed-by: Etienne Carriere
---
v4
* move this patch forward in this series before installing base
protocol to avoid collapsing exist
Adding SCMI base protocol makes it inconvenient to hold the agent instance
(udevice) locally since the agent device will be re-created per each test.
Just remove it and simplify the test flows.
The test scenario is not changed at all.
Signed-off-by: AKASHI Takahiro
Reviewed-by: Simon Glass
Revie
101 - 143 of 143 matches
Mail list logo
