All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Bradley Morgan <brads@mainlining.org>
Cc: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com>,
	Vincent Jardin <vjardin@free.fr>, Peng Fan <peng.fan@oss.nxp.com>,
	"u-boot@lists.u-boot-project.org"
	<u-boot@lists.u-boot-project.org>,
	Sinan Akman <sinan@writeme.com>, Bryan Brattlof <bb@ti.com>,
	Holger Brunck <holger.brunck@hitachienergy.com>
Subject: Re: [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1
Date: Mon, 26 Oct 2026 18:34:44 -0600	[thread overview]
Message-ID: <20261027003444.GO646438@bill-the-cat> (raw)
In-Reply-To: <B40E19A5-99C4-49F6-AF13-D0BE0D682404@mainlining.org>

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

On Tue, Oct 27, 2026 at 12:25:48AM +0000, Bradley Morgan wrote:
> On 27 October 2026 00:19:23 GMT, Tom Rini <trini@konsulko.com> wrote:
> >On Mon, Oct 26, 2026 at 09:27:05PM +0000, Bradley Morgan wrote:
> >> On 26 October 2026 21:19:52 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >On Mon, Oct 26, 2026 at 09:14:37PM +0000, Bradley Morgan wrote:
> >> >> On 26 October 2026 18:30:10 GMT, Tom Rini <trini@konsulko.com> wrote:
> >> >> >On Mon, Oct 26, 2026 at 05:27:05PM +0000, Bradley Morgan wrote:
> >> >> >> On 26 October 2026 17:23:32 GMT, Tom Rini <trini@konsulko.com>
> >wrote:
> >> >> >> >On Mon, Oct 26, 2026 at 05:00:19PM +0000, Bradley Morgan wrote:
> >> >> >> >> On 26 October 2026 16:58:47 GMT, Bradley Morgan
> >> >> ><brads@mainlining.org>
> >> >> >> >> wrote:
> >> >> >> >> >On 26 October 2026 16:55:09 GMT, Tomas Alvarez Vanoli
> >> >> >> >> ><tomas.alvarez-vanoli@hitachienergy.com> wrote:
> >> >> >> >> >>>>
> >> >> >> >> >>>>Hi all,
> >> >> >> >> >>>>
> >> >> >> >> >>>>Just a data point from a user: we are using U-Boot on a
> >T1040
> >> >> >(QorIQ
> >> >> >> >/
> >> >> >> >> >>>>mpc85xx) in a product, and we intend to keep up with
> >mainline
> >> >as
> >> >> >> >much
> >> >> >> >> >as
> >> >> >> >> >>>>we can. We'd appreciate PowerPC support staying in tree,
> >and
> >> >> >we're
> >> >> >> >> >happy
> >> >> >> >> >>>>to test patches on T1040 hardware and report back.
> >> >> >> >> >>>>We run u-boot in 32-bit mode (not sure if it is possible to
> >> >use
> >> >> >> >64-bit)
> >> >> >> >> >>>>and
> >> >> >> >> >>>>linux in 64-bit.
> >> >> >> >> >>>>I am in the process of bringing it up to our 2025.07 branch
> >> >and
> >> >> >> >> >>>>potentially
> >> >> >> >> >>>>mainlining as much as possible. We have some remnants of it
> >> >under
> >> >> >> >> >>>>`board/keymile/kmcent2`.
> >> >> >> >> >>>
> >> >> >> >> >>>Would T1042D4RDB affect you?
> >> >> >> >> >>
> >> >> >> >> >>Not directly from what I see in the code, as long as the
> >shared
> >> >> >code
> >> >> >> >with
> >> >> >> >> >>ARCH_T1040 is kept. Sorry for the false alarm, just wanted to
> >> >> >report
> >> >> >> >that
> >> >> >> >> >>there are dozens of us using powerpc :)
> >> >> >> >> >
> >> >> >> >> >What you could do if you would like is to test the whole
> >series
> >> >to
> >> >> >see
> >> >> >> >if
> >> >> >> >> >it unaffected you.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >Btw tom I had a idea: you merge Vincent's bug fix and my
> >> >maintainers
> >> >> >> >> >patch,you make a PowerPC custodian tree, and I handle the
> >series
> >> >and
> >> >> >> >the
> >> >> >> >> >naks and stuff and the comments.
> >> >> >> >> 
> >> >> >> >> and btw yes I'll make the pr with the finished patches so you
> >can
> >> >> >merge
> >> >> >> >> them cleanly
> >> >> >> >
> >> >> >> >Trees are relatively cheap, but I'm not sure we need another one
> >> >either
> >> >> >> >for the subset of formerly-Freescale and not-QorIQ PowerPC parts.
> >> >Since
> >> >> >> >I added you to the fsl-qoriq tree, you can also just pick up the
> >> >> >> >outstanding fixes and your maintainer patches (and leave dropping
> >> >stuff
> >> >> >> >for now, as this series shows today we're just getting people
> >having
> >> >a
> >> >> >> >chance to see and reply to this stuff) and send me a PR. Thanks.
> >> >> >> 
> >> >> >> Hi, sorry, I didn't clarify enough, so I had a chat for some
> >people
> >> >from
> >> >> >> the open src firmware slack, yes?
> >> >> >> 
> >> >> >> And here is their answer 
> >> >> >> 
> >> >> >> "Ah, Peng Fan maintains the FSL QoriQ tree:
> >> >> >> https://git.u-boot-project.org/u-boot/custodians/u-boot-fsl-qoriq
> >> >> >> 
> >> >> >> That is the vendor one though.
> >> >> >> So yea, I'd go with a general PowerPC tree.
> >> >> >> 
> >> >> >> Also because QoriQ is both Arm and PPC series. :sweat_smile:"
> >> >> >> 
> >> >> >> And even my slopper suggests the tree, for sanity purposes :D
> >> >> >
> >> >> >Fine, trees are still cheap. There's u-boot-ppc now. But please keep
> >in
> >> >> >mind everything else I said, thanks.
> >> >> 
> >> >> Thx. 
> >> >> 
> >> >> Question: will you merge the maintainers patch on this PR, so I can
> >> >focus on my add-on maintainers patch and the removals?
> >> >
> >> >Lets hold off on the removals a bit more, as I was saying.
> >> 
> >> That's not what I meant
> >> 
> >> I meant, you'd merge ONLY the maintainers patch in this PR
> >> 
> >> Then, I'll go and take up the removals, and give it say, a couple weeks
> >to
> >> let it marinade, and give it responses THEN submit a PR with the
> >removals
> >> in it. Then happy days.
> >> 
> >> 
> >> Or I could also take the maintainers patch with me too...
> >
> >Yes, please pick up the maintainers patches and if I follow what's in
> >Peng's queue right, there are a few other powerpc fixes out there.
> >
> 
> Not in this PR, maybe any on lore that stands out?
> 
> lx2160a is ARM
> 
> nbxv3 is arm too.
> 
> I'll look harder (maybe I'm wrong) soon

