From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Greg Ungerer <gerg@kernel.org>, Strontium <strntydog@gmail.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH] MIPS: Revert "add support for buggy MT7621S core detection"
Date: Sat, 2 Oct 2021 10:25:31 +0200 [thread overview]
Message-ID: <20211002082531.GA4254@alpha.franken.de> (raw)
In-Reply-To: <20210930165741.9662-1-ilya.lipnitskiy@gmail.com>
On Thu, Sep 30, 2021 at 09:57:41AM -0700, Ilya Lipnitskiy wrote:
> This reverts commit 6decd1aad15f56b169217789630a0098b496de0e. CPULAUNCH
> register is not set properly by some bootloaders, causing a regression
> until a bootloader change is made, which is hard if not impossible on
> some embedded devices. Revert the change until a more robust core
> detection mechanism that works on MT7621S routers such as Netgear R6220
> as well as platforms like Digi EX15 can be made.
>
> Link: https://lore.kernel.org/lkml/4d9e3b39-7caa-d372-5d7b-42dcec36fec7@kernel.org
> Fixes: 6decd1aad15f ("MIPS: add support for buggy MT7621S core detection")
> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
> ---
> arch/mips/include/asm/mips-cps.h | 23 +----------------------
> 1 file changed, 1 insertion(+), 22 deletions(-)
applied to mips-fixes.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-10-02 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 16:57 [PATCH] MIPS: Revert "add support for buggy MT7621S core detection" Ilya Lipnitskiy
2021-09-30 17:14 ` Sergio Paracuellos
2021-09-30 22:33 ` Greg Ungerer
2021-10-02 8:25 ` Thomas Bogendoerfer [this message]
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=20211002082531.GA4254@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=gerg@kernel.org \
--cc=ilya.lipnitskiy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=nbd@nbd.name \
--cc=sergio.paracuellos@gmail.com \
--cc=strntydog@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).