Re: [PATCH v2 1/8] build: add e5500 CPU_TYPE
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
— Begin Message —
Not sure if it makes any difference here but the T2081 used by the WatchGuard Firebox M300 is actually an e6500 core. Ray > On Dec 20, 2021, at 2:00 PM, Stijn Tintel <st...@linux-ipv6.be> wrote: > > This CPU type is compatible with NXP's PPC based QorIQ processors, and > will be used by the upcoming new qoriq target. > > Signed-off-by: Stijn Tintel <st...@linux-ipv6.be> > --- > include/target.mk | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/include/target.mk b/include/target.mk > index 60760bf602..fb57553f7d 100644 > --- a/include/target.mk > +++ b/include/target.mk > @@ -234,6 +234,7 @@ ifeq ($(DUMP),1) > endif > ifeq ($(ARCH),powerpc64) > CPU_TYPE ?= powerpc64 > + CPU_CFLAGS_e5500:=-mcpu=e5500 > CPU_CFLAGS_powerpc64:=-mcpu=powerpc64 > endif > ifeq ($(ARCH),sparc) > -- > 2.32.0 > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
signature.asc
Description: Message signed with OpenPGP— End Message —
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Read more here: Source link