This patch removes the AT91_LOAD_BAREBOX_SRAM option.
The option was introduced over 12 years ago and is now misleading.
The functionality of loading a stage into SRAM can now be implemented
via PBL in a low-level board-specific call.
For boot sources (other than MMC), BOOTRom expects the size of t
Hi Stefano,
I merged both patches into one to avoid intermediate breakage.
On Fri, Feb 21, 2025 at 07:01:08PM +0100, Stefano Manni wrote:
> @@ -1599,7 +1607,8 @@ static int imx7_fcb_write(struct mtd_info *mtd, int
> block, struct fcb_block *fcb
> return mxs_nand_write_fcb_bch62(block, fcb,
Hi Jonas,
On 3/4/25 5:24 PM, Jonas Rebmann wrote:
This patch adds support for the phyBOARD-Segin i.MX 93 and the phyCORE
i.MX 93 SoM it is based upon.
Note that support is only provided for the standard configuration
featuring 1GB RAM as testing was only possible on that variant and only
the si
Hi David,
On 05.03.25 12:30, David Jander wrote:
> On Tue, 4 Mar 2025 22:50:00 +0100
> Martin Wege wrote:
>> So yes, you would have customers for NFSv4.1 support in barebox.
>
> Just wanted to chime in to amplify this a bit, since we are also using NFSv4.2
> netboot (though only TFTP in barebox
dd26bc1d5a0 ("ARM: i.MX93: add destination argument to
imx93_romapi_load_image()") added the imx93_romapi_load_image call to
imx93_load_and_start_image_via_tfa and removed the call from
board-specific lowlevel code. So drop the corresponding include as well.
Signed-off-by: Bastian Krause
---
arc
Hi Ahmad,
On Wed, 5 Mar 2025 13:51:51 +0100
Ahmad Fatoum wrote:
> Hi David,
>
> On 05.03.25 12:30, David Jander wrote:
> > On Tue, 4 Mar 2025 22:50:00 +0100
> > Martin Wege wrote:
> >> So yes, you would have customers for NFSv4.1 support in barebox.
> >
> > Just wanted to chime in to am
There's already precedence in global.tftp.windowsize, so global.nfs.port
is probably a better name than squeezing it into global.net.
This parameter is not yet in any release, so the fallout is fairly
limited.
While at it, mention it in the documentation.
Signed-off-by: Ahmad Fatoum
---
Docume
s/varariables/variables/
Signed-off-by: Ahmad Fatoum
---
Documentation/user/networking.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/user/networking.rst
b/Documentation/user/networking.rst
index 0adcff6954dc..1be2a15ac5f4 100644
--- a/Documentation/user/n
Dear Martin,
On Tue, 4 Mar 2025 22:50:00 +0100
Martin Wege wrote:
> On Mon, Mar 3, 2025 at 9:40 AM Ahmad Fatoum wrote:
> >
> > Hi,
> >
> > On 28.02.25 11:57, Sascha Hauer wrote:
> > > On Fri, Feb 21, 2025 at 12:54:00PM +0100, Martin Wege wrote:
> > >> On Wed, Feb 12, 2025 at 3:33 PM Sasch
Hello Martin,
On 04.03.25 22:50, Martin Wege wrote:
> On Mon, Mar 3, 2025 at 9:40 AM Ahmad Fatoum wrote:
>> We had a discussion about this last year, but it didn't result in any
>> upstream code yet:
>> https://lore.barebox.org/barebox/caavcncczhs8mkvdgcj2l-eiur+oxgwexrlnado_hfyhfsi7...@mail.gmai
On Mon, 03 Mar 2025 09:59:16 +0100, Steffen Trumtrar wrote:
> When the L4WD0 is left enabled on startup, depending on handoff files
> and its PLL settings, the DDR code might hang while waiting for the
> calibration to be successful. Rework this code and cleanup the rest of
> the driver a little
On Fri, 21 Feb 2025 19:01:08 +0100, Stefano Manni wrote:
> Device file was hardcoded to "nand0.barebox".
> This patch harmonize the signature of
>
> imx6_bbu_nand_register_handler()
> imx7_bbu_nand_register_handler()
> imx28_bbu_nand_register_handler()
>
> [...]
Applied, thanks!
[1/2] imx-bbu
Trivial code cleanup, which includes:
- Adding/removing blank lines for better code readability.
- Wrapping the of_compatible driver property in DRV_OF_COMPAT().
Signed-off-by: Alexander Shiyan
---
arch/arm/mach-at91/ddramc.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --g
13 matches
Mail list logo