Maybe I'm just mis-remembering, thanks.

-- 
Tom

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

  reply	other threads:[~2026-10-27  0:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22  7:34 [GIT PULL] Please pull fsl-qoriq-for-2027-01-rc1 Peng Fan
2026-10-22 14:42 ` Bradley Morgan
2026-10-26  8:43   ` Vincent Jardin
2026-10-26  9:25     ` Bradley Morgan
2026-10-26 14:20       ` Tom Rini
2026-10-26 14:58         ` Bradley Morgan
2026-10-26 16:19           ` Vincent Jardin
2026-10-26 16:26             ` Bradley Morgan
2026-10-26 16:39               ` Tomas Alvarez Vanoli
2026-10-26 16:42                 ` Bradley Morgan
2026-10-26 16:55                   ` Tomas Alvarez Vanoli
2026-10-26 16:58                     ` Bradley Morgan
2026-10-26 17:00                       ` Bradley Morgan
2026-10-26 17:23                         ` Tom Rini
2026-10-26 17:27                           ` Bradley Morgan
2026-10-26 18:30                             ` Tom Rini
2026-10-26 21:14                               ` Bradley Morgan
2026-10-26 21:19                                 ` Tom Rini
2026-10-26 21:27                                   ` Bradley Morgan
2026-10-27  0:19                                     ` Tom Rini
2026-10-27  0:25                                       ` Bradley Morgan
2026-10-27  0:34                                         ` Tom Rini [this message]
2026-10-26 17:19                     ` 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=20261027003444.GO646438@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bb@ti.com \
    --cc=brads@mainlining.org \
    --cc=holger.brunck@hitachienergy.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=sinan@writeme.com \
    --cc=tomas.alvarez-vanoli@hitachienergy.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=vjardin@free.fr \
    /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.