From: Tom Rini <trini@konsulko.com>
To: "Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: Karel Balej <balejk@matfyz.cz>,
~postmarketos/upstreaming@lists.sr.ht, u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] Initial support for PXA1908 and samsung-coreprimevelte
Date: Mon, 30 Dec 2024 09:25:33 -0600 [thread overview]
Message-ID: <20241230152533.GC3476@bill-the-cat> (raw)
In-Reply-To: <4950238.GXAFRqVoOG@radijator>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On Sat, Dec 28, 2024 at 12:10:49PM +0100, Duje Mihanović wrote:
> On Friday 27 December 2024 22:53:27 Central European Standard Time Tom Rini
> wrote:
> > On Fri, Dec 27, 2024 at 10:22:14PM +0100, Duje Mihanović wrote:
> > > Hello,
> > >
> > > This series adds initial support for Marvell's PXA1908 ARM64 SoC and
> > > Samsung's Galaxy Core Prime VE LTE, a smartphone based on said SoC.
> > >
> > > On this board, U-Boot is used as a secondary bootloader to work around
> > > certain quirks of the factory S-Boot.
> > >
> > > Signed-off-by: Duje Mihanović <duje.mihanovic@skole.hr>
> >
> > What is the status of getting these dtsi files upstream? Thanks.
>
> They are the last component of PXA1908 support waiting to be merged, see
> https://lore.kernel.org/all/20241104-pxa1908-lkml-v13-0-e050609b8d6c@skole.hr/
> .
>
> In case you're asking this to see whether the board could use OF_UPSTREAM, I
> should note that the dtsi files in this set differ from the ones waiting to be
> merged into Linux differ by being slimmed down, having different compatibles
> in a few places (CPU and serial ports specifically) and the coreprimevelte dts
> also has an extra property `pxa,rev-id` which the stock bootloader requires
> for booting. Could all this be handled in a `pxa1908-samsung-coreprimevelte-u-
> boot.dtsi` and `pxa1908-u-boot.dtsi` once they are upstreamed?
Yes, this is about moving to OF_UPSTREAM. Strictly and only with respect
to things that we have to deal with due to other bootloaders can we deal
with problems like that in the -u-boot.dtsi file. Otherwise we need to
match compatibles, etc, with upstream. Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-12-30 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 21:22 [PATCH 0/2] Initial support for PXA1908 and samsung-coreprimevelte Duje Mihanović
2024-12-27 21:22 ` [PATCH 1/2] arm: mmp: add initial support for PXA1908 SoC Duje Mihanović
2024-12-27 21:22 ` [PATCH 2/2] board: samsung: add initial support for coreprimevelte board Duje Mihanović
2024-12-27 21:53 ` [PATCH 0/2] Initial support for PXA1908 and samsung-coreprimevelte Tom Rini
2024-12-28 11:10 ` Duje Mihanović
2024-12-30 15:25 ` Tom Rini [this message]
2024-12-31 11:16 ` Duje Mihanović
2024-12-31 16:05 ` 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=20241230152533.GC3476@bill-the-cat \
--to=trini@konsulko.com \
--cc=balejk@matfyz.cz \
--cc=duje.mihanovic@skole.hr \
--cc=u-boot@lists.denx.de \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox