From: Du Huanpeng <duhuanpeng@loongson.cn>
To: barebox@lists.infradead.org
Subject: Re: macro about loongson's CPU & SoC
Date: Tue, 26 Nov 2019 21:03:58 +0800 [thread overview]
Message-ID: <20191126130357.GA23625@brew> (raw)
In-Reply-To: <20191126115119.GA20169@brew>
> The name CPU_LOONGSON1B is used in the linux kernel.
> Please keep barebox macro name in sync with linux kernel.
shall we use the rules in a "balanced" way? :)
the name CPU_LOONGSON1B is used in the kernel, it is true.
if you dive into the source tree, you will find more~
in bootloader, do we need so many kinds of CPU, are they
realy different? two or three ISA set(CPU) is enough for
loongson's chip(see the table in my last mail) to run barebox.
Regards,
duhuanpeng
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-11-26 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 11:57 Du Huanpeng
2019-11-26 12:11 ` Antony Pavlov
2019-11-26 13:03 ` Du Huanpeng [this message]
2019-11-27 14:01 ` Sascha Hauer
2019-12-02 9:03 ` Du Huanpeng
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=20191126130357.GA23625@brew \
--to=duhuanpeng@loongson.cn \
--cc=barebox@lists.infradead.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