From: Tom Li <tomli@tomli.me>
To: Alexandre Oliva <lxoliva@fsfla.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: James Hogan <jhogan@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhc@lemote.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@vger.kernel.org, Tom Li <tomli@tomli.me>
Subject: Re: CS5536 Spurious Interrupt Problem on Loongson2
Date: Sat, 23 Feb 2019 09:56:51 +0800 [thread overview]
Message-ID: <20190223015650.GA8616@localhost.localdomain> (raw)
In-Reply-To: <ora7in8tfs.fsf@lxoliva.fsfla.org>
On Fri, Feb 22, 2019 at 09:43:43PM +0200, Aaro Koskinen wrote:
> Mini-PC does not have any EC. PMON is:
> Version: PMON2000 2.1 (Bonito) #121: Mon Jan 5 14:19:11 CST 2009.
On Fri, Feb 22, 2019 at 05:22:15PM -0300, Alexandre Oliva wrote:
> I don't have the PMON or EC versions in /proc/cmdline. machtype is the same.
> 'vers' in the pmon text prompt responds: PMON2000 2.1 (Bonito) #291
Okay, so the problem is presented on both Yeeloong laptops and MiniPCs, and
it seems both you are running some old PMON versions. The new PMON should
report the PMON and/or EC versions versions in /proc/cmdline.
The version I'm using is
> PMON: PMON2000 2.1 (Bonito) #7: 2010-08-31 01:26:26 (LM8089-1.4.9a)
I'll attempt to reproduce and investigate the problem after finishing the
initial pushes of Yeeloong platform drivers.
However, there are some difficulties.
* I don't have the MiniPC. Loongson 2F hardware is now completely unsupported,
and almost impossible to purchase one.
* Early PMON source was not released under a version-control system, and now it's
difficult to find both the source code and the binary for those earlier versions.
* PMON upgrading is notoriously unreliable, unless the binary image is completely
tested by someone with the identical setup, the result is likely a bricked machine.
I don't recommend you to upgrade the firmware, unless you've got the on-field support
of hardware hackers with soldering equipment and a EEPROM programmer.
I'll try asking online if anyone still has the old hardware lying around, and
check the corpse of those dead and buried threads posted on the Chinese fourm
ten years ago, to see if there's still some binary images.
Thanks,
Tom Li
next prev parent reply other threads:[~2019-02-23 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 20:22 CS5536 Spurious Interrupt Problem on Loongson2 Alexandre Oliva
2019-02-23 1:56 ` Tom Li [this message]
2019-02-23 6:08 ` Jiaxun Yang
2019-02-23 15:30 ` Aaro Koskinen
2019-02-24 4:55 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 14:37 Tom Li
2019-02-22 19:43 ` Aaro Koskinen
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=20190223015650.GA8616@localhost.localdomain \
--to=tomli@tomli.me \
--cc=aaro.koskinen@iki.fi \
--cc=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=lxoliva@fsfla.org \
--cc=ralf@linux-mips.org \
/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).