From: "Marek Behún" <kabel@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Tom Rini <trini@konsulko.com>,
Priyanka Jain <priyanka.jain@nxp.com>,
Sinan Akman <sinan@writeme.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2] powerpc: Add support for CZ.NIC Turris 1.x routers
Date: Mon, 10 Jul 2023 20:51:34 +0200 [thread overview]
Message-ID: <20230710205134.4613eacd@dellmb> (raw)
In-Reply-To: <20230710141932.wdetsvwadbdlcgqb@pali>
On Mon, 10 Jul 2023 16:19:32 +0200
Pali Rohár <pali@kernel.org> wrote:
> On Monday 12 June 2023 14:07:24 Tom Rini wrote:
> > On Wed, Aug 17, 2022 at 10:56:22PM +0200, Pali Rohár wrote:
> >
> > > CZ.NIC Turris 1.0 and 1.1 are open source routers, they have dual-core
> > > PowerPC Freescale P2020 CPU and are based on Freescale P2020RDB-PC-A board.
> > >
> > > Hardware design is fully open source, all firmware and hardware design
> > > files are available at Turris project website:
> > >
> > > https://docs.turris.cz/hw/turris-1x/turris-1x/
> > > https://project.turris.cz/en/hardware.html
> > >
> > > This patch adds full U-Boot support for CZ.NIC Turris 1.x routers. P2020
> > > BootROM can load U-Boot either from NOR flash or from SD card. So there is
> > > defconfig file turris_1x_nor_defconfig which builds NOR version and
> > > defconfig file turris_1x_sdcard_defconfig which builds SD card version.
> > >
> > > Design of CZ.NIC Turris 1.x routers is based on Freescale P2020RDB-PC-A
> > > board, so common board code from boards/freescale/p1_p2_rdb_pc directory is
> > > shared and linked also into Turris 1.x U-Boot board code.
> > >
> > > Turris 1.x code in this patch uses modern distroboot and can boot Linux
> > > kernel from various locations, including NAND, SD card, USB flash disks,
> > > NVMe disks or SATA disks (connected to extra SATA/SCSI PCIe controllers).
> > >
> > > Signed-off-by: Pali Rohár <pali@kernel.org>
> >
> > To be clear, this is something that if there's still interest in
> > upstreaming this platform, this patch needs to be rebased and re-tested
> > as it's non-trivially out of date. In addition:
>
> So you have been waiting for year WITHOUT ANY COMMENT, to ensure that
> this patch does not apply anymore and to ensure that it would hard or
> even impossible to rebase this change on top of the moving development.
> And then you said that I should do this job. This is exactly same as
> writing to me "fuck you, we do not need you anymore". So I would answer
> for this to you that You are idiot. I have no other words for this. You
> were complaining that you are missing developers for doing cleanup or
> maintenance of powerpc. And this is the way how to ensure that no other
> would come. Congratulation. It is this what you wanted? Seems so.
There is interest for this to be rebased and retested.
Tom is not an idiot, this thing is on me, as I explained here
https://www.mail-archive.com/u-boot@lists.denx.de/msg476138.html
We are in the process of hiring some people to ease the load.
I will look into this then. I don't have anything else to say besides
that I am sorry and that there is too few of us now to do this work and
that I also am frustrated with this.
Marek
next prev parent reply other threads:[~2023-07-10 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 9:01 [PATCH] powerpc: Add support for CZ.NIC Turris 1.x routers Pali Rohár
2022-08-17 20:56 ` [PATCH v2] " Pali Rohár
2023-06-12 18:07 ` Tom Rini
2023-06-12 19:02 ` Marek Behún
2023-06-24 9:19 ` Pali Rohár
2023-06-24 16:57 ` Tom Rini
2023-06-25 15:27 ` Pali Rohár
2023-06-26 0:51 ` Tom Rini
2023-07-10 14:19 ` Pali Rohár
2023-07-10 18:51 ` Marek Behún [this message]
2022-08-31 16:48 ` [PATCH v3] " Pali Rohár
2023-03-29 19:32 ` [PATCH] " Pali Rohár
2023-03-29 20:02 ` Simon Glass
2023-04-01 8:28 ` Pali Rohár
2023-05-16 7:06 ` Pali Rohár
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=20230710205134.4613eacd@dellmb \
--to=kabel@kernel.org \
--cc=pali@kernel.org \
--cc=priyanka.jain@nxp.com \
--cc=sinan@writeme.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox