From: Tom Rini <trini@konsulko.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v2] powerpc: Add support for CZ.NIC Turris 1.x routers
Date: Sun, 25 Jun 2023 20:51:03 -0400 [thread overview]
Message-ID: <20230626005103.GK3931582@bill-the-cat> (raw)
In-Reply-To: <20230625152749.d4owb2mgayxj2byq@pali>
[-- Attachment #1: Type: text/plain, Size: 2322 bytes --]
On Sun, Jun 25, 2023 at 05:27:49PM +0200, Pali Rohár wrote:
> On Saturday 24 June 2023 12:57:46 Tom Rini wrote:
> > On Sat, Jun 24, 2023 at 11:19:51AM +0200, Pali Rohár 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:
> > >
> > > Meanwhile I have already done rebase and retest, v3 is here:
> > > https://patchwork.ozlabs.org/project/uboot/patch/20220831164821.29109-1-pali@kernel.org/
> >
> > Yes, and I replied to that with feedback.
>
> Seems that there is no feeback on above patch.
Well, you're right, everything that is in this thread, and still applies
right now is I guess in the v2 thread instead?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-06-26 0: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 [this message]
2023-07-10 14:19 ` Pali Rohár
2023-07-10 18:51 ` Marek Behún
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=20230626005103.GK3931582@bill-the-cat \
--to=trini@konsulko.com \
--cc=pali@kernel.org \
--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