All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Dorde Stojicevic <dorde.stojicevic@rohde-schwarz.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: Re: Re: Re: [PATCH] arm: Backward compatibility to U-Boot v2020.04
Date: Wed, 25 Feb 2026 16:24:17 -0600	[thread overview]
Message-ID: <20260225222417.GY1593142@bill-the-cat> (raw)
In-Reply-To: <f991777100194a22b350660b5977cf27@rohde-schwarz.com>

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

On Tue, Feb 24, 2026 at 07:30:13AM +0000, Dorde Stojicevic wrote:

> Hi all,
> 
> sorry that it took a while to get the response from Lynx but it couldn´t be helped unfortunately.
> 
> I got the response from Lynx:
> 
> " Hello Dorde.
> 
> I’ve got a replay from our engineering team. We do not support u-boot, so we don’t have any plans to make SRP “ARM64 kernel“ compatible.
> 
> We work with board with default u-boot (for now it is U-Boot SPL 2020.04).
> 
> So, you are free to make any changes in u-boot to make SRP run in newest version of u-boot.
> "
> 
> I am a bit surprised by the response that they don´t seem really interested in it, but it is how it is. So we are free to apply the patch to our liking.
> 
> Let me know how we proceed from here

Well, if they aren't going to do the work, someone needs to do the work
to support the OS. What's happened since 2020.04 is that we now
correctly detect and fail something that claims to be a Linux ARM64
Image, but is not. We aren't going to go back and re-allow that, it was
a bug.

The proposal I outlined for how I think it should look, for proper
support, is something that I hope someone interested / motivated can
look in to doing.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-02-25 22:24 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
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 [this message]
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=20260225222417.GY1593142@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=dorde.stojicevic@rohde-schwarz.com \
    --cc=quentin.schulz@cherry.de \
    --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.