All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dorde Stojicevic <dorde.stojicevic@rohde-schwarz.com>
To: Tom Rini <trini@konsulko.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: RE:  Re: Re: [PATCH] arm: Backward compatibility to U-Boot v2020.04
Date: Fri, 6 Feb 2026 06:28:39 +0000	[thread overview]
Message-ID: <989f3c4aa5a04fd3b1c2efda1aedd459@rohde-schwarz.com> (raw)
In-Reply-To: <20260206015447.GP2603314@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 3850 bytes --]

Hi,

yes of course.

Here it is:

$ mkimage -l build/ed7ct-cb.srp
FIT description: LynxSecure 2025.10.0-39844b80e0 SRP (aarch64)
Created:         Thu Feb  5 13:58:31 2026
 Image 0 (kernel-1)
  Description:  LynxSecure 2025.10.0-39844b80e0 SRP (aarch64)
  Created:      Thu Feb  5 13:58:31 2026
  Type:         Kernel Image
  Compression:  uncompressed
  Data Size:    262512264 Bytes = 256359.63 KiB = 250.35 MiB
  Architecture: AArch64
  OS:           Linux
  Load Address: 0x40200000
  Entry Point:  0x40200040
 Image 1 (fdt-1)
  Description:  Flattened Device Tree blob for LynxSecure 2025.10.0-39844b80e0 SRP (aarch64)
  Created:      Thu Feb  5 13:58:31 2026
  Type:         Flat Device Tree
  Compression:  uncompressed
  Data Size:    79519 Bytes = 77.66 KiB = 0.08 MiB
  Architecture: AArch64
 Default Configuration: 'conf-1'
 Configuration 0 (conf-1)
  Description:  LynxSecure 2025.10.0-39844b80e0 SRP (aarch64)
  Kernel:       kernel-1
  FDT:          fdt-1

Pls keep me in to loop, I am quite interested in this

Greetings
Dorde


Dorde Stojicevic

Networks and Cybersecurity

Rohde & Schwarz SIT GmbH
Hemminger Strasse 41 | 70499 Stuttgart-Weilimdorf | Germany
Phone: +4971169945195

Internet: www.rohde-schwarz.com



Geschäftsführer / Managing Director: Ralf Koenzen
Aufsichtsratsvorsitzender / Chair of the Supervisory Board: Mario Paoli
Sitz / Registered Office: Stuttgart
Handelsregister / Commercial Register: AG Stuttgart HRB 759 934
Umsatzsteuer-Identifikationsnummer (USt-IdNr.) / VAT Identification No.: DE 121 963 283
Elektro-Altgeräte Register (EAR) / WEEE Register No.: DE 877 727 67



-----Original Message-----
From: Tom Rini <trini@konsulko.com> 
Sent: Friday, February 6, 2026 2:55 AM
To: Stojicevic Dorde (11SIEPT1) <dorde.stojicevic@rohde-schwarz.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>; u-boot@lists.denx.de
Subject: *EXT* Re: Re: [PATCH] arm: Backward compatibility to U-Boot v2020.04 ***CAUTION_Invalid_Signature***

On Thu, Feb 05, 2026 at 12:20:27PM +0000, Dorde Stojicevic wrote:
> Hi guys,
> 
> and thanks for your fast response.
> 
> Sorry for the formatting issue, I am bound to our company Outlook, which hard-codes our signatures, so this one will not be possible to take out. I am not quite sure git send-email would work, for the same reason + corporate stuff....
> 
> Anyhow, an update/clarification on the things going on here (I could/should have sent initially, sorry for that):
> 
> 1) Lynx Toolchain compiles a FIT Image with the following structure:
> 	{
> 		Images{
> 			Kernel-1 {
> 				Data=Image;
> 			}
> 			Fdt-1 {
> 				Data=system.dtb;
> 			}
> 		}
> 		Configurations {
> 			Here kernel-1 and fdt-1 used as default conf-1
> 		}
> 	}
> 2) Data=Image does not have the Magic Code 0x644d5241
> 3) It is booting with U-Boot SPL 2020.04+g1ccc9d93576+p1 according to Lynx. I haven´t tested myself since we started with 2024.04, and we need it for some other features.
> 4) Then I investigated differences v2020.04 vs v2024.04, and found this part of code came in.
> 5) The finding is consistent with last error reported by U-Boot prior to reset "Bad Linux ARM64 Image magic!"
> 
> 6) I 1st tried patching the Data=Image in Lynx FIT with the magic code, but it didn’t work.
> 7) once I patched bootm in U-Boot to skip this part and behaves as in 
> v2020.04 (excluded all restructuring etc.) it booted the Lynx kernel
> 
> Basically, v2024.04 correctly detects "Bad Linux ARM64 Image magic!", as none is there at the moment, but in order to boot Lynx Hypervisor as-is this backward compatibility to v2020.04 is needed.
> 
> Does this shine more light on it?

This is helpful, yes, thanks. Can you provide an "mkimage -l" of one of these failing to boot FIT images?

--
Tom

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 9150 bytes --]

  reply	other threads:[~2026-02-06 12:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 15:41 [PATCH] arm: Backward compatibility to U-Boot v2020.04 Dorde Stojicevic
2026-02-03 16:42 ` Quentin Schulz
2026-02-03 17:00 ` Tom Rini
2026-02-05 12:20   ` Dorde Stojicevic
2026-02-06  1:54     ` Tom Rini
2026-02-06  6:28       ` Dorde Stojicevic [this message]
2026-02-06 15:03         ` Tom Rini
2026-02-06 15:17           ` Dorde Stojicevic
2026-02-06 15:32             ` Tom Rini
2026-02-24  7:30             ` Dorde Stojicevic
2026-02-25 22:24               ` Tom Rini
2026-02-26  8:15                 ` Dorde Stojicevic
2026-02-26 15:26                   ` Tom Rini
2026-07-31  6:46                     ` Dorde Stojicevic
2026-07-31 10:10                       ` Patrick Deiber
     [not found]     ` <CAFLszTh7F9K+NqyOxSzs7G_+MgNURFrLyGuK3WJhdNndvwQZpA@mail.gmail.com>
2026-08-06 20:58       ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=989f3c4aa5a04fd3b1c2efda1aedd459@rohde-schwarz.com \
    --to=dorde.stojicevic@rohde-schwarz.com \
    --cc=quentin.schulz@cherry.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.