From: Pavel Machek <pavel@ucw.cz>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Huacai Chen <chenhc@lemote.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH 3/3] MIPS: Loongson64: Add /proc/boardinfo
Date: Fri, 16 Oct 2020 15:11:59 +0200 [thread overview]
Message-ID: <20201016131159.GB4335@amd> (raw)
In-Reply-To: <1602241050-24051-4-git-send-email-yangtiezhu@loongson.cn>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Hi!
> Add /proc/boardinfo to get mainboard and BIOS info easily on the Loongson
> platform, this is useful to point out the current used mainboard type and
> BIOS version when there exists problems related with hardware or firmware.
>
> E.g. with this patch:
>
> [loongson@linux ~]$ cat /proc/boardinfo
> Board Info
> Manufacturer : LEMOTE
> Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
> Family : LOONGSON3
>
> BIOS Info
> Vendor : Kunlun
> Version : Kunlun-A1901-V4.1.3-20200414093938
> ROM Size : 4 KB
> Release Date : 2020-04-14
Please put this into /sys somewhere, with usual rules. This is hard to
extend/parse.
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-10-16 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 10:57 [PATCH 0/3] Avoid build error, clean up numa.c and add /proc/boardinfo Tiezhu Yang
2020-10-09 10:57 ` [PATCH 1/3] MIPS: Loongson64: Select SMP in Kconfig to avoid build error Tiezhu Yang
2020-10-09 10:57 ` [PATCH 2/3] MIPS: Loongson64: Clean up numa.c Tiezhu Yang
2020-10-10 8:06 ` Jiaxun Yang
2020-10-09 10:57 ` [PATCH 3/3] MIPS: Loongson64: Add /proc/boardinfo Tiezhu Yang
2020-10-10 8:01 ` Jiaxun Yang
2020-10-10 23:40 ` Tiezhu Yang
2020-10-16 13:11 ` Pavel Machek [this message]
2020-10-17 1:23 ` Tiezhu Yang
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=20201016131159.GB4335@amd \
--to=pavel@ucw.cz \
--cc=chenhc@lemote.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.